Link to home
Start Free TrialLog in
Avatar of steve_howden
steve_howdenFlag for Australia

asked on

SBS 2003 Exchange. Trouble having two domains with incoming SMTP mail

Hi expert people,

We are new users of SBS 2003 (love it!) SBS 2003 SP1 and Exchange 2003 SP2.

Once we got everything running  using our existing POP accounts we decided to move over to SMTP direct to Exchange. A problem has cropped up;

We have two domains, lets call them domain1 and domain2. Domain1 is the primary domain that we setup at the installation of SBS.
We got our ISP to add two new MX records so that we now have mail.domain1.com and mail.domain2.com pointing at the IP of our external interface and there are backup MX records going to a server at our ISP.

I then went into Recipient Policies and added @domain2.com to the list and checked the box. Then "update now" in the Recipient Update Service. A quick check of users showed that the new email addresses userx@domain2.com had been added

All mail delivery to domain1 is fine, good as gold. Absolutely nada for anything sent to domain2 though.

I'm sure I am missing some vital step here.

Thanks, Steve
ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of steve_howden

ASKER

Thanks leew,

Didn't know there was a wizard for adding a second domain. Damn, I love wizards with SBS.

No I didn't reboot. Doing it now...... I'll let you know.

Steve
It's not terribly clear unless you reference web sites/documentation, but you basically run the same wizard that you ran the first time to setup the domain.  It adds the recipient policy.  
Dear leew,

Eeeeeerm, do I feel like a dummy! A restart was all it needed. Doh!

That was a nice easy point score for you. Hopefully the next question will be harder, I am going to post a new question in this topic area very shortly about mailing to public folders.

many thanks for the timely reply, Steve
You probably just needed to restart the exchange services, but it's often easier to just reboot.