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.

Thanks
shutterhackerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
0
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

or

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.
0
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

shutterhackerAuthor Commented:
Thanks again. Applying the policy down, I was able to make it work this time. Mail flow is normal now.
0
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.
0
shutterhackerAuthor Commented:
Thanks again.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.