Forum Discussion
IMCEAEX NDRs 50% solved - Exchange 2013
Hello, After DB corruption and re-creating two mailbox accounts, adding new X500 email address entries (based on email NDRs "mailto:" fields) and deleting cached contact information in outlook cl...
Based on many posts I've been reading, I modified the X500 entry by removing the "@smooth.com".
Before
/o=corp123/ou=Exchange Administrative Group (FYDIBOHF4141415)/cn=Recipients /cn=ABC@smooth.com
After
/o=corp123/ou=Exchange Administrative Group (FYDIBOHF4141415)/cn=Recipients /cn=ABC
Now the NDR emails shows the following 😞
/o=corp123/ou=Exchange Administrative Group (FYDIBOHF4141415)/cn=Recipients /cn=ABzC
User's DN appears to be OK within AD.
Any ideas?
Max
- marguelles, have you seen this kb?
https://support.microsoft.com/en-ca/help/4039597/ndr-when-delegate-sends-update-to-meeting-in-o365-hybrid
It might not be your exact scenario, but just imagine the big underlying theme is having some but not all recipients present in the local Exchange org where the ndr is being generated.
In my experience, Exchange servers add the @domain onto the end of the legacyExchangeDN / x500 when they can't find that recipient in the local directory. But the @domain only shows in the ndr, not on the actual ldn/x500 being searched for.
Not sure if this will help but figured I'd throw it out there just in case.Hi JeremyTBradshaw,
Apparently, the issue got resolved by removing the @domain.inc from the X500 entry!
Thanks for your answer!
Regards,- Glad it helped!
