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

Issues removing an SMTP Domain from Exchange on SBS 2003

I have a client that has multiple email domains, 123.com and 456.com for example.  The SBS Exchange server was receiving email for both domains and there were no issues.  Now I have moved the 456.com email domain to a hosted Exchange solution.

I have gone into the SBS 2003 server manager and removed the 456.com smtp domain from the default recipient policy and then gone into each individual mailbox and removed the @456.com smtp address from each.  I have changed the MX records to point to the new hosted Exchange server.

If email is sent from the Exchange 123.com domain to 456.com on the new hosted exchange server, the sender receives and NDL receipt stating that the user does not exist on the remote domain.  SPF and PTR records have been changed as well.

Help is desperately needed.  TOP POINTS given.
0
dkh4bf
Asked:
dkh4bf
  • 5
  • 3
1 Solution
 
madhatter5501Commented:
search the metabase.xml and look for any references to that domain, and remove them

http://forums.msexchange.org/m_1800436952/mpage_1/key_/tm.htm#1800497077
0
 
dkh4bfAuthor Commented:
I did find two entries referring to the old domain in the metabase.xml file, which I removed.  I restarted IIS, but am still having the same issue.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
dkh4bfAuthor Commented:
madhatter5501...

I followed the directions in the article posted and am still having the same issue.
0
 
madhatter5501Commented:
till you get to a resolution on this, try to make that domain an internal relay and point it to the hosted domain.  that will cause any lookups to happen internally, but when they don't find a match they will go look at the hosted domain.  its a bandaid, but it will get you working for now.
0
 
dkh4bfAuthor Commented:
After following the steps in the second article, I looked at the metabase.xml file and the 456.com domain entries are there again.  When I try to delete and save the file, I am told that I can't save it.  Any ideas?

How do I set up an internal relay like you are suggesting?

Thanks
0
 
dkh4bfAuthor Commented:
Can I delete the 456.com entries in the metabase.xml file using the IIS Metabase Explorer?
0
 
dkh4bfAuthor Commented:
I did delete the entries using the metabase explorer and that fixed the issue.  Thanks!  Points are yours!
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now