By the registry, 5.1.10 means the recipient’s domain says it accepts no mail (a null MX). Microsoft 365 uses it for “Recipient not found” — the address does not exist there. Which one you have depends on who sent the bounce.
| Code | 5.1.10 |
| Meaning | Recipient address has null MX |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | With 556 (the registry’s use) or 550 (Microsoft’s) |
| What the sender does | Returns the message at once |
| Defined in | RFC 7505 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What causes it
- From Microsoft 365: the recipient address does not exist — or the bounce is backscatter, from a message a spammer sent in your name.
- Elsewhere: the recipient’s domain publishes “MX 0 .”, taking no mail.
What to do
- Check the recipient address.
- If you never sent the message, it is backscatter: tighten SPF, DKIM and DMARC so fewer receivers accept forgeries of your domain.
What each provider means by it
| Who | What they say |
|---|---|
| Microsoft 365 | 5.1.10 Recipient not found — SMTP address lookup did not find the recipient. |
| Postfix | Answers 556 5.1.10 when the recipient’s domain has a null MX. |
Sources
Checked on 27 September 2026 against these official sources:
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- RFC 7505: A “Null MX” No Service Resource Record for Domains That Accept No Mail — rfc-editor.org
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — learn.microsoft.com
- Fix NDR error 550 5.1.10 in Exchange Online — learn.microsoft.com
- Postfix Configuration Parameters — postfix.org