Tech Support Forum banner
Status
Not open for further replies.

[SOLVED] Exchange 2003 on SBS 2003

1.4K views 4 replies 2 participants last post by  2xg  
#1 ·
I have added a second email domain to a clients Exchange system and all is working fine with that address.
I have now been asked to add a third email domain so I followed the same steps that I took when adding the second domain but the new address is not working. When I send a mail to it I get an undeliverable reply back from the postmaster at the second domain saying the address cannot be found.

I have checked the MX records and they are pointing to the same place as the 2nd address.
I have created a new recipient policy for the 3rd address.
I have updated AND rebuilt the Recipient Update Service.
I have added the relevant IP address to the relay restrictions "Allow" list.
I have restarted both the SMTP and Exchange Routing Engine services.
I have added the 3rd address to the MailMarshal domains.
I have added the 3rd address to the MailMarshal routing table.

I have noticed that the 3rd address has NOT filtered through to AD but the 2nd address has.
I have manually added the 3rd address to one of the users in AD and tried to send a mail but got the same undeliverable reply come back.

I am running out of ideas!
 
#2 · (Edited)
Re: Exchange 2003 on SBS 2003

Hi System10,

I dont' see in your check list about Host (A).
Check your DNS Manager where Exchange Server running - Did you create a Host (A) for the 3rd Domain and point to the correct IP?

If you're not sure about the IP, you may find out from WhoIs.

You may also do a nslookup and see what IP the 3rd Domain is pointing to. Here's an example of what the dnslookup results, if the configuration is setup correctly.

Server: server.company.local
Address: 10.10.0.X

Name: domain3.com
Address: 216.227.X.X

I hope that I explained it clearly. It has been a while since I've worked on SBS2003, shd somewhat similar config on SBS2011 :rolleyes:
 
#3 ·
Re: Exchange 2003 on SBS 2003

Hi 2xg,

I'm a little confused now. As far as I was concerned, A records didn't even play a supporting part in getting the 2nd domain email up and running. I didn't have do do anything with them and no one mentioned them to me as being something I'd have to configure. I followed exactly the same steps for the 3rd domain email but no cigar.

I will look into the A records though and see what I can find as I've obviously missed something vital. Thanks for the heads up.
 
#4 ·
Re: Exchange 2003 on SBS 2003

Okay, so I got this problem nailed. In the end it was simply the order of the addresses in the MailMarshal routing table! It's always something simple...

Thanks for your help.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.