Close Menu
Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Facebook X (Twitter) Instagram
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    • Home
    • Intune
    • Windows
      • Modern Workplace
    • macOS
    • Android
    • iOS
    • Automation
      • Logic Apps
      • Intune Monitoring
      • GitHub
    • Security
      • Passwordless
      • Security
    • Speaking
    • About me
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Home»Exchange Online»Exchange Error: 550 5.1.1 RESOLVER.ADR.ExRecipNotFound
    Exchange Online

    Exchange Error: 550 5.1.1 RESOLVER.ADR.ExRecipNotFound

    Peter KlapwijkBy Peter KlapwijkFebruary 27, 2017Updated:December 3, 2019113 Mins Read

    Sometimes you have a reason to restore a mailbox from back-up, because it was deleted by mistake or a former employee is hired again. But after restoring the mailbox, several (internal) users are not able to send email to the restored mailbox and receive an error message like: Delivery has failed to these recipients or groups. With the error code IMCEAEX #550 5.1.1 RESOLVER.ADR.ExRecipNotFound ##
    In other Exchange versions the message also contains Recipient not found by Exchange Legacy encapsulated email address lookup.
    (This message could also show up after migrating the mailbox to another forrest)

    Exchange diagnostics

    Exchange diagnostics

    The first thing you probably think of to resolve the issue, is to delete the cached email address from Outlook, but that did not resolve the error message.

    Outlook

    We just created a new account, with an old, restored mailbox, maybe we need to restart the MS Exchange Active Directory Topology service (or even the Exchange server). In this case, that did not work either.

    Services

    So what is the solution to this problem!? I was pointed at this blog (credits to the writer of that blog!). It was the same error code we received, but not the exact same message (Recipient not found by Exchange Legacy encapsulated email address lookup is missing from our message) but that makes no difference. It pointed me in the right direction, the LegacyExchangeDN was changed since we created a new account/ restored the mailbox and was not associated with the new account.

    Attribute editor

    Exchange internally still uses an X.500 addressing schema. So when an user sends an email internally to the restored mailbox, the old X.500 address is used and therefor Exchange is not able to deliver the email. The user who send the email receives a Non Delivery Report (NDR) with the old ID in the form of a IMCEAEX address.

    Exchange error code

    We are able to rebuild the required X.500 address based on the received IMCEAEX in the NDR by using a PowerShell script.
    Copy below PowerShell scipt:

    $Direction = Read-Host “Ingrese IMCEAEX”
    $Remplazo= @(@("_","/"), @("\+20"," "), @("\+28","("), @("\+29",")"), @("\+2C",","), @("\+3F","?"), @("\+5F", "_" ), @("\+40", "@" ), @("\+2E", "." ))
    $Remplazo | ForEach { $Direccion = $Direccion -replace $_[0], $_[1] }
    $Direccion = “X500:$Direccion” -replace “IMCEAEX-“,”” -replace “@.*$”, “”
    Write-Host $Direction

    Open PowerShell ISE and past the script.

    Powershell code

    Click on the Play button to run the script and it will now ask you to enter the IMCEAEX, which you received in the NDR. It starts with IMCEAEX and ends with the domainname. 

    Powershell code

    Paste it in the PowerShell window and press ENTER. You now receive the X.500 address.

    The last step is to enter the received X.500 address to the restored mailbox. You can do that by opening the user account from ADUC, on the Attribute Editor tab go to proxyaddress.

    Attribute editor

    Click on Edit and paste the X.500 address in the Value to add box, click on Add and OK (twice)

    Multi-valued String editor

    It is also possible to add the X.500 address to the mailbox by using the Exchange; In Exchange 2010 you can use the Exchange Management Console. In Exchange 2013 and 2016 you can use ECP.
    On the e-mail addresses tab you enter the X.500 address (below is a print screen from Exchange 2010)

    Exchange user properties

    Your subtitle here

    After adding the X.500 address, we are now able to send internal e-mail to the restored mailbox!

    Exchange Online PowerShell
    Share. Facebook Twitter LinkedIn Email WhatsApp
    Peter Klapwijk
    • Website
    • X (Twitter)
    • LinkedIn

    Peter is a Security (Intune) MVP since 2020 and is working as Modern Workplace Engineer at Wortell in The Netherlands. He has more than 15 years of experience in IT, with a strong focus on Microsoft technologies like Microsoft Intune, Windows, and (low-code) automation.

    Related Posts

    Manage Internet Explorer settings with Intune – Part 2

    March 26, 2018

    Exchange Server 2007 end of life on April 11th

    March 1, 2017

    Conditional Access in the new Azure portal

    December 22, 2016
    View 11 Comments

    11 Comments

    1. Dean on April 10, 2017 15:39

      There are some minor syntax issues with the script. Try this one instead:

      $Direction = Read-Host “ENTER IMCEAEX”
      $Replacement= @(@(“_”,”/”), @(“\+20”,” ”), @(“\+28”,”(“), @(“\+29”,”)”), @(“\+2C”,”,”), @(“\+3F”,”?”), @(“\+5F”, “_” ), @(“\+40”, “@” ), @(“\+2E”, “.” ))
      $Replacement | ForEach { $Direction = $Direction -replace $_[0], $_[1] }
      $Direction = “X500:$Direction” -replace “IMCEAEX-“,”” -replace “@.*$”, “”
      Write-Host $Direction

      Reply
      • Niklas on April 30, 2020 09:28

        That’s correct, alternatively you can build that X500-Address on your own:

        https://docs.microsoft.com/de-de/exchange/troubleshoot/mail-delivery/imceaex-ndr

        Reply
    2. Peter on April 20, 2017 08:43

      Thanks Dean! I see WordPress screws up the script 🙁
      I need to figure out how to change this on the blog, but will change it.

      Reply
    3. Cosmin on August 10, 2017 11:54

      Thank you! Very good stuff, you saved my bacon!

      Reply
    4. Florian on October 25, 2017 13:40

      Thank you.
      Saved my life!

      Reply
      • Peter on November 2, 2017 20:39

        You`re Welcome!

        Reply
    5. Todd on December 20, 2017 23:07

      Great post! It worked! 🙂

      Reply
    6. Pierre Wong on September 11, 2018 11:01

      Thank you!!
      Very useful 🙂

      Reply
    7. Marjan Mrak on October 9, 2019 14:21

      I didn’t noticed script correction in comments. 🙂 So I had to figure it out myself. You saved my behind, too!

      Reply
    8. Saeid on February 6, 2020 01:48

      Great post! saved my life 🙂
      Thank you!

      Reply
      • Peter Klapwijk on February 6, 2020 13:43

        You`re welcome! 🙂

        Reply
    Leave A Reply Cancel Reply

    Peter Klapwijk

    Hi! Welcome to my blog post.
    I hope you enjoy reading my articles.

    Hit the About Me button to get in contact with me or leave a comment.

    Awards
    Sponsor
    Latest Posts

    Update Windows Defender during Windows Autopilot enrollments

    May 16, 2025

    Hide the “Turn on an ad privacy feature” pop-up in Chrome with Microsoft Intune

    April 19, 2025

    How to set Google as default search provider with Microsoft Intune

    April 18, 2025

    Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs

    April 13, 2025
    follow me
    • Twitter 4.8K
    • LinkedIn 6.1K
    • YouTube
    • Bluesky 1.5K
    Tags
    Administrative Templates Android Automation Autopilot Azure Azure AD Browser Conditional Access Edge EMS Exchange Online Feitian FIDO2 Flow Google Chrome Graph Graph API Identity Management Intune Intune Monitoring iOS KIOSK Logic Apps macOS MEM MEMMonitoring Microsoft 365 Microsoft Edge Microsoft Endpoint Manager Modern Workplace Office 365 OneDrive for Business Outlook Passwordless PowerApps Power Automate Security SharePoint Online Teams Windows Windows 10 Windows10 Windows 11 Windows Autopilot Windows Update
    Copy right

    This information is provided “AS IS” with no warranties, confers no rights and is not supported by the authors, or In The Cloud 24-7.

     

    Copyright © 2025 by In The Cloud 24-7/ Peter Klapwijk. All rights reserved, No part of the information on this web site may be reproduced or posted in any form or by any means without the prior written permission of the publisher.

    Shorthand; Don’t pass off my work as yours, it’s not nice.

    Recent Comments
    • Adam on Get notified on expiring Azure App Registration client secrets
    • Peter Klapwijk on Update Windows Defender during Windows Autopilot enrollments
    • Rob van de Ven on Add a certificate to the Trusted Publishers with Intune without reporting errors
    • Carl on Update Windows Defender during Windows Autopilot enrollments
    • Peter Klapwijk on The next step in a passwordless Windows experience
    most popular

    Application installation issues; Download pending

    October 1, 2024

    Restrict which users can logon into a Windows 10 device with Microsoft Intune

    April 11, 2020

    How to change the Windows 11 language with Intune

    November 11, 2022

    Update Microsoft Edge during Windows Autopilot enrollments

    July 9, 2024
    Peter Klapwijk – In The Cloud 24-7
    X (Twitter) LinkedIn YouTube RSS Bluesky
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.

    Manage Cookie Consent
    To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
    View preferences
    {title} {title} {title}