If you see the following error in your Exchange 2003, 2007, or 2010 queue, there are three things you should do to troubleshoot the problem:
451 4.4.0 Primary target IP address responded with: “421 4.2.1 Unable to connect.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
Below are the three items you need to check:
Type helo yourdomain.com and enter.
Type mail from: yourname@yourdomain.com and enter.
Type rcpt to: recipient@remotedomain.com and enter.
Type data and enter.
Type subject: test and enter.
Type test and enter.
Type . and enter to quit the session
If you do not see any errors, this proves the problem is with your server and not with the recipients server.
Type set q=mx
Type <remote email domain name>
If you see the name of a server, then they have an MX record
If all this fails, post your question on a forum like http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/8d41844f-cc28-4a4b-9463-fd5e53392830 and read articles like http://blogs.technet.com/b/messaging_with_communications/archive/2011/04/22/how-to-manage-exchange-2010-message-queues.aspx
This website uses cookies.
View Comments
When I got to this step "Type mail from: yourname@yourdomain.com and enter."
I got the following error 500 #5.5.1
Sorry, that is not an error I have run into. I would just Google and see what comes up.
After telnet to port 25 failed, tracert from firewall failed too. Opened ticket with ISP who was able to duplicate issue.
In our case, we need to ensure the IP ranges on the Hybrid Receive Connector and the NAT rule for port 25 matched.
In addition to the original port ranges on the receive connector, we also added the ranges for 'Microsoft Online Services' from the microsoft site.
http://onlinehelp.microsoft.com/Office365-enterprises/hh373144.aspx
if your exchange server don't have enough space on C: the same Error occurs.
Thanks for recommending our SuperTool. I also noticed that you recommended another source for checking you rDNS, our tool does that as well. We've worked hard to build an all encompassed tool, if you have any feedback, we'd love to hear it!
Thanks,
@mxtoolbox
Your service is excellent and I am very happy to support it.
Thanks and have a HAPPY NEW YEAR!