Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

550 5.1.1 RESOLVER.ADR.ExRecipNotFound and IMCEAEX bounces after moving mail to Microsoft 365

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Replies and new messages bounce with "#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##", and the recipient looks like a long string that starts with IMCEAEX-. Microsoft's explanation is that the user's LegacyExchangeDN value changed, while a cache in Outlook or Outlook on the web still holds the old one. The fix for the admin is to add the old value to the user as an X500 proxy address. The fix for the user's cache is to remove the bad AutoComplete entry and type the full address again.

Mail moved by a PST import or a third-party migration tool is the case Microsoft names. Those methods can leave the old internal address on messages, so a reply goes to an address that no longer exists.

What the error means

Every recipient has an attribute called LegacyExchangeDN. Microsoft says the auto-complete cache in Outlook and in Outlook on the web (OWA) uses the value of that attribute to route email messages internally. If the value changes, the page says the delivery of email messages "may fail with a 5.1.1 NDR". The NDR (non-delivery report, or bounce) then shows the old value in the form of an IMCEAEX address. Microsoft's IMCEAEX page says the NDR "indicates that the user no longer exists in the environment". Read that as a statement about the old address, since the user can still have a working mailbox, which is why the steps below start by testing the real SMTP address.

Microsoft's page for Outlook in Microsoft 365 describes two linked symptoms. First, messages or meeting invitations bounce with an NDR that has the generating server's name and an IMCEAEX address. Second, AutoComplete misbehaves: the name fills in on the To line, but double-clicking it shows a dialog with wrong or missing information.

The same page lists three conditions behind it:

  • You reply to a message that was migrated from a personal folders (.pst) file or by a third-party migration tool.
  • The Outlook nickname cache (AutoComplete) contains a bad entry.
  • The Offline Address Book (OAB) is not updated or cannot be downloaded.

Microsoft adds that the issue occurs when a migration method does not correctly update the underlying X.500 distinguished name information for the original recipients, and says "The most common culprits in this scenario are .pst migrations."

Likely causes

Cause What you see How to confirm
LegacyExchangeDN changed for the user Bounce for an IMCEAEX address; the user exists The old DN from the NDR is missing from the user's proxy addresses
Reply to a migrated message (PST or third-party tool) Only replies to migrated mail bounce A newly typed full SMTP address works
Bad AutoComplete or nickname cache entry Same bounce when the name is picked from the list The bounce stops after the entry is removed and the address retyped
Offline Address Book not updated or not downloading Missing or wrong details when the name is double-clicked Follow Microsoft's Offline Address Book troubleshooting article (Step 4 below)

Prove the cause before changing anything

Start with the bounce text. If the recipient begins with IMCEAEX-, you are in the first row and the X500 fix applies. If not, go to the cache steps.

Next, test whether the user's real address works. Have the sender type the recipient's full SMTP address by hand, without picking from AutoComplete or replying to old mail. If that message is delivered, the mailbox is fine and the bad item is a cached address.

Then read the user's current proxy addresses without changing anything. In Exchange Online PowerShell:

Get-Mailbox -Identity jsmith | Select-Object -ExpandProperty EmailAddresses | Out-File -FilePath .\jsmith-addresses-before.txt

This writes every address in the EmailAddresses collection to the named file, one per line, so nothing is cut short on screen, and the file is your record for the change in Step 2. Open the file. If an X500 entry matching the old value is already there, the first row is not your cause.

Example (illustrative): after a migration, mail to jsmith@contoso.com.au bounces from a reply. The NDR recipient is IMCEAEX-_O=CONTOSO_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=jsmith@contoso.com.au. Apply Microsoft's replacements in order. The four underscores become slashes, the three "+20" become spaces, "+28" becomes an opening parenthesis and "+29" a closing one. That is 4 + 3 + 1 + 1 = 9 substitutions. After deleting the IMCEAEX- prefix and the trailing @contoso.com.au, the address is X500:/O=CONTOSO/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=jsmith.

Fix

