Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Email delivery

Exchange bounce: 550 5.1.10 Recipient not found by SMTP address lookup

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

Short answer

The receiving Exchange organisation has no recipient with that SMTP address. Check the address and the sender's stale auto-complete entry first. If you run the recipient side, look for a missing licence, a broken forwarding rule, an authoritative accepted domain, or a cloud mailbox with no matching on-premises remote mailbox in a hybrid setup.

  • Applies to Exchange Online, Exchange Server 2016 and later hybrid
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Read the bounce and compare the address in it with the address you meant to send to. If they differ, a forwarding rule on the recipient side rewrote the target. If they match, find out who owns the recipient system and which of the causes below fits it.

    # Exchange Online PowerShell: does a cloud mailbox exist, and what is its ExchangeGuid?
    Get-Mailbox <MailboxName> | FL ExchangeGuid
  2. 2Match what you see, then jump to its fix

    1. 1The address in the bounce is exactly the one you sent to, and the recipient says it is spelled differently or was changed.The address is mistyped or comes from a stale auto-complete entryFix
    2. 2You administer the recipient's tenant, and the user exists in Active users but has no product licence with email.The recipient has no valid licence in Exchange OnlineFix
    3. 3The address in the bounce differs from the one the sender used.A forwarding rule sends the message to an address that does not existFix
    4. 4Hybrid setup: only recipients that exist on-premises and not in Exchange Online as a mail user or contact bounce with 5.1.10.The accepted domain is Authoritative but some recipients live on-premisesFix
    5. 5A Microsoft 365 user cannot send to on-premises users, or the on-premises side cannot resolve the cloud user, in an Exchange hybrid deployment.A user created in Microsoft 365 has no on-premises object (hybrid)Fix

What does the error look like?

  • 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
  • Remote Server returned '550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup'
  • User wasn't found at contoso.com

Cause 1 of 5

The address is mistyped or comes from a stale auto-complete entry

1Check

Open the bounce, choose Send Again, and compare the address letter by letter with what the recipient gave you. Outlook's auto-complete list can hold an old address that keeps coming back.

# Outlook: start typing the name in the To box and look at the drop-down entry

2Fix

Remove the address from the To box and from the auto-complete list (select it in the drop-down and press Delete), then type the full correct address and send again.

# No command: edit the To line in the new copy of the message

3Verify

The resent message is delivered and no new 5.1.10 bounce arrives.

# Check the Inbox for a bounce a few minutes later

Confirmed by learn.microsoft.com

Did this fix it?

Cause 2 of 5

The recipient has no valid licence in Exchange Online

1Check

In the Microsoft 365 admin center open Users, then Active users, find the user, and look at Product licenses. A mailbox hosted in Exchange Online needs a licence that includes email.

# Microsoft 365 admin center > Users > Active users > (user) > Licenses and apps

2Fix

Choose Edit on the licence section and assign a licence that includes Exchange Online. If the user does not exist at all, create the mailbox or a contact first.

# Microsoft 365 admin center: assign the licence, then save

3Verify

Ask the sender to resend. Confirm the recipient now resolves.

# Ask the sender to resend; the bounce no longer arrives

Confirmed by learn.microsoft.com

Did this fix it?

Cause 3 of 5

A forwarding rule sends the message to an address that does not exist

1Check

Three kinds of forwarding can rewrite the target: an Inbox rule the user made, account forwarding set on the mailbox, and an organisation mail flow rule that redirects. Look at all three for the recipient.

# Inbox rule: user's mailbox settings > Mail > Automatic processing > Inbox and sweep rules
# Account forwarding: admin center > Users > Active users > (user) > Mail Settings > Email forwarding
# Mail flow rule: Exchange admin center > Mail flow > Rules

2Fix

Correct the destination address or remove the rule. For account forwarding, turn Email forwarding off in the user's Mail settings. For a mail flow rule, edit or delete the redirect rule under Mail flow, Rules in the Exchange admin center.

# Exchange admin center > Mail flow > Rules: update, turn off or delete the redirect rule

3Verify

Resend a test message from the original sender.

# The message arrives in the recipient's Inbox

Confirmed by learn.microsoft.com

Did this fix it?

Cause 4 of 5

The accepted domain is Authoritative but some recipients live on-premises

1Check

With an Authoritative accepted domain, Exchange Online looks for the recipient in its own organisation and stops delivery if it is not there. With Internal Relay it passes unknown recipients to your on-premises organisation through a connector.

# Exchange admin center > Mail flow > Accepted domains > (recipient domain)

2Fix

If the domain is shared between cloud and on-premises and a connector to on-premises is already in place, set the domain to Internal Relay. The page warns that this changes routing, so set up the connector first: without it, mail to on-premises users stops.

# Accepted domains > (domain) > choose Internal Relay > Save

3Verify

Send to an on-premises recipient from a cloud mailbox.

# Send a test to an on-premises recipient from a cloud mailbox

Confirmed by learn.microsoft.com

Did this fix it?

Cause 5 of 5

A user created in Microsoft 365 has no on-premises object (hybrid)

1Check

If the user was created in the cloud, the on-premises Exchange environment has no object for that SMTP address, so every lookup fails. Read the cloud mailbox's ExchangeGuid.

Get-Mailbox <MailboxName> | Format-List ExchangeGuid

2Fix

Create a remote mailbox on-premises with the same name, alias and user principal name as the cloud mailbox, set its ExchangeGuid to the cloud value, then run directory synchronisation.

# Exchange Management Shell (on-premises)
Set-RemoteMailbox <MailboxName> -ExchangeGuid <GUID>
# On the Entra Connect Sync server
Start-ADSyncSyncCycle -PolicyType Delta

3Verify

Wait for sync, then confirm the user shows as Synced with Active Directory and mail flows.

# Admin center > Users > Active users: the user shows as Synced with Active Directory

Confirmed by learn.microsoft.com

Did this fix it?

How do I stop it coming back?

  • Give every cloud-created user in a hybrid setup a matching remote mailbox object, and let directory synchronisation finish before announcing the address.
  • Review forwarding rules, account forwarding and mail flow redirects when someone leaves, so no forward points at a deleted address.
  • Assign the licence at the same time as the user is created.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Related fixes

Email

Django send_mail fails or hangs with an SSL error

smtplib.SMTPException raised from send_mail()

Django has two secure modes that must not be mixed: EMAIL_USE_TLS for explicit TLS (STARTTLS, usually port 587) and EMAIL_USE_SSL for implicit TLS (usually port 465).

4 causes, each with a fix

Email

Mail from your own domain keeps landing in the spam folder

dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=example.com

Open a message that went to spam and read its Authentication-Results header: it shows whether SPF, DKIM and DMARC passed, and for which domain.

5 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.