DFR (Delivery Failure Report) Error Message:
User sends a message to another user on the same Exchange server or to another Exchange server within the Domain across a connector or in a different Exchange Domain/Forest. The error reason is;
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator. The MTS-ID of the original message is: ...
Possible Solutions:
1. Issue with a public folder's offline address book / contact list.
Administrative Groups --> First Adminstration Group --> Folders --> Public Folders --> (right click) View System Folders --> Offline Address Book --> [Insert folder names here (check each one)] --> OAB Folders/Properties
On replication tab, issue could be that the OAB Version 2 setting is not set to replicate.
2. Issue with an invalid "Target Address" for a contact, user, E-mail address (external), or public folder with a OAB address book contact.
If the error is to a specific person/group, then search for that destination e-mail address and check the target e-mail setting/value.
3. Issue shows itself only after "a while" when up to that point the target e-mail address has been working. The target e-mail address/site connector to the destination domain or account is still valid. A SMTP service and routing service restart does fix this issue for "a while". Solution is unknown to us. Disappeared after migration to 2008 Exchange server.
4. Two folders or users or contacts loop in their Alternate Recipient field.
5. A "targetAddress" attribute on a mailbox-enabled user or folder is populated when it should not be or is populated with an address that points to looping route. Clear the targetAddress attribute.
(This is similar to #1 reason above.)
6. A recipient policy includes local domain that matches an MS Exchange server. In this case the policy needs to have the server(s) removed.
7. If the error includes "MAPI Reason Code: 1, MAPI Diagnostic Code 3" and you are using an Exchange / Domino connector but sending from the "Lotus side", check your Domino Directory for the following:
a. User forwarding address that forwards to an Exchange side e-mail that no longer exists and there is a rule/policy on the Exchange-side that routes and loops the message until the maximum hops on the Exchange side.
b. Group members field contains an e-mail address that routes to the Exchange side that no longer exists and there is a rule/policy on the Exchange-side that routes and loops the message until the maximum hops on the Exchange side.
The fix will be like both fix the looping connector issue on the Exchange side (e.g. domain suffix forwards in place for various "sister" divisions of a company.) that makes this a looping issue and not a invalid recipient issue, and update the forwarding address or group member e-mail address from the "old" e-mail suffix to the current/new domain suffix (e.g. somename@rcs.com --> mindwatering.com) to fix the catalyst that displays the Exchange routing issue.
You can skip Dynamic groups (as those are auto-populated by the mail servers based on the update frequency specified in the Domino Directory Domain Profile). You can also skip Mail-in Application/Database documents as those point to Domino applications not e-mail addresses outside Domino.
You should also check any Directory Assistance directories and search for the target e-mail address in a forward e-mail address field.
Other Tips:
Use message tracking to confirm which server was the last good stop. That should help you narrow down the connection, contact, or folder with the "bad" e-mail address.
Check the SMTP logs on the last server before the mail bounced. Look for the target/destination e-mail address bouncing.
previous page
|