Email bounce codes explained: 550 5.1.1, 5.4.1, 452 4.2.2 and friends

SMTP bounce codes for mailbox checks: user unknown, disabled, over quota, greylisting and the blocks that look like them, with Gmail and Microsoft 365 examples.

  • #verification
  • #smtp
  • #deliverability
Four SMTP replies and their verdicts: 250 2.1.5 OK is deliverable, 550 5.1.1 User unknown is undeliverable, 452 4.2.2 Over quota is risky, 550 5.7.1 blocked using Spamhaus is unknown. What the mail server said, and what it means reply to RCPT TO verdict 250 2.1.5 OK deliverable 550 5.1.1 User unknown undeliverable 452 4.2.2 Over quota risky 550 5.7.1 Blocked using Spamhaus unknown a block is about the sender, never about the mailbox

Every time a mail server refuses a recipient, it says why in a short line of text: 550 5.1.1 User unknown. Those lines end up in bounce messages, in your email provider’s logs, and in the answers an email verifier gets when it checks whether an address exists. Reading them correctly is the difference between removing a dead address and removing a real colleague because a spam filter didn’t like your server.

This is a practical reference to the replies that matter for mailbox existence, with the provider-specific wording we see in practice.

How to read an SMTP reply

A reply has up to three parts:

550 5.1.1 The email account that you tried to reach does not exist.
│   │     └─ free text, provider-specific
│   └─ enhanced status code (RFC 3463): class.subject.detail
└─ basic reply code (RFC 5321)

The basic code says how final the answer is:

Code Meaning
2xx Accepted. 250 is the usual “OK”.
4xx Temporary failure: try again later.
5xx Permanent failure for this request.

The enhanced status code, defined in RFC 3463, says why. Its middle number is the subject:

Subject About Examples
x.1.x The address 5.1.1 bad mailbox address
x.2.x The mailbox 5.2.1 disabled, x.2.2 full
x.4.x Network and routing 4.4.1 no answer from host
x.5.x The SMTP protocol 5.5.0 other protocol status
x.7.x Security and policy 5.7.1 delivery not authorized

Not every server sends an enhanced code, and some use them loosely, so the text matters too.

The mailbox doesn’t exist

These are hard bounces. Stop sending to the address.

Reply Where you’ll see it
550 5.1.1 The email account that you tried to reach does not exist. Gmail and Google Workspace
550 5.1.1 User Unknown Many servers and gateways
550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in virtual mailbox table Postfix
550 No such user ([email protected]) Common, no enhanced code
550 Unrouteable address Exim
550 Invalid Recipient - https://community.mimecast.com/docs/DOC-1369#550 Mimecast
554 delivery error: dd This user doesn't have a yahoo.com account Yahoo
550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup Microsoft Exchange Online

Microsoft’s two odd ones

Two Microsoft replies trip up anyone who matches on words:

  • 550 5.4.1 Recipient address rejected: Access denied: Exchange Online with Directory-Based Edge Blocking checks every recipient against the organization’s directory and rejects unknown ones with this line. “Access denied” sounds like a block, and x.4.x is officially about routing, but it means this recipient doesn’t exist.
  • 550 5.5.0 Requested action not taken: mailbox unavailable: Outlook.com and Hotmail’s answer to an unknown consumer address.

The mailbox exists, but…

Reply Meaning What to do
550 5.2.1 The email account that you tried to reach is disabled. (Gmail) The account exists but is disabled Treat as undeliverable
550 5.2.1 Mailbox disabled, not accepting messages The same, elsewhere Treat as undeliverable
452 4.2.2 The email account that you tried to reach is over quota. (Gmail) Full; temporary Retry later; suppress if it persists
552 5.2.2 Mailbox full Full Retry later; suppress if it persists

A full mailbox is a real mailbox, but one whose owner may have stopped reading it. Verifiers usually report it as risky rather than valid.

Not about the mailbox: blocks and policy

These replies are about the sender: its IP address, reputation, authentication or behavior. They say nothing about whether the recipient exists. Never remove an address because of them.

Reply Meaning
550 5.7.1 Unfortunately, messages from [203.0.113.7] weren't sent. … part of their network is on our block list (S3150). Outlook.com: the sending IP is on Microsoft’s block list
550 5.7.606 Access denied, banned sending IP [203.0.113.7]. Microsoft 365: the sending IP is banned
554 5.7.1 Service unavailable; Client host [203.0.113.7] blocked using zen.spamhaus.org The receiving server checks the Spamhaus block list
553 5.7.1 [BL21] Connections will not be accepted from 203.0.113.7, because the ip is in Spamhaus's list Yahoo, block list
550 5.7.1 [203.0.113.7] Our system has detected an unusual rate of unsolicited mail originating from your IP address. Gmail: reputation
554 Rejected by policy Mimecast policy

