• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 520
  • Last Modified:

Removing 2nd SMTP domain from an Exchange 2003 Organizatioin

Please help!

We have an Exchange 2003 SP2 hosting two SMTP domains @a.com and @b.com. The OS is Windows 2003 SP1 (it is an SBS 2003 for that matters). The @b.com group is moving off so we have set up a new Exchange for them. Now when @b.com people send emails to @a.com people the mails need to go out of the old server. What is the correct procedure for removing @b.com from the old server?

So far I have tried:

On the old server there is only on Recipient Policy - "Default Policy" which contains two SMTP addresses @a.com and @b.com, with @a.com as primary. I removed @b.com from the policy. When I hit OK it asked if I want to apply the policy down I chose NO. The address space was indeed removed from the policy.

After that, the server won't send any email to outside. All mails are stuck in the queues. Tracking showed they all stopped at "Message routed and queued for remote delivery" but never reached "Start outbound transfer of message".

I put the @b.com back to the policy. The server started to send mail to outside.

I knew I missed some steps here. I had not remove the references to @b.com in users and public folders' email addresses. But I want to know if anybody has done this type of work? Is there a known good procedure to follow? The old server is still the production server for @a.com people. Breaking it will piss them off big time.

  • 4
  • 2
1 Solution
R. Andrew KoffronCommented:
remove the recipient policy, clear any @b.com email addresses make sure there is a valid MX record for b.com, flush dns.  check to make sure there isn't a forward lookup zone for b.com it should start working correctly in a few hours.

SBS2003 is fairly limited so I wouldn't think there'd be anything really stuck in there referring to exchange stuff.  once the recipient policy and addresses are removed.

you might try and add a forward lookup zone with all the  A records for b.com's mail and web if it's not working soon, and mx record of course.
shutterhackerAuthor Commented:
Thank you Harel.

The forward lookup zone for b.com has been removed weeks ago from two DNS servers in the domain that the old exhange server resides in. The MX record for b.com has been created for few weeks. On the old server the resolving client (by ping) seems to be fine revolving the MX record for b.com to the correct public address. I think this prep is complete.

Which one should we do first?

Clearing all @b.com address


removing @b.com from the default policy?

When I remove @b.com, should I choose yes to "do you want to apply down the policy"? I am wary about YES because I am sure exactly what it means. The users in ADUC have "Automatically update e-mail addresses based on recipient policy" checked. I don't know what the consequence to existing addresses when I choose Yes.
R. Andrew KoffronCommented:
I believe you should, if it's the question about applying the policy to all recipients, you want to remove it. if your domain has moved to a new server.
get a screen shot of the exact dialog question.
it's been a while since I've dropped a recipient policy and don't want to tell you the wrong thing.
basically removing the b.com domain from the a.com group is exactly what you want to do.
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

shutterhackerAuthor Commented:
Thanks again. Applying the policy down, I was able to make it work this time. Mail flow is normal now.
shutterhackerAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for shutterhacker's comment #a39457518

for the following reason:

Helpful tips.
shutterhackerAuthor Commented:
Thanks again.
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.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now