• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1373
  • Last Modified:

exchange MTA, all sent mail is NDR'd

A non-delivery report with a status code of 5.3.0 was generated for recipient rfc822;ccy7912@ethome.net.tw (Message-ID  <96493585.EL067@hotmail.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.

The server was running fine for more than half a year now, and all of a sudden.... we are experiencing this.. i have seen accepted answers for this exact problem but the resources are no longer on this site....

Thanks for any help i get...

cw
0
cvvood
Asked:
cvvood
  • 4
  • 4
1 Solution
 
rakeshmiglaniCommented:
How many exchange servers do you have?
Is this E55 or E2k or E2k3?
How is the mail flow configured?
Any recent change or patch installed?
Is the internal mail flow working fine?
any errors in the application logs?
0
 
cvvoodAuthor Commented:
The error above is the error in the application log...
2003 server

I do not believe that there were any patches installed
 Internal Mail is flowing fine
mail is configured to be forwarded to our providers SMTP server


0
 
rakeshmiglaniCommented:
have you tried restarting exchange services?
do you see any email stuck in the smtp queues?
any errors in the application logs?
have you specified smart host in the smtp virtual server or configured it in a smtp connector?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
cvvoodAuthor Commented:
yes, restarted...
yes mail in queues, but looks like junk...  could i be compromised?
the error above has been reported MULTIPLE time on the application event log
I have been forwarding all mail to the smart host... but just removed that to send from the local SMTP Server to test....

Thanks Rakes....
0
 
rakeshmiglaniCommented:
you need to clear the queues first.. check the following article for that.. it is very good

Filter Out Mail to Non-Existent Users
http://www.amset.info/exchange/filter-unknown.asp

NDR and Open Relay Spam Clean Up
http://www.amset.info/exchange/spam-cleanup.asp

Are you an Open Relay?
http://www.amset.info/exchange/smtp-openrelay.asp
0
 
cvvoodAuthor Commented:
I am now at the point where all of the above are done or false, I am not an open relay.  I have no spam,  And the filter unknown has been activated.

I have spoken with my ISP and found that they did infact have issues. but corrected them.

During their issues I took the Smart host off and sent all mail out through the local SMTP server on the exchagne server...  we began to get NDR's from client sites because of reverselookup....  

So after contacting the ISP i changed the connector back to it's original settings restarted the router and MTA stacks....

But still no good....

CW

any ideas?   Mail is routing internally very fast, and the system administrator's message (NDR) arrives IMMEDIATELY after sending....


The message cannot be delivered due to a configuration error on the server. Please contact your Administrator.
            <repsgex.repsg.com #5.3.0 smtp;553 5.3.0 DENY>

I have delt with Exchange for quite some time, and this is just crazy...  am I really Denying my own mail out?

CW

0
 
cvvoodAuthor Commented:
alright...

Well, sounds like the changes I made were correct....

Can you answer me one question....

If you make changes to the Default SMTP server,  what do you have to restart to make sure all the changes are initialized?

secondly....  My ISP has put a new smtp server online, I was pointing to the old one as the DNS had not updated...  But better yet, I updated the DNS records on the server, but when I rebooted, the server's DNS records were not updated.....

Anyway, hollar back and you got the points.. thank you for the sounding board.. I knew I was doing the right things....

CW
0
 
rakeshmiglaniCommented:
You should restart SMTP Service after any changes you make in the SMTP Virtual server.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now