Critical ErrorSMTP Error · Permanent (5.x.x)
550 5.1.10

Recipient not found (Microsoft 365 / Outlook)

A 550 5.1.10 bounce from Microsoft 365 or Outlook.com says "Recipient not found". Microsoft looked up the address and no mailbox has it.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.1.10 Recipient not found (Microsoft 365 / Outlook)
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

550 5.1.10 is a permanent SMTP reply meaning recipient not found (microsoft 365 / outlook). Microsoft explains that the SMTP address lookup did not find the recipient. For @outlook.com and @hotmail.com addresses the same problem can appear as 550 5.5.0 "Requested action not taken: mailbox unavailable".

What 550 5.1.10 means

Microsoft explains that the SMTP address lookup did not find the recipient. For @outlook.com and @hotmail.com addresses the same problem can appear as 550 5.5.0 "Requested action not taken: mailbox unavailable".

⚠️
This is a 5.x.x permanent failure — the message will keep bouncing until you fix the cause. Retrying the same message unchanged won't help.

Common causes

📨
#1

The address is wrong or no longer exists

Most common

A typo, or a person who left the company and whose mailbox was removed.

🔁
#2

Your list has old or guessed addresses

Common

Pattern-guessed or bought lists produce many 5.1.10 bounces at once, which also hurts your sender reputation.

⚙️
#3

The recipient domain moved to Microsoft 365 but the user was not set up

Less common

The domain points its MX at Microsoft, but this address was not created there.

How to fix 550 5.1.10

  1. 1

    Check the exact address

    Confirm the spelling with the recipient, or find a current address another way.

  2. 2

    Remove the address from your list

    Do not retry. Suppress it so you do not send to it again.

  3. 3

    Verify lists before large sends

    A high rate of 5.1.10 bounces is a reputation problem. Verify addresses before a campaign, especially guessed ones.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check