550 is SMTP’s general permanent “no”: the receiving server will not take the message for this recipient, now or later. It covers two very different cases — the mailbox does not exist (usually with 5.1.1), or the server refuses the sender for policy reasons (5.7.1, 5.7.26 and the rest) — and the enhanced code after it says which.
| Code | 550 |
| Meaning | Requested action not taken: mailbox unavailable |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | RCPT most often; also MAIL, EHLO and the end of the message |
| What the sender does | Stops and returns the message to the sender |
| Defined in | RFC 5321, section 4.2 |
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
- The address does not exist at the destination — a typo, a stray space, a mailbox that was closed.
- The receiver’s policy refuses the sender: failed SPF, DKIM or DMARC, a blocklisted address, poor reputation, a malformed message.
- The server will not relay: the recipient’s domain is not one it handles.
What to do
- Read the enhanced code and the text after it — they name the reason, often with a link.
- For an unknown mailbox: check the address; if it is right, the mailbox is gone. Stop sending to it.
- For a policy refusal: fix what the text names — authentication, reverse DNS, a blocklisting — before sending again. Resending unchanged gets the same answer.
What each provider means by it
| Who | What they say |
|---|---|
| Gmail | 550 5.1.1 for an address that does not exist; 550 5.2.1 for an inactive account; 550 5.7.1 for policy and reputation; 550 5.7.24 to 5.7.30 for sender-requirement failures — SPF, reverse DNS, DKIM, TLS. |
| Microsoft 365 | 550 5.1.1 to 5.1.20 for recipients that cannot be found; 550 5.7.1 for “not authorized”, “unable to relay” and “client was not authenticated”; the 5.7.5xx family for its anti-spam blocks, such as 5.7.509 for a DMARC reject. |
| Outlook.com | Codes such as 550 SC-001 (reputation) and DY-001 (dynamic address) in the text; 550 5.7.515 since 5 May 2025 for high-volume senders that fail SPF, DKIM and DMARC. |
| Yahoo | Lists 550 among its “other policy errors” — a null MX, a header too big, a date out of range. Do not retry a 5xx, it says. |
| Postfix | The default for unknown recipients (unknown_local_recipient_reject_code and its siblings). |
| Exim | Uses 550 whenever an access list denies. |
Bounces with this code
- Gmail 550 5.7.26: unauthenticated email is not accepted due to the domain’s DMARC policy
- Gmail 550 5.7.27: the message didn’t pass SPF authentication
- Gmail 550 5.7.30: the message didn’t pass DKIM authentication
- Gmail 5.7.32: the From header isn’t aligned with the SPF or DKIM domain
- Gmail 550 5.7.40: the sending domain doesn’t have a DMARC record
- Gmail 550 5.7.25: the sending IP address doesn’t have a PTR record
- Gmail 550 5.7.24: the SPF record has one or more suspicious entries
- Gmail 550 5.7.29: the message wasn’t sent over a TLS connection
- Gmail 550 5.7.28 and 421 4.7.28: an unusual rate of unsolicited email
- Gmail 550 5.7.1: very low reputation of the sending IP address or domain
- Gmail 550 5.7.1: the message does not meet IPv6 sending guidelines
- Outlook 550 5.7.515: the sending domain does not meet the required authentication level
Worth knowing
A server may refuse an unknown recipient with 550 and no address information, rather than 551 with the new address.
Related: 5.1.1, 5.7.1, 554, 450, 5.7.26.
Questions
Is a 550 bounce my fault?
It depends on the code after it. 5.1.1 means the recipient’s address does not exist — a problem with the address, not your server. 5.7.x means the receiver refused you as a sender — something about your domain, server or message.
Sources
Checked on 27 September 2026 against these official sources:
- RFC 5321: Simple Mail Transfer Protocol — rfc-editor.org
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- Gmail SMTP errors and codes — knowledge.workspace.google.com
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — learn.microsoft.com
- Outlook.com postmaster: troubleshooting and SMTP error codes — sendersupport.olc.protection.outlook.com
- SMTP Error Codes — senders.yahooinc.com
- Postfix Configuration Parameters — postfix.org
- 44. Access control lists — exim.org