Step 1: convert the NDR address. Microsoft's rules, applied to the recipient address in the NDR, are:

  • Replace any underscore (_) with a slash (/).
  • Replace "+20" with a blank space.
  • Replace "+28" with an opening parenthesis and "+29" with a closing parenthesis.
  • Delete the "IMCEAEX-" string.
  • Delete the "@mgd.domain.com" string (Microsoft's example). Here that is @contoso.com.au.
  • Add "X500:" at the beginning.

Other "+##" patterns are ASCII codes and must also be converted: "+2C" is a comma, "+2E" a period, "+3F" a question mark, "+40" an at symbol and "+5F" an underscore. Microsoft notes there may be other symbols that appear differently in the NDR, so check the result by eye before you use it.

Step 2: add the proxy address. First check that jsmith-addresses-before.txt from the read-only step holds the current addresses.

Disruptive step: the next command changes the user's proxy addresses, and a mistyped value does not fix the bounce. Use the @{Add=...} form. Assigning an array without it replaces all existing addresses, including the primary one.

Add the converted value without disturbing the existing ones, using the add syntax Microsoft documents for the EmailAddresses parameter:

Set-Mailbox -Identity jsmith -EmailAddresses @{Add="X500:/O=CONTOSO/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=jsmith"}

To back out, run the same command with Remove in place of Add, using the exact value you added:

Set-Mailbox -Identity jsmith -EmailAddresses @{Remove="X500:/O=CONTOSO/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=jsmith"}

Step 3: remove the bad AutoComplete entry.

Risk: selecting the X (or pressing the DELETE key) in the step below removes one suggestion from that user's list and nothing else. Microsoft's AutoComplete page says that if you later send that contact a new email, the entry is restored to the list. Do not empty the whole list for a user whose mailbox is in Exchange Online and who runs Outlook for Microsoft 365 Version 2202 or later: for that case Microsoft says only two sections of its AutoComplete article apply, "Enable the AutoComplete feature" and "Remove AutoComplete list entries one at a time". The "Empty Auto-Complete List" button belongs to the other cases in that article, so for older Outlook builds or mailboxes outside Exchange Online read that article first, and remember that emptying the list deletes every suggestion for that user.

Microsoft says to reset the nickname and AutoComplete caches in Outlook and, if the user replies to a migrated message, to type the whole address again. If AutoComplete fills in a name or address, select the X next to the entry (or press the DELETE key) to remove it, and type the full address by hand.

Step 4: check the Offline Address Book. Microsoft says to make sure the OAB is operating correctly and points to its OAB troubleshooting article for Microsoft 365. Changing OAB settings is outside the steps above.

Confirm the fix

Send a new test message from the same sender, replying to the migrated message that bounced. Check delivery in the recipient's mailbox. In the Exchange admin center, a message trace for the message shows its delivery status. Check the user's proxy addresses again and confirm the X500 entry is present exactly once. Ask the user to double-click the name in the To line: the contact card should now show full details. If the same sender still bounces after the proxy address is in place and the cache is cleared, compare the old value in the new NDR with the one you added. A single wrong character in the converted address leaves the bounce unchanged, and the shell will not warn you.

What to watch afterwards

  • Other users on the same migration batch. A method that does not update X.500 information affects every recipient in migrated mail, not only the first one reported.
  • New IMCEAEX bounces in the first days after each batch. Each new IMCEAEX value needs its own X500 address.
  • Reply bounces to old migrated messages. These return as users work through old mail.
  • The Offline Address Book not updating or failing to download, which is the cause Microsoft's page lists.
  • Meeting invitations. Microsoft lists them beside messages as items that fail with this NDR, so ask organisers whether invitations to the same people bounce.

Risks and limits

These commands have not been run or lab-tested. The IMCEAEX page shows an NDR address and the matching X500 result, and a short list of character replacements. It notes "The most common items will be replaced" and that other symbols may also change. It does not give a Set-Mailbox command, so the PowerShell syntax comes from the Set-Mailbox reference, which documents the @{Add=...; Remove=...} form for proxy addresses. The Set-Mailbox reference states the syntax of non-SMTP address types is not validated, so a wrong X500 value is accepted without error. The page also does not describe mail users or groups, only users, and it does not cover mailboxes still on-premises. The reference pages show no date.

Sources