Hello, As of about a week ago, I am unable to send any emails to the secondary domain configured on my Exchange server. When I try to send an email to this domain, I get the following NDR: Reporting-MTA: dns;snt0-omc1-s5.snt0.hotmail.com Received-From-MTA: dns;SNT109-DS18 Arrival-Date: Mon, 16 Aug 2010 11:54:01 -0700 Final-Recipient: rfc822;rsutton@secondarydomain.net Action: failed Status: 5.5.0 Diagnostic-Code: smtp;550 relay not permitted Here is what I have tried/verified: The secondary email domain is configured in the default recipient policy and is check marked. Relay permissions on the SMTP virtual server are configured to allow any authenticated computer to relay. There are no additional errors in the event log. I have enabled logging on the SMTP virtual server however there is no information in that log. Emails sent to the primary SMTP domain are working without problem. Please help. Thanks, Ryan

Since you're not seeing anything in the SMTP log, I'd check the MX records for that secondary domain. -Peter

The MX record is pointing to the same IP as the primary domain.

You want the Exchange Server to accept the message correct?Not relay? Are you sure you have you made Exchange authoritive for that domain? Did it ever work? Or is this a new domain? Does Exchange accept the messages directly from the internet or is there something in between? http://support.microsoft.com/kb/823158

I want Exchange to accept the message and deliver it to the user. In the Exchange Sys manager in the recipient policy the box is checked for "This Orginzation is responsible for all mail delivery to this address" which I believe means it is authoritive. It has been working for a year+, there were no changes made prior to when it stopped working. The Exchange server accepts the messages from our hosted spam solution which is configured with the domain/user and pointing to the same IP as the primary domain.

Does Exchange SMTP logging and message tracking for the hosted anti-spam provider show that it accepted the message and attempted to route it to the Exxhange Server? In your NDR, hotmail is reporting the failure, so you sent the message from your hotmail account and the accepting SMTP gateway rejected it. That makes me think the problem is with the anti-spam provider.

SMTP logging and message tracking are not showing anything. I agree it does sound like an issue with the anti-spam. I will verify if those settings are correct and update. Thanks.

The anti-spam provider did not have the secondary domain configured. We added that and now we are getting new NDR's: 2010-08-17 09:09:05 H=private.co.uk [212.53.64.29] F=<private@hotmail.com> rejected RCPT <martin@seconddomain.net>: response to "RCPT TO:<martin@primarydomain.com>" from mail.primarydomain.com [Exchange public IP] was: 550 5.1.1 User unknown This is only happening to two users, and FWIW both users have the secondary domain configured as their primary SMTP address.

Hi, First, I would like to confirm the following questions: 1. What’s the meaning of the following sentence: “This is only happening to two users, and FWIW both users have the secondary domain configured as their primary SMTP address.”? Does it mean that only two users have the problem and the two users have primary SMTP address? 2. Can you send the email from Hotmail to other Mailbox users on Secondary Exchange server or the issue only occur on certain user? Regarding to the latest NDR information, it can occur by incorrect Filter recipients settings. Please refer to the following article to assure that the problematic user does not list in the Block list. How to configure connection filtering to use Realtime Block Lists (RBLs) and how to configure recipient filtering in Exchange 2003 Does the same NDR error persist? If so, I suggest you run a Telnet SMTP test to the primary Exchange server and verify whether the email can go through. For more information about Telnet command, please refer to the article below: Use Telnet to Test SMTP Communication Thanks, NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

"The secondary email domain is configured in the default recipient policy and is check marked. " U better create new recipient policy with secondary domain. and remove from default one. It should work. -bpara

Please see my responses to your questions: 1. What’s the meaning of the following sentence: “This is only happening to two users, and FWIW both users have the secondary domain configured as their primary SMTP address.”? Does it mean that only two users have the problem and the two users have primary SMTP address? Yes you understand correctly. 2. Can you send the email from Hotmail to other Mailbox users on Secondary Exchange server or the issue only occur on certain user? Yes it only happens to these two users. The only difference I see with these two users is that the secondary domain is their primary SMTP address. Regarding to the latest NDR information, it can occur by incorrect Filter recipients settings. Please refer to the following article to assure that the problematic user does not list in the Block list. How to configure connection filtering to use Realtime Block Lists (RBLs) and how to configure recipient filtering in Exchange 2003 Thanks I will take a look Does the same NDR error persist? If so, I suggest you run a Telnet SMTP test to the primary Exchange server and verify whether the email can go through. For more information about Telnet command, please refer to the article below: Use Telnet to Test SMTP Communication I will check and report back. 1. What’s the meaning of the following sentence: “This is only happening to two users, and FWIW both users have the secondary domain configured as their primary SMTP address.”? Does it mean that only two users have the problem and the two users have primary SMTP address? Yes you understand correctly. 2. Can you send the email from Hotmail to other Mailbox users on Secondary Exchange server or the issue only occur on certain user? Yes it only happens to these two users. The only difference I see with these two users is that the secondary domain is their primary SMTP address. Regarding to the latest NDR information, it can occur by incorrect Filter recipients settings. Please refer to the following article to assure that the problematic user does not list in the Block list. How to configure connection filtering to use Realtime Block Lists (RBLs) and how to configure recipient filtering in Exchange 2003 Thanks I will take a look Does the same NDR error persist? If so, I suggest you run a Telnet SMTP test to the primary Exchange server and verify whether the email can go through. For more information about Telnet command, please refer to the article below: Use Telnet to Test SMTP Communication Thanks, Novak Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Thank you for your update. At this stage, please take your time to perform the above suggestions to check the result. If there is any progress, please feel free to let me know. Regards, NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.