This document describes the process to troubleshoot when Non-delivery Receipts (NDRs) are reported to the recipient in Unity Connection.
Occasionally, you might see unexplained NDRs reported to the receipent in Unity Connection. When it is reported, the NDR reports to the Unaddress Distribution List. There might or might not be reports of messages that were not reported to Unity Connection users. Other settings might include:
- Single Inbox is also configured.
- Unity Connection is configured to relay the message to Smart Host if Unity Connection cannot deliver the message.
- Unity System Settings > General Configuration > 'When a recipient can not be found' is set to 'Relay message to Smarthost'.
In order to troubleshoot this issue, perform these steps:
- Navigate to Cisco Unity Connection Serviceability.
- Choose Trace > Micro Trace.
- Choose Message Transfer Agent (MTA) 10 - 30.
- Choose Simple Mail Transfer Protocol (SMTP) 10 - 30.
- Attempt to reproduce the issue or note the exact time of the next NDR received.
- Use the Real-Time Monitoring Tool (RTMT) to collect files and collect Connection Message Transfer Agent and Connection SMTP Server from 15 minutes before and after the NDR is received.
In the Connection MTA trace you might see:
class=CsUnityMtaMessage;Attempting to relay a message that had already been
relayed. NDRing the message to:f99b2b0c-7f8d-440e-838d-c4214a8bcc8c
When this occurs, navigate to Connection Administration > System Settings > SMTP Configuration > Smart Host.
You might find that the Smart Host is the actual Unity Connection server name or IP address. This
causes a loop which is related to the message found in the MTA trace. Change this setting to an Exchange server.