Thursday, June 13, 2024
HomeMicrosoft ExchangeAlternate 2016 – Non-Supply Report (NDR) «

Alternate 2016 – Non-Supply Report (NDR) «

A non-delivery report (NDR) isn’t a reason behind e-mail supply points, however does often present diagnostic info that helps with troubleshoot. At all times learn the NDR when one is out there. Many points reported in NDRs shall be server-related.

Nonetheless, the NDR might reveal a difficulty that’s extra more likely to be recipient-related.

One specifically deserves particular point out; the IMCEAEX non-delivery report. This NDR will happen when the LegacyExchangeDN attribute has modified for a recipient. A typical cause for the attribute altering is when a consumer has left the group, and their mailbox has been eliminated, after which they’ve later re-joined the group and had a brand new account and mailbox created with the identical identify and SMTP tackle.

When different customers within the group despatched e-mail to that recipient, an entry was added to their Outlook auto-complete cache. Auto-complete cache entries make the most of the LegacyExchangeDN attribute, which is at all times distinctive. When the brand new account and mailbox is created, a brand new LegacyExchangeDN worth is used, so the auto-complete cache entries not match.

There are two options to this drawback:

  • Clear the auto-complete cache entries for customers within the group. This answer doesn’t scale nicely, and is inconvenient for finish customers, so it isn’t beneficial.

  • Add an X500 tackle to the brand new mailbox for the previous LegacyExchangeDN worth.

For instance, the recipient tackle within the NDR resembles the next:


To create an X500 proxy tackle for the previous LegacyExchangeDN attribute for the consumer, make the next adjustments based mostly on the recipient tackle within the NDR:

  • Substitute any underscore character (_) with a slash character (/).

  • Substitute “+20” with a clean area.

  • Substitute “+28” with a gap parenthesis character.

  • Substitute “+29” with a closing parenthesis character.

  • Delete the “IMCEAEX-” string.

  • Delete the “” string.

  • Add “X500:” firstly.

After you make these adjustments, the proxy tackle for the instance within the “Signs” part resembles the next:


Notice The commonest gadgets shall be changed. Nonetheless, there could also be different symbols within the LegacyExchangeDN attribute that can even be modified from the best way that they seem within the NDR. Usually, any character sample of “+##” have to be changed with the corresponding ASCII image.

Ratish Nair

Microsoft MVP | Workplace Servers and Providers

Workforce @MSExchangeGuru

Depart a response, or trackback.



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments