Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

A non-delivery report with a status code of 5.3.5 was generated

Avatar of bluetab
bluetab asked on
ExchangeSBS
3 Comments1 Solution1412 ViewsLast Modified:
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 <SERVERWCf3ednHM3SOl00000003@xyz.com>).  
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-ON882577C2.0059ED0D-862577C2.006676AA@def.com>).  
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
Avatar of Shreedhar Ette
Shreedhar EtteFlag of India imageTechnical Manager
Commented:
This problem has been solved!
Unlock 1 Answer and 3 Comments.
See Answers