Opens in a new tab

SMTP 550: mailbox unavailable — what it means and the fix

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.

Code550
MeaningRequested action not taken: mailbox unavailable
KindPermanent failure — the sender gives up
Sent in reply toRCPT most often; also MAIL, EHLO and the end of the message
What the sender doesStops and returns the message to the sender
Defined inRFC 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

WhoWhat they say
Gmail550 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 365550 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.comCodes 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.
YahooLists 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.
PostfixThe default for unknown recipients (unknown_local_recipient_reject_code and its siblings).
EximUses 550 whenever an access list denies.

Bounces with this code

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:

See every bounce before your customers do

Add your domain and send us a test message: we show what a receiving server saw — authentication, reverse DNS, blocklists, TLS — and monitor the servers you send from for blocklistings every day. Free for your first domain.

Create a free account