asked on
Domain name no longer hosted locally, but Exchange does not try to deliver to remote server
Hi everyone,
Running Exchange Server 2003 with Service Pack 2. We had a domain called mydomain.com which was hosted in our organization. It was in the default recipient policy and several users had @mydomain.com smtp email addresses.
Mydomain.com now belongs to someone else who is hosting it at Google.
My problem is that despite deleting mydomain.com from the recipient policy (and rebuilding the RUS) Exchange is not attempting to deliver any messages to the foreign server, it is instead trying to deliver locally and therefore giving me error 5.1.1 "The e-mail account does not exist at the organization this message was sent to."
I know that mydomain.com is configured correct with regards to MX records etc... as they are able to receive mail from other sources without issue. Also, using nslookup indicates that the server is aware the mydomain.com's mail is hosted elsewhere. We are running GFI, but I don't think that it has anything to do with it (this time).
Any help would be appreciated. Thanks!
Running Exchange Server 2003 with Service Pack 2. We had a domain called mydomain.com which was hosted in our organization. It was in the default recipient policy and several users had @mydomain.com smtp email addresses.
Mydomain.com now belongs to someone else who is hosting it at Google.
My problem is that despite deleting mydomain.com from the recipient policy (and rebuilding the RUS) Exchange is not attempting to deliver any messages to the foreign server, it is instead trying to deliver locally and therefore giving me error 5.1.1 "The e-mail account does not exist at the organization this message was sent to."
I know that mydomain.com is configured correct with regards to MX records etc... as they are able to receive mail from other sources without issue. Also, using nslookup indicates that the server is aware the mydomain.com's mail is hosted elsewhere. We are running GFI, but I don't think that it has anything to do with it (this time).
Any help would be appreciated. Thanks!
Exchange
Last Comment
encoad
ASKER
Hi Simon,
I should have mentioned that I removed all of the @mydomain.com addresses from all the users in active directory using admodify.net
Thanks
I should have mentioned that I removed all of the @mydomain.com addresses from all the users in active directory using admodify.net
Thanks
ASKER
I'm bumping this up in points as I really need it resolved and it doesn't seem like a simple one...
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Hi Sembee,
You were right, it was still in the metabase. Once removed messages started to flow outside the organization without trouble. Before I award points and close this question, is this problem indicative of other problems in my enchange organization? I would normally expect the System Manager to remove the domains from the metabase when they are removed from the default recipient policy.
Thanks!
You were right, it was still in the metabase. Once removed messages started to flow outside the organization without trouble. Before I award points and close this question, is this problem indicative of other problems in my enchange organization? I would normally expect the System Manager to remove the domains from the metabase when they are removed from the default recipient policy.
Thanks!
If it was still in the metabase that would tend to indicate a problem with the server - the metabase isn't synchronising with the Exchange server. It isn't that simple to fix though... not for the faint hearted. There are instructions on Microsoft's web site on how to reset the sync, but the usual recommendation is a reinstall of IIS and Exchange.
Simon.
Simon.
ASKER
Thanks again!
Simon.