bluetab
asked on
A non-delivery report with a status code of 5.3.5 was generated
Since Monday afternoon many of my users have not been able to send emails. Most of the emails are getting stuck in the queue. The Event Viewer is reporting the following two errors:
1st Error: Event 3017
A non-delivery report with a status code of 5.3.5 was generated for recipient rfc822; abc@def.com (Message-ID <SERVERWCf3ednHM3SOl000000
Causes: A looping condition was detected. (The server is configured to route mail back to itself). If you have multiple SMTP Virtual Servers configured on your Exchange server, make sure they are defined by a unique incoming port and that the outgoing SMTP port configuration is valid to avoid looping between local virtual servers.
Solution: Check the configuration of the virtual serverÆs connectors for loops and ensure each virtual server is defined by a unique incoming port.
2nd Error: Event 3015
A non-delivery report with a status code of 5.3.0 was generated for recipient rfc822;abc@def.com (Message-ID <OFB9DDEC9A.4A170CE7-ON882
Causes: Exchange mistakenly attempted mail delivery to an incorrect MTA route.
For more information, click http://www.microsoft.com/contentredirect.asp.
Solution: Check your route and topology; use the winroute tool to ensure the routes are properly replicated between servers and routing groups.
Steps taken:
Verified that only one SMTP Virtual Server is configured. The MTA Stacks service was disabled. I have reenabled this service and deleted the two appropriate registry keys. To my knoweldge there are no users who have rules configured that would cause a looping issue. Right now I'm wondering our domain has been blacklisted somewhere but I'm not sure the best way to check.
SBS 2003 SP 2 w/ Exchange SP2
1st Error: Event 3017
A non-delivery report with a status code of 5.3.5 was generated for recipient rfc822; abc@def.com (Message-ID <SERVERWCf3ednHM3SOl000000
Causes: A looping condition was detected. (The server is configured to route mail back to itself). If you have multiple SMTP Virtual Servers configured on your Exchange server, make sure they are defined by a unique incoming port and that the outgoing SMTP port configuration is valid to avoid looping between local virtual servers.
Solution: Check the configuration of the virtual serverÆs connectors for loops and ensure each virtual server is defined by a unique incoming port.
2nd Error: Event 3015
A non-delivery report with a status code of 5.3.0 was generated for recipient rfc822;abc@def.com (Message-ID <OFB9DDEC9A.4A170CE7-ON882
Causes: Exchange mistakenly attempted mail delivery to an incorrect MTA route.
For more information, click http://www.microsoft.com/contentredirect.asp.
Solution: Check your route and topology; use the winroute tool to ensure the routes are properly replicated between servers and routing groups.
Steps taken:
Verified that only one SMTP Virtual Server is configured. The MTA Stacks service was disabled. I have reenabled this service and deleted the two appropriate registry keys. To my knoweldge there are no users who have rules configured that would cause a looping issue. Right now I'm wondering our domain has been blacklisted somewhere but I'm not sure the best way to check.
SBS 2003 SP 2 w/ Exchange SP2
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the info Shree. I checked the blacklist site and we are listed on the CBL. I've requested to be removed and will scan some computers to see if they are infected.
I already went through the kb555418 link and it wasn't much help.
I'll post back and let you know if the problem is resolved after being removed from the CBL.
Scot
I already went through the kb555418 link and it wasn't much help.
I'll post back and let you know if the problem is resolved after being removed from the CBL.
Scot
http://support.microsoft.com/kb/555418