Background: I have a customer which we migrated to Exchange 2013 SP1 from Exchange 2007 a while ago. The migration was done in a PST transfer manner with the import/export-pst cmdlets. The Exchange is running on a Win Server 2012 R2 VM on VMware ESX 5.5. Users use Outlook 2007 internally, as well as OWA and ActiveSync mobile externally. Let's call the domain contoso.com for security purposes.
Issue: Joe Doe is intermittently receiving NDR messages when sending/replying to internal emails to Maria Smith. Please note that Maria Smith was originally Maria White. The surname change happened BEFORE the migration, but this issue began AFTER the migration. The NDR is the following:
Diagnostic information for administrators: Generating server: EX.contoso.local IMCEAEX-_O=CONTOSO_OU=First+20administrative+20group_cn=Recipients_cn=maria+2Ewhite@contoso.com Remote Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found' Original message headers: Received: from EX.contoso.local (192.168.0.150) by EX.contoso.local (192.168.0.150) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 10 Dec 2014 16:33:14 +0100 Received: from EX.contoso.local ([::1]) by EX.contoso.local ([::1]) with mapi id 15.00.0847.030; Wed, 10 Dec 2014 16:33:14 +0100 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary
What we did so far:
- Cleared auto-complete cache in Outlook
Added the IMCEAEX address shown in the NDR as an X500 address alias in Maria Smith's mailbox. The resultant X500 address we used is:
/O=CONTOSO/OU=First administrative group/cn=Recipients/cn=maria.white
Removed the .NK2 cache file from the Outlook profile
Confirmed that Joe Doe's Outlook address book is updating properly...it is correct, I checked personally from his Outlook
Checked Maria's LegacyExchangeDN attribute in the current AD object...its a jumble of numbers and characters...but I found some people online which said that I can ignore this.
NB. I tried sending an email directly to that X500 address internally from Outlook to test, but it sees it as an invalid address...not sure if its normal behavior or because the structure of the address is wrong...
I've read countless blogs and posts of people with exactly the same issue...and they solve it immediately with the X500 alias method...it isn't working for me and it's driving me nuts. Any ideas?