Looks like it might be a LegacyExchangeDN (LEDN) issue, in that Outlook has cached the LEDN value of the old mailbox, and is still trying to send to that cached address. Try and clear the Outlook (NK2) cache entry for this user (ie: when the name comes up in the auto-complete, hit your delete key to clear it out of the cache), then manually type in the smtp address. Another option would be if you have (or create) a new contact object for this individual in your org, in place of the old mailbox, and add the old LEDN of the mailbox as an x500 address to the new contact object. By doing this, you will preserve the ability to reply to older emails that have been stored with the old LEDN, and negate the need to clear the cached entry for all your users.-Matt

Dear anyone who can help, yesterday i moved a domain from my company to another company in another state. i used to handle the email for these people but we sold the company and now they will handle the email. i use exchage 2007. i transfered the domain and they made the IP changes and setup the email for them. i deleted the user from my server, AD and removed them from the global address book. but now why we try and send him email i get an error back... Diagnostic information for administrators: Generating server: Exchangeserver.hudsoncompanies.int IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=BDixon@hudsoncompanies.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Original message headers: Received: from Exchangeserver.hudsoncompanies.int ([127.0.0.1]) by exchangeserver ([127.0.0.1]) with mapi; Fri, 31 Aug 2012 09:24:29 -0400 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: Don Lancellotta <DLancellotta@hudsoncompanies.com> To: Bradford Dixon <IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=BDixon@hudsoncompanies.com> Date: Fri, 31 Aug 2012 09:24:28 -0400 Subject: test Thread-Topic: test Thread-Index: Ac2He/J0lFPTi9MfQxaoWrNIRBskFw== Message-ID: <7BE522909BCBCA4DBD8911DD000AF21B12A525F871@exchangeserver> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <7BE522909BCBCA4DBD8911DD000AF21B12A525F871@exchangeserver> MIME-Version: 1.0 any help on how to fix this?

Do you still have a forward lookup zone for this domain in your internal DNS? You may still have an MX record pointing to your own server.Mobile OWA For Smartphone www.leederbyshire.com email a@t leederbyshire d.0.t c.0.m

Looks like it might be a LegacyExchangeDN (LEDN) issue, in that Outlook has cached the LEDN value of the old mailbox, and is still trying to send to that cached address. Try and clear the Outlook (NK2) cache entry for this user (ie: when the name comes up in the auto-complete, hit your delete key to clear it out of the cache), then manually type in the smtp address. Another option would be if you have (or create) a new contact object for this individual in your org, in place of the old mailbox, and add the old LEDN of the mailbox as an x500 address to the new contact object. By doing this, you will preserve the ability to reply to older emails that have been stored with the old LEDN, and negate the need to clear the cached entry for all your users.-Matt