Question : Exchange Server 2003 unable to relay for second domain

Hello,
We have tried to configure Exchange 2003 to start accepting mail for a fourth domain (we already have it accepting mail for 3 domains). We know the external DNS for the new domain name is working properly, here is why: We have Symantec anitspam filter sitting on our network. The external DNS forwards mail to the symantec antispam --> which in turn scans it and sends it to the Exchange Server. Our DomainA.com / DomainB.com / and DomainC.com works perfect. Anything sent to our new domain (Domain4.com) will cause symantec to respond with "Unable to Relay message". So, we know Domain4.com mail is getting to the symantec filter on our network but exchange is rejecting it!?

In Exchange system Manager, we've added the new domain name to the default Policy (under Recipient Policies), just like the other three, and the checkbox is checked (but it's not set as the default, becuase DomainA.com is the default!)) In Active Directory (on a separate server), we've modified some users to have the additional email addresses in their profiles.

Any mail that we send from an external source to [email protected] comes back to the sender as "unable to relay message". We have symantec set up to send a response to the sender with the error message.

Any ideas? sound familiar?

One thing I did discover after doing research, this might help you. We downloaded Microsoft's metabase editor to the Exchange srv and went under LM\SMTPSVC\1\DOMAINS and did not find the new domain, but I do see the other three domain entries, and they do receive email properly. Maybe the DS2MB is not replicating to the Metabase? Here is the article where I found this info on the metabase:
http://www.eggheadcafe.com/ng/microsoft.public.exchange2000.win2000/post3906410.asp

Ok, please let me know if I can clarify any points.

Thanks in advance!
Sean

Answer : Exchange Server 2003 unable to relay for second domain

PAQed with points (250) refunded

DarthMod
Community Support Moderator