Windows Small Business Server 2003, latest service pack Exchange Server 2003, latest service pack We have moved our email services off of Exchange to a hosted solution elsewhere. Now I need to de-commission Exchange from thinking it is reponsible for sending and receiving email for the domain mydomain.com. Our internal AD domain is mydomain.lan and not mydomain.com. In Exchange I have verified the RUS and Recipient Policy is no longer issuing @mydomain.com email addresses. I have gone through AD and verified that no accounts are setup with @mydomain.com email addresses. We do not run a split DNS infrastructure so the MX record in the DNS for mydomain.com is correct. All email is flowing to the new hosted mail service, except for mail between the few accounts we have setup for Project Web Access, SharePoint, etc. Right now in AD I have setup each user that uses a mailbox at the new email host with an email address such as @sub.mydomain.com and all emails from PWA, SP, etc., are reaching the users just fine. What I want to do instead is setup each of these users in AD with an email address of @mydomain.com and have the email routed to the new mail host. This is not happening. Exchange is still trying to route these emails internally, and failing because I have already deleted those Exchagne mailboxes for the users who have moved to hosted email. There are no remaining AD accounts using @mydomain.com email addresses, they're all using @mydomain.lan, as is RUS and RP in ESM. In the IIS metabase file I do find several mentions of "mydomain.com". I do not know which ones to remove to see if this is what is causing mail failures when mail is sent to @mydomain.com recipients internally. I'm not even sure if I need to do this, I just came across some posts on msexchange.org that advised other people to do this and it worked for them. Please help? TIA

1- delete and zones for mydomain.com from your local dns 2-delete mydomain.com from the E-mail Address policy MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT

1 - As originally posted, "We do not run a split DNS infrastructure..." 2 - As originally posted, "In Exchange I have verified the RUS and Recipient Policy is no longer issuing @mydomain.com email addresses..." Whatever image you posted does not show up. It also seems that the "Alert me when someone responds to this post" option does not work either. I was never notified of any replies. Good job on this interface, too, MS. What a piece of junk. I am seeing this thread via http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/77150276-f5e1-4d1b-a102-02c6614cb1f5. I got here going through the microsoft.com Support site. I feel like I am in a black hole. How do I get back to the old Microsoft forums, where things actually worked and were readable?

Hi, Since we only discuss the Exchange issue on the pure Exchange product environment in this forum, I suggest you create a new thread in the SBS forum. Please understand that SBS Server has integrated all functionalities on a single box which will require the SBS related knowledge which we do not have enough resource. Thank you for your understanding. For your reference, I have enclosed the SBS forum link below: http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/threads Thanks, NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.