troubleshooting Question

Domain name no longer hosted locally, but Exchange does not try to deliver to remote server

Avatar of encoad
encoad asked on
Exchange
7 Comments1 Solution213 ViewsLast Modified:
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!
ASKER CERTIFIED SOLUTION
Join our community to see this answer!
Unlock 1 Answer and 7 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros