Removing a domain name from Exchange server

We have an Exchange 2003 email server running three email domain names, eg:

We have moved to a new server (external/internet based now). However, when users on or try to send email to, it bounced back saying the recipient is unknown, eg:

Your message did not reach some or all of the intended recipients.
Sent: 23/03/2006 07:59
The following recipient(s) could not be reached: on 23/03/2006 07:59
  The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
  <mail.encams.local #5.1.1>

The email sent to is not leaving the exchange server (we are monitoring at gateway level). How can we remove all traces of the from our current exchange server, therefore forcing the email "out" of the gateway?

On Exchange 5.5, to remove a domain name, you simply go to site > configuration > site addressing > and remove the email domain name from there.

How would I remove from my Exchange 2003 server?

Urgent, hence 500 points.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

how did you move to a new server?
is the new server part of the same exchange ORG and Admin group?
EncamsAuthor Commented:
Hi. is now not on our lan, our building, our network or anything, it is a completely separate entity which we have created externally (on the internet) and is hosted externally.

We "simply" need to remove traces of from our existing AD/Exchange to enable email addressed to to go "out" to the Internet, instead of it looking "locally" for it.

have you checked your recipient policies?
is the email address configured there?
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

EncamsAuthor Commented:

We edited the recipient policy for and simply changed the email address to

Will this suffice?
if you are not using it then why not remove it from the policies.
EncamsAuthor Commented:
What would happen if I were to delete that recipient policy completely?

It is currently # 1 in the policies list.

Would anything else be affected?
how many policies do you have?
are the other domain names also configured in this policy or do you have seperate policies for the other 2 domains
EncamsAuthor Commented:

Separate policies for each domain name, so only is in the top one.

Safe to delete then!
EncamsAuthor Commented:

Policy deleted, tried sending an email to and still get the same error:

Your message did not reach some or all of the intended recipients.
Subject: test to dom3
Sent: 23/03/2006 09:53
The following recipient(s) could not be reached: on 23/03/2006 09:53
  The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
  <mail.encams.local #5.1.1>

I have re-applied the remaining policies.
is this a mix mode setup (exchange 5.5 and exchange 200x)? or just pure exchange 200x

lower the priority of this policy so that the other two (domain1 and domain2) are set as priority 1 and 2 or priority 2 and 1.

make sure that you have not configured any thing else in the policy for like FAX addresses or any custom address.

the delete the policy

wait for replication or restart the exchange services
EncamsAuthor Commented:

Tricky to restart services during the day. Can I force replication now?

(no mixed mode by the way)

how many servers?

you can force the AD replication.
EncamsAuthor Commented:
Just the one email server.

How can i force a replication please?
open AD sites and Services.
you will see your DC/GCs listed there.
click on NTDS Settings and on the right side you would see the replication connector
Right click on it and select replicate now

this would replicate the AD information between the Dcs/GCs

but the replication in exchange takes time as some information is cached in exchange configuration and metabase. for the exchagne part give it some time, like 30 minutes or so
EncamsAuthor Commented:
Thanks for your help, but alas, still no luck.

No change at all, same error.  It is as if it still has a record or a trace of in there somewhere.

Anything else I can try or look for?

i would suggest a restart of all the exchange services to flush the old information.

you can also check the settings in your existing policies whether the smtp address is present there

also has any configuration been done in the smtp virtual server settings or any smtp connector created or modified
How to configure the SMTP connector in Exchange 200x

When to create SMTP connectors in Exchange 2000 and later

How to install and to configure SMTP Connectors in Exchange 2000 Server
Do you have internal MX records for in DNS ?

Try this from a CMD box on your Exchange server:

set type=mx

It should show you where it wants to send the mail.
EncamsAuthor Commented:
Hi Lee.

NS Lookup resolves correctly to the external ip of

Could Exchange be caching dns lookups?

If it was, you would see it in NSLookup.  Maybe the address doesn't exist in , then.  How sure are you that it does.  I know you said the mail doesn't leave the server, but if the receiving server can't match the name when your server is negotiating with it, then the email wouldn't go anywhere.  Try a telnet session with the remote server.

telnet 25

see what happens.

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
EncamsAuthor Commented:
Hi again.

Our exchange server uses a local smarthost, it does not have direct internet access.

I can telnet out on port 25 to the smarthost and send a telnet email with no problems.

This is how I know the email is not leaving the server, as we are not seeing an incomming connection on the smarthost server from the Exchange server when trying to email

The plot thickens!
Is the smarthost entered into your Default Virtual Server, or an SMTP connector?  If it's an SMTP connector, you will need to add to its list of namespaces, unless it already has * in the list.
EncamsAuthor Commented:

If I goto the properties of the Default SMTP Connector, in the General tab, the smarthost is listed in there. Under the Address Space tab of the same properties window, I simply have a * entry for SMTP.
OKay, so everything's going through that.  I think the next thing I would try is to do an NSLOOKUP from the smarthost, to see where that thinks mail for should be going.
EncamsAuthor Commented:

The smarthost mx record lookup still looks to the internet on the correct ip, but as above, the smarthost is not seeing/getting a connection from the exchange server when sending email to

It's as if the email refuses to leave the local exchange server as there are traces or something still prompting the exchange server to think that it still manages email for !?

So, you definitely have no recipient policies containing this domain? Is the Default SMTP Virtual Server configured to use external DNS servers (Delivery/Advanced)?

Do you have Message Tracking enabled?
EncamsAuthor Commented:
Definately no recip pols left containing

Default SMTP Virtual Server uses the same smarthost, external dns servers part is empty. Worth me adding an internet-based dns server in there?

Bear in mind still, I don't think the email is getting this far (to the point of external/smtp delivery) ?

Alas, we have no message tracking in place.
EncamsAuthor Commented:
Pulling (whats left) of my hair out on this one now.

Can I create a virtual "something" so if Exchange sees an email address to it knows to send it out via the smarthost address?

I wouldn't add an external DNS server if the name is resolving correctly.  On the other hand, it would do no harm to try it for a few minutes, I guess.  I was just wondering if there was something already in there, it may be best to take it out, that's all.  I don't think you need the smarthost configured on the VS if it is also on the Connector, but this wouldn't give you a problem for just one domain.

I would try turning in message tracking, then you can see what happens to the message as it passes through various parts of the messaging path.
EncamsAuthor Commented:
Ok, message tracking on.

I get:

store drive: message submitted from store
message submitted to advanced queing
message submitted to categorizer
message categorized and queued for routing
non-delivered report (ndr) generated

Can I break that down further still?
No.  But that is exactly what you'd get for a badly-addressed internal mail.  So, it is definitely not leaving the server.

Is there anything interesting in the Event Logs on the Exchange server?
EncamsAuthor Commented:
Not a thing, eventwvr all looking healthy and normal, no traces of anything out of place.

Any workarounds or anything?
I think it's time for a restart of the Exchange services, I'm afraid.  You might try adding back into you Default Recipient Policy, and then removing it again, in case it got confused last time you removed it, or something.  But I wouldn't expect anything miraculous to happen.

You have no trace of in Active Directory Domains and Trusts?  Or in DNS Manager?
EncamsAuthor Commented:
Thanks for your help Lee, will reboot at 7AM (empty office!) and keep you posted.
Did the reboot fix it?  Was it as simple as that?
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

From novice to tech pro — start learning today.