Bounce errors / 550 5.1.1 Microsoft 365 and Outlook

How do you fix Outlook error 550 5.1.1, recipient not found?

Microsoft 365 could not find the mailbox you addressed. Check the address first, then clear the old entry from your Outlook Auto-Complete list. If the address is right, the recipient's email admin has to look at their side.

  • Hard bounce
  • Who fixes it: You, then their admin
  • Try again: No
Start my free trial7-day free trial · $0 today
The exact message
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'

You see this when you email an Outlook.com address or a company that runs on Microsoft 365 or Exchange.

Here is how to read that message.

Each colour marks one part of the message, and the numbers match the notes underneath.

  1. 1
    The reply code550 is the server's answer. The 5 means permanent, so the same message will not get through later.
  2. 2
    The status code5.1.1 is the standard code for a bad destination mailbox address. Microsoft's own table lists it under that name.
  3. 3
    The Microsoft detailRESOLVER.ADR is the part of Exchange that matches an address to a recipient. RecipNotFound says it matched nothing.
  4. 4
    The plain wordsNot found. The address is not a mailbox in the recipient's organization.

There is another version of this message.

The words after the code are what separate one cause from another. Find yours.

The same error as Microsoft logs it for a mailbox it cannot match

550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found

Here is what the message means in plain words.

Microsoft 365 receives the message, looks the address up in the recipient's directory and finds nobody to deliver it to. Microsoft's documentation says this error happens when the sender typed the address wrong, when the address never existed in that system, or when it was valid once and has since been changed or removed.

There are two Microsoft-only twists. Outlook remembers addresses you have used in its Auto-Complete list, and a stale entry keeps failing even after the person's mailbox moved. And a recipient can have a forwarding rule that sends your message on to a second address that does not exist, which produces this same error for an address you typed correctly.

These are the usual reasons for it.

  • A typo in the address, or an address that was never valid.
  • An old entry in your Outlook Auto-Complete list (the nickname cache) that points at a mailbox that has moved.
  • The person's mailbox was deleted, or moved between on-premises Exchange and Microsoft 365.
  • A forwarding rule at the recipient's end that sends your mail on to a bad address.
  • A stale or doubled MX record on the recipient's domain.

Who has to fix it?

The blue card is the one that fixes it. A dashed card helps in some cases, and a grey card has nothing to do.

Your bounce says 550 5.1.1

You, the sender

Fixes it

You fix most of these: correct the address, and delete the old Auto-Complete entry.

The person you emailed

Sometimes

Only if a forwarding rule on their mailbox points to a bad address.

Their email admin

Sometimes

Their admin fixes stale MX records, bad forwarding and mail flow rules, and mailboxes that moved.

Follow these steps to fix it.

  1. Confirm the address.Microsoft calls a wrong address the most common cause. Check the spelling and the domain, and send again if you find a mistake.
  2. Remove the address from your Auto-Complete list.In Outlook, remove the entry from the Auto-Complete list. In Outlook on the web, start typing the name in a new message, highlight the suggestion with the arrow keys and press Delete. Then write a new message. Resending the old one repeats the failure.
  3. Compare the address in the bounce with the one you sent to.Check the message in your Sent Items. If the two addresses differ, the recipient has a rule forwarding your mail to another address that does not exist, and they need to correct or remove it.
  4. Check that you sent the message at all.Look through your Sent Items for messages you did not write. If you find none, the bounce is backscatter (a bounce for a message someone faked in your name) and you can ignore it. If you find some, change your password and tell your admin.
  5. Ask the recipient's admin if the address is certainly right.Reach the person another way and ask them to pass this to their email admin. The admin checks that the mailbox exists, that the domain has one correct MX record pointing at Microsoft 365, and that no forwarding or mail flow rule sends mail to a bad address.

Here is how to stop it from happening again.

You cannot see inside someone else's Microsoft 365 organization, but you can check an address before you write to it. A list that is checked first sends far fewer messages into a mailbox that is not there.

Your listCheck every addressSend to the good ones
Deliverable

The mailbox exists and accepts email. Keep it and send.

Risky: catch-all

The domain accepts every address. Send these in a smaller, separate batch.

Undeliverable

The mailbox can't receive email. Remove it before it bounces.

Unknown

The mail server did not answer in time. Check it again in a little while.

Free email checkerPaste an address and see whether it is deliverable, risky or undeliverable before you send.
Bulk email verifierCheck a whole list in one go and send only to the addresses that pass.
MX lookupSee whether a domain has mail servers at all.
Email finderLook a person up again to get the address they use today.

These errors look similar, and here is how they differ.

ErrorWhere you see itWhat it meansTry again?
550 5.1.1Microsoft 365 and OutlookThis page. Recipient not foundNo
550 5.1.1Gmail and Google WorkspaceThe email account does not exist.No
550 5.1.10Microsoft 365Recipient not found. The address lookup found no recipient.No
550 5.5.0Outlook.com and HotmailMailbox unavailable. The address was not found by the lookup.No
550 5.4.1Microsoft 365Recipient address rejected: access denied. The address does not exist.No

These are the questions people ask about this error.

What does RESOLVER.ADR.RecipNotFound mean?

The part of Exchange that matches an address to a recipient found nobody. In plain words the mailbox is not there, or not under that address.

Why does Outlook still bounce an address that I fixed?

Outlook can keep an old entry for that person in its Auto-Complete list and use it instead of what you typed. Delete the entry and write a new message.

Is 550 5.1.1 a permanent failure?

Yes. The 5 at the start means permanent, so waiting does not help. Something about the address or the recipient's setup has to change first.

Does this mean Microsoft blocked my domain?

No. A block shows a 5.7 code with words about policy, reputation or a block list. This error is about the address not being found.

What if only some of my emails to the same company bounce?

A company that has moved mailboxes or runs more than one mail system can answer differently for different people. Ask their admin to check the mailboxes that bounced and the domain's MX record.

Other bounce errors you may run into.

See every bounce error in one table

These are the sources behind this page.

The message wording and the fixes come from the providers' own documentation and from the RFC that defines the codes.

Stop writing to mailboxes that are gone.

Emailchaser finds email addresses, checks them and sends your cold emails from your own mailboxes.

Start my free trial7-day free trial · $0 today