as per this thread http://forums.msexchange.org/m_1800512756/mpage_2/key_/tm.htm
i have a similar situation
but reading through to the last post, the issue was not confirmed as resolved with the last suggested method.
scenario is this:
company: domainabc.com was acquired and a new company rename was created in existing
infrastructure to domainxyc.com. same exchange servers were used so essentially new exchange policies were created to set
pri smtp as domainxyz.com with domainabc.com remaining as secondary smtp addresses.
Then the company split and
domainabc.com users were migrated off our infrastructure onto another totally independant network. they kept domainabc.com.
we kept domainxyz.com on the original exchange setup.
now users in domainxyz.com cant send emails to the external
organisation domainabc.com as emails dont route externally and return with a NDR: " The e-mail account does not exist at the
organization this message was sent to"
we have a exchange 2003 environment. 1x FE server, and 2x BE servers
so as per the link above, i've done the following:
- I made sure I removed all references for domainabc.com from
policies in system manager.
- used Metabase Explorer and removed references to that domains there
- Restarted IIS
(did the above on all 3 exchange servers rather than waiting for replication)
When that didnt resolve the
issue I created an smtp routing connector for domainabc.com and to point to the firewall IP of domainabc.com (reminder, this
is seperate to our network, so in theory i presume the smtp connections should route out to the internet and hit
domainabc.com fw). Restarted the exchange routing service and stop and started the smtp virtual server protocol in ESM – for
all exchange servers.
- then Restarted all Exchange Servers for good measure.
still getting the same
ND message and ESM tracking shows it doesnt even leave the local exchange server