Fix 550 5.1.10 RESOLVER.ADR.RecipientNotFound in Exchange Online & Hybrid Mail Flow

One of the most frequent Non-Delivery Reports (NDRs) encountered in Exchange Online and Exchange Server SE / 2019 Hybrid deployments is:

550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup

This bounce occurs when Exchange Online's Transport Categorizer receives an email destined for an Authoritative Accepted Domain (or a misconfigured Internal Relay domain) and cannot match the recipient's SMTP address—or legacy IMCEAEX (LegacyExchangeDN) address—to any object in Microsoft Entra ID / Exchange Online Directory (EXODS).


Root-Cause Diagnostic Flowchart (550 5.1.10)

Diagnosing 550 5.1.10 RESOLVER.ADR.RecipientNotFound Cause 1: Hybrid Domain Type On-prem mailbox not synced to Entra ID & domain is set to Authoritative in EXO. Fix: Sync user or InternalRelay Cause 2: Missing x500 / Alias Outlook AutoComplete cache sends to stale IMCEAEX / LegacyExchangeDN after mailbox recreation. Fix: Add x500 proxyAddress Cause 3: Missing TargetAddress Cloud-to-OnPrem routing loop or missing mail.onmicrosoft.com routing address on hybrid RemoteMailbox. Fix: Enable-RemoteMailbox Directory Based Edge Blocking (DBEB): When a domain is Authoritative in Exchange Online, DBEB rejects any address not present in Entra ID at the EOP edge.

Scenario 1: The Bounce Contains an IMCEAEX-_O=... Address (Missing x500 Proxy Address)

If a user's mailbox was deleted and recreated (or migrated across forests), internal senders replying from their Outlook Auto-Complete cache (Nickname cache) send to the old LegacyExchangeDN, which Exchange converts into an IMCEAEX-... string.

PowerShell Script: Convert IMCEAEX String to a Valid x500: Address

POWERSHELL
function ConvertFrom-ImceaexToX500 {
    param([Parameter(Mandatory)][string]$ImceaexAddress)

    # Strip IMCEAEX- prefix and @domain suffix
    $Clean = $ImceaexAddress -replace '^IMCEAEX-', '' -replace '@.*%%%CODEBLOCK_1%%%#39;, ''

    # Decode standard IMCEAEX character escapes
    $Clean = $Clean -replace '_', '/' `
                    -replace '\+20', ' ' `
                    -replace '\+28', '(' `
                    -replace '\+29', ')' `
                    -replace '\+2C', ',' `
                    -replace '\+2E', '.' `
                    -replace '\+3F', '?' `
                    -replace '\+40', '@'

    return "x500:$Clean"
}

# Example usage:
$X500 = ConvertFrom-ImceaexToX500 -ImceaexAddress "IMCEAEX-_O=EXO_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=a1b2c3d4@lab365.in"
Write-Host "Add this proxyAddress to the user: $X500" -ForegroundColor Green

Once generated, add the x500: address to the user's EmailAddresses in Exchange Online (or on-premises AD if Directory Synced):

POWERSHELL
# Cloud-only mailbox:
Set-Mailbox -Identity "[email protected]" -EmailAddresses @{Add = $X500}

# Hybrid AD-synced mailbox (run in on-prem Exchange Management Shell):
Set-RemoteMailbox -Identity "[email protected]" -EmailAddresses @{Add = $X500}

Scenario 2: Hybrid Mail Flow Fails Between Exchange Online & On-Premises Exchange SE

If an on-premises mailbox is not yet synchronized to Entra ID via Entra Connect, or if you route shared domains across third-party hosts, verify whether the Accepted Domain in Exchange Online is set to Authoritative or InternalRelay:

POWERSHELL
Connect-ExchangeOnline -ShowBanner:$false

# Check Accepted Domain type
Get-AcceptedDomain | Select-Object Name, DomainName, DomainType, Default

# Check if the recipient exists in Exchange Online Directory (EXODS)
Get-EXORecipient -Identity "[email protected]" -ErrorAction SilentlyContinue |
    Select-Object DisplayName, RecipientTypeDetails, PrimarySmtpAddress, ExternalEmailAddress

If the user was created directly in on-premises Active Directory instead of via New-RemoteMailbox, run Enable-RemoteMailbox on-premises so Entra Connect syncs the proper RemoteRoutingAddress ([email protected]). For details on hybrid recipient flags, see our msExchRemoteRecipientType Reference Guide.