Exchange Server 2003 - Removing second E-mail Domain

Posted on 2011-10-25
Last Modified: 2012-05-12
We have a Client wth the following conditions:

Three (3) Servers, all Wndows Server 2003 Enterprise.
Server A: PDC and GC
Server B: BDC, GC and Exchange 2003 Ent.
Server B: ERP and SQL

Recently, a consultant performed the following, in this exact order:
Installed Exchange 2003 Ent on Server A in preparation of decommissioning Server B entirely.
Demoted Server B, leaving Exchange intact.
Replicated "some" objects, but others apparently displayed as "local modified" on for Server A.
Moved all the mailboxes and Public folders (only had two), then closed down Server B. They did a few internal testing, and were satisfied. They then uninstalled Exchange 2003 from Server B and pulled the plug.
At one point in time, Server B hosted mail for two Domains: Domain A and Domain B. Domain B was purchased by an outside Company, and references on Server B were removed. They did have problems sending to recipients at Domain B for some time, but apparently got that corrected. Now, with only Server A running Exchange, they are again having problems sending to Users at Domain B. The error is as follows: on 10/24/2011 1:23 PM
            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.
            < #5.1.1>

As you can see, Server A is trying to locate the recipient that "use" to reside in this organization, but fails. The Recipient list looks ok, and the Domain only hosts mail for Domain A. Domain B is no longer there. However, we do "see" references in various public folder locations for Domain B. How do we remove those, get mail working again through to Domain B and clean up this mess in Exchange?

Question by:TPAMisfit
    LVL 20

    Expert Comment

    typically you need to rebuild the address books - on the server - and make sure they have been updated on the client.
    this can happen - even without the complications of the server move.

    for testing I prefer to use OWA, as this eliminates issues with my local address book not being updated. when OWA works then I move to the workstations.
    LVL 7

    Accepted Solution

    From your explanation, it looks like you have the Domain B hosted somewhere outside. If that the case, try creating an SMTP connector explicitly for and use external DNS to deliver the email. Ensure that the new server(Server A) is part of source server list.

    Also ensure that you Exchange Org is not responsible for email delivery of

    Under Recipients -> Recipient Policies -> properties of Default Policy(your email policy). check if the is there, then disable it and remove the authority for domainb and test the mail-flow.

    Also search in your AD for address, as you said it was working before AD should be fine.

    Keep a track of all changes you make, for an easy roll back..

    LVL 1

    Author Comment

    There do not appear to be any references to Domain B anywhere in the organization - not even for any deleted mailboxes, Recipient Policies, etc. But that is certainly how the system is responding to mail being sent to Domain B. It is as if it is looking "somewhere" and thnking it should be authoritative.

    Not sure how to rebuild the OAB using OWA. I can use OWA on the Server and use the "To" button and have it locate Users in the GAL. The GAL does not have any Users with an address from Domain B.

    LVL 1

    Author Closing Comment

    The E-mail Address tab was inexplicably "missing" in the Recipient Policy settings. Once we re-enable those pages, the reference to Domain B was located. Thanks a TON for the help.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Want to promote your upcoming event?

    Is your company attending an event or exhibiting at a trade show soon? Are you speaking at a conference? Spread the word by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

    Set OWA language and time zone in Exchange for individuals, all users or per database.
    Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
    In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
    In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    11 Experts available now in Live!

    Get 1:1 Help Now