The rule of thumb: 5.7.x is a policy refusal. When there’s no enhanced code, words like blocked, block list, Spamhaus, reputation, policy or SPF mean the same. Microsoft’s 5.4.1 recipient rejection is the one exception worth hard-coding.

Try again later

Reply Meaning
451 4.7.1 Greylisting in action, please come back later Greylisting: unfamiliar senders are deferred on purpose and accepted on a later attempt
421 4.7.0 … unusual rate of unsolicited mail … Gmail is rate-limiting the sender
450 4.1.1 … Recipient address rejected: unverified address Postfix couldn’t verify the recipient with a downstream server yet

A 4xx is not a verdict. Senders retry automatically for hours or days. A verifier should report “unknown”, come back later, and only then decide.

When the code says nothing

Some servers answer 550 Requested action not taken or 554 Transaction failed with no enhanced code and no explanation. A plain 550 for a recipient, after the server happily accepted the sender, is most likely an unknown user, but it isn’t proven. A 554 with no text could be anything. Report these with lower confidence rather than pretending to know.

What to do with each kind of bounce

Bounce handling in your sending tool usually follows these rules:

  • Unknown user, disabled mailbox, domain without mail servers: suppress the address right away. Sending again only adds bounces to your reputation. If the address came from a form, look for a typo: [email protected] is fixed by a typo check, not by retrying.
  • Full mailbox: keep it for a few attempts over several days, then suppress it if it keeps bouncing. A mailbox that stays full is usually one nobody reads any more.
  • Greylisting and other 4xx replies: your mail server retries on its own. Only act if it finally gives up.
  • Blocks and policy refusals: fix your side. Check whether your sending IP or domain is on a block list, and whether SPF, DKIM and DMARC pass; the SPF and DMARC checker shows the published records for any domain. Don’t remove the recipients: they did nothing wrong.
  • Catch-all domains: nothing bounces during the conversation, but some bounce afterwards. What is a catch-all email domain? covers how to handle them.

The same codes show up when you check an address before sending, which is cheaper than finding out from a bounce. You can see the mail servers a domain uses with the MX lookup.

How isBusinessEmail reads these replies

The email verifier and /v1/verify apply the rules above to the reply to RCPT TO:

Reply status reason
250 (and a random address refused) deliverable mailbox_exists
5.1.1, 5.1.10, Microsoft 5.4.1 recipient rejection, Outlook.com 5.5.0, “user unknown” wording undeliverable mailbox_not_found
5.2.1, “disabled” wording undeliverable mailbox_disabled
x.2.2, “over quota” or “mailbox full” risky mailbox_full
Plain 550, 551 or 553 without an explanation undeliverable (confidence 0.8) mailbox_rejected
5.7.x or block-list and policy wording unknown probe_blocked
4xx unknown greylisted, retried in the background
Other unexplained 5xx unknown smtp_rejected

Each result includes the stage the conversation reached, the reply code, the enhanced code and the server’s text with addresses and IP addresses removed, so you can see exactly why it was classified that way.

Frequently asked questions

What does 550 5.1.1 mean?

The receiving server says the recipient address doesn't exist: the mailbox was never created, was deleted, or the address is misspelled. It is a permanent failure, so don't resend to that address.

What does 550 5.4.1 Recipient address rejected: Access denied mean?

From Microsoft 365, it usually means the recipient doesn't exist in the organization's directory. Exchange Online rejects unknown recipients this way when Directory-Based Edge Blocking is on. The wording sounds like a block, but it is about the address.

What is the difference between a 4xx and a 5xx error?

A 4xx reply is temporary: the server wants you to try again later, for example because of greylisting or a full queue. A 5xx reply is permanent for that message: retrying the same thing will get the same answer.

What does 452 4.2.2 over quota mean?

The mailbox exists but is full. The 4 means the server considers it temporary, so a later delivery may succeed once the owner frees up space. Some servers use 552 5.2.2 for the same situation.

Is 550 5.7.1 a bad email address?

Usually not. 5.7.x codes are security and policy refusals: the receiving server refused the sender, its IP, its authentication or the content. Read the text to find out why, and don't remove the recipient on the strength of it.

What is the difference between a hard bounce and a soft bounce?

A hard bounce is a permanent failure, such as an unknown user (5.1.1) or a domain that doesn't exist. A soft bounce is temporary, such as a full mailbox or greylisting. Senders usually suppress hard bounces immediately and soft bounces after repeated failures.