Reference · 25 codes
SMTP bounce codes, explained
What each SMTP reply and enhanced status code means, what usually causes it, and whether to retry, suppress the address or fix your sending setup.
How to read a bounce code
550 5.1.1
A basic SMTP reply (550) followed by an enhanced status code (5.1.1).
- 5 Class
- Class. 2 = success, 4 = temporary failure, 5 = permanent failure.
- .1 Subject
- Subject. The area of the problem. 1 is the address, 2 the mailbox, 7 security or policy.
- .1 Detail
- Detail. The specific condition. 5.1.1 means the mailbox does not exist.
Permanent failures (5xx)
Definitive rejections. Suppress the address, or fix your sending setup when the cause is policy.
-
550 5.1.1SuppressUser unknown (mailbox does not exist)
The most common hard-bounce code. The receiving server has confirmed that no mailbox exists at this address.
-
550 5.7.1Fix reputationMessage rejected by policy (spam or content)
The message was rejected by the receiving server's policy engine, not because the mailbox is missing. It is usually a…
-
551 5.1.6SuppressMailbox has moved, no forwarding address
The mailbox previously existed at this address but has since moved (often due to a domain migration or account restructuring)…
-
552 5.2.2SuppressMailbox full (permanent quota failure)
Unlike the temporary 452 code, this is a permanent failure. Some mail servers escalate a mailbox that stays over quota, treating…
-
553 5.1.3SuppressInvalid mailbox name syntax
The receiving server rejected the address because its local part (before the @) does not follow that server's mailbox naming…
-
554 5.7.1Fix reputationTransaction failed (policy or reputation block)
A permanent, server-wide rejection tied to the reputation of the sending IP or domain, often because it appears on a blocklist.
-
554 5.4.6SuppressRouting loop detected (too many hops)
The message bounced between mail servers too many times, usually because of conflicting forwarding rules, and was rejected to…
-
550 5.7.26Fix reputationGmail: unauthenticated sender or DMARC failure
Gmail rejected the message because it failed authentication: neither SPF nor DKIM passed, or the message failed the DMARC policy…
-
550 5.7.25Fix reputationGmail: sending IP has no valid reverse DNS
Gmail rejected the message because the sending IP has no PTR record. Google requires every sender to have valid forward and…
-
550 5.2.1SuppressMailbox disabled
The mailbox exists but is disabled and not accepting messages. RFC 3463 defines X.2.1 as mailbox disabled. Gmail uses it for…
-
550 5.7.515Fix reputationOutlook.com: authentication level not met
Outlook.com rejected the message because the sending domain does not meet Microsoft's authentication requirements for high-volume…
-
550 5.7.509Fix reputationMicrosoft: DMARC failed, reject policy
Exchange Online rejected the message because it failed DMARC and the sending domain publishes p=reject. Microsoft is enforcing…
-
550 5.7.606Fix reputationMicrosoft: access denied, banned sending IP
Microsoft rejected the connection because the sending IP is on Microsoft's own blocklist. Codes 5.7.606 to 5.7.649 all mean the…
-
550 5.4.1SuppressMicrosoft 365: recipient address rejected
On Microsoft 365, this reply means the recipient does not exist. Directory Based Edge Blocking checks every recipient against the…
-
550 5.5.0SuppressOutlook.com: mailbox unavailable
From Outlook.com, Hotmail and Live, this reply means the mailbox does not exist. Microsoft's consumer service uses the RFC 5321…
-
554 5.7.9Fix reputationYahoo: message not accepted for policy reasons
Yahoo refused the message for policy reasons. Yahoo documents 553 and 554 replies as permanent failures, including messages that…
Temporary failures (4xx)
Transient problems. Retry with backoff before treating the address as bad.
-
421 4.7.0Retry laterService not available (rejected by policy)
The receiving server is temporarily refusing the connection, often due to rate limiting or a temporary reputation-based policy…
-
450 4.2.0Retry laterMailbox temporarily unavailable
The mailbox exists but cannot accept mail right now, commonly because the inbox is full or the server has a brief issue with that…
-
451 4.3.0Retry laterLocal error in processing (often greylisting)
A generic temporary failure on the receiving server. It is very often the signature of greylisting, where an unrecognized sender…
-
452 4.2.2Retry laterMailbox full (temporary, over quota)
The recipient's mailbox has exceeded its storage limit and is temporarily refusing new mail until space is freed up.
-
421 4.7.28Retry laterGmail: unusual rate of email, rate limited
Gmail is temporarily rate limiting the sender. The reply reads "Gmail has detected an unusual rate of email", and its variants…
-
450 4.2.1Retry laterGmail: recipient is receiving mail too fast
Gmail is deferring the message because this one recipient is receiving mail at a rate that prevents more messages from being…
-
451 4.7.500Retry laterMicrosoft: access denied, try again later
Exchange Online is temporarily refusing mail from the sending IP. Microsoft documents the 4.7.500 to 4.7.699 range as "Access…
-
421 4.7.0 [TSS04]Retry laterYahoo: messages temporarily deferred
Yahoo is temporarily deferring mail from the sending IP. Yahoo documents its TS codes, such as [TS01] and [TSS04], as temporary…
Success (2xx)
The receiving server accepted the address.
Prevent bounces
Catch bad addresses before you hit send
Most hard bounces come from mailboxes that no longer exist. RocketVerifier checks every address with a live SMTP handshake, without sending an email, so you can remove them first.
Stop hard bounces before they start
Verify your list with 99.5% accuracy and get a clear reason for every result. Unknown results are always free.
100 free credits · No card required · Credits never expire