# 550 5.1.10: recipient not found (Microsoft 365)

URL: https://iblockspam.com/smtp-errors/550-5-1-10
Last updated: 2026-10-09

Code: 550 5.1.10 (permanent failure, the message bounced)
Provider: Microsoft 365 / Outlook.com

Microsoft 365 couldn't find the recipient's address. It's usually a typo or an old address, but it can also be backscatter from mail you never sent.

Microsoft's NDR reference describes 5.1.10 as "Recipient not found": SMTP address lookup didn't find the recipient's address. It also lists 550 5.5.0 "Requested action not taken: mailbox unavailable" for hotmail.com and outlook.com addresses that aren't found, and calls it similar to 550 5.1.10.

Note that the standard meaning of X.1.10 is different. In the IANA registry, X.1.10 means "Recipient address has null MX", used with reply code 556. Microsoft uses 5.1.10 for a recipient that doesn't exist. Read the text to know which you have.

Microsoft's article gives two reasons. Either the recipient's address doesn't exist or couldn't be found, or you're seeing backscatter: a spammer sent mail to a non-existent address with your address forged as the sender, and the bounce came to you. Microsoft says backscatter is harmless and can be deleted, but if you get a lot, run an anti-malware scan and ask your admin to set up SPF. For real messages, check the address, clear the Auto-Complete entry, and ask the recipient to check forwarding rules.

## Common causes

- A typo or outdated recipient address.
- A bad entry in your Outlook Auto-Complete list.
- The recipient's forwarding rule sends to an address that doesn't exist.
- The recipient's mailbox doesn't exist or has no license.
- Backscatter: your address was forged on spam sent to invalid recipients.

## How to fix it (sender)

- Check the address and resend it typed fresh, after deleting the Auto-Complete entry.
- Compare the address in the NDR with the one you sent to. If they differ, the recipient has a forwarding rule to fix.
- If you never sent the original, treat it as backscatter.

## How to fix it (recipient or admin)

- Confirm the recipient exists and has an active license.
- Review inbox rules and account forwarding that may send to a broken address.

**Q: I got a 550 5.1.10 for an email I didn't send. Was I hacked?**
Usually not. Microsoft explains this is often backscatter: a spammer forged your address on mail to a non-existent recipient. Check your Sent folder; if it's clean, delete the bounce. If you get many, scan for malware and make sure your domain has SPF.

**Q: Is Microsoft's 5.1.10 the same as the standard 5.1.10?**
No. The IANA registry defines X.1.10 as a recipient domain with a null MX (with reply code 556). Microsoft uses 5.1.10 for a recipient address it can't find.

Sources:
- Fix NDR error "550 5.1.10" in Exchange Online (Microsoft Learn): https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/fix-error-code-550-5-1-10-in-exchange-online
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online (Microsoft Learn): https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/non-delivery-reports-in-exchange-online
- IANA: SMTP Enhanced Status Codes registry: https://www.iana.org/assignments/smtp-enhanced-status-codes/smtp-enhanced-status-codes.xhtml

---

Source: iBlockSpam, https://iblockspam.com/smtp-errors/550-5-1-10 (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt