NDR message #5.5.0 smtp;554 email address…Relay operation rejected

0 pts.
Tags:
Microsoft Exchange
Hi, I'm getting random NDRs when users are sending to other users in our Exchange org. Granted the recipients are in another Routing Group so I suspect that problem to be there. Where do I check to make sure that our different routing groups allow messages to flow between them? Thanks. Delius
ASKED: January 6, 2005  6:10 PM
UPDATED: January 24, 2005  11:31 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

I would use exchange system manager to check your routing groups. You may want to take a look at your recipient policies while your in there to make sure they are correct.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Petroleumman
    Hello, Open Exchange Systems Manager and expand Routing Groups -> Org -> Connectors -> Internet Mail Connector and check your entries on the 'Connected Routing Groups' tab. You should have an entry for each one of your organizations active routing groups listed. If not, add them and test. The 5.5.0 error is a generic SMTP error so it gives very little or no valuable information to by. You can also set up Message Tracking and see if you can identify the path of a message to possibly see where it is failing. If this does not resolve your problem, include more detail in your follow-up response. Good Luck!
    0 pointsBadges:
    report
  • Dcheng
    Thanks for the help. The RGC for our location to another looks like it's setup correctly and the right local and remote servers are in each connector. Each RGC has a list of accepted servers that can route past it or they're set to allow all to route past them. Since all the server's in question are internal this should not be a problem. The weird problem is that sometimes the mail gets delivered directly to the remote server while other times it gets delivered to the remote location's external (sendmail) SMTP server. What's even worst is that the external SMTP server does not handle the domain the email addresses are sent to (thus I suspect the bounce message). What we discovered was that when the Public Folder referrals setting for each RGC are set to allow the NDRs stop and mail is delivered. It's so strange.
    0 pointsBadges:
    report
  • Dcheng
    Is it possible that this is a DNS issue? If the DNS is using a round-robin DNS, it's possible that the "remote location's external SMTP server" might be an alternate route for the "remote server" you're trying to reach. If DNS or your routing mechanism can't connect to the "correct" remote server, DNS might be connecting it with the next "round robin" server. Just a thought. I'd suggest getting the network folk involved, possibly some network sniffing!
    0 pointsBadges:
    report
  • Dcheng
    We also suspected a DNS problem but it turns out that the FQDN of the Virtual SMTP server on the bridgehead servers int the remote RG was set to an external MX server that denied all of our deliveries. The solution was to change the FQDN to point to the Exchange servers there. Other Exchange admins have told me that the FQDN should not matter as Exchange uses the GC for address resolution and delivery so it doesn't matter what the FQDN for the Virtual SMTP server is set to. I agree also but it appears that eventhough the GC resolves the address and knows which server to send to it must get relayed past the bridgehead server and that is where we saw the problem with the FQDN. Can anyone clarify how Exchange routes internal mail? Thanks.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following