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
steve_howdenAsked:
Who is Participating?
 
Lee W, MVPConnect With a Mentor Technology and Business Process AdvisorCommented:
You should have used the wizard... but I don't *THINK* that not using it should have caused a problem.  Have you rebooted the server?
0
 
steve_howdenAuthor Commented:
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
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
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.  
0
 
steve_howdenAuthor Commented:
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
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
You probably just needed to restart the exchange services, but it's often easier to just reboot.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.