dkh4bf
asked on
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
madhatter5501
http://www.msexchange.org/tutorials/fixing-damaged-incorrectly-configured-owa-2003-installation.html
ASKER
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.
ASKER
madhatter5501...
I followed the directions in the article posted and am still having the same issue.
I followed the directions in the article posted and am still having the same issue.
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.
ASKER
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
How do I set up an internal relay like you are suggesting?
Thanks
ASKER
Can I delete the 456.com entries in the metabase.xml file using the IIS Metabase Explorer?
ASKER
I did delete the entries using the metabase explorer and that fixed the issue. Thanks! Points are yours!