SMTP bounce codes explained: 550 5.1.1 user unknown and the rest
· 7 min read · Email validation
550 5.1.1 user unknown means the receiving mail server says the recipient's mailbox doesn't exist, and it's permanent: suppress the address and never retry it. More generally, every SMTP bounce carries two codes. The three-digit reply code from RFC 5321 says whether the failure is permanent (5xx) or temporary (4xx). The enhanced status code from RFC 3463, like 5.1.1, says what went wrong. The tables below cover the codes you will actually see and what to do with the address for each.
How to read the two codes together
A bounce line looks like this:
550 5.1.1 <sam@example.com>: Recipient address rejected: User unknown in virtual mailbox table
550is the basic reply code. First digit2is success,4is a transient failure (try again),5is a permanent failure.5.1.1is the enhanced status code, writtenclass.subject.detail. The class repeats the permanence (2,4or5). The subject is the interesting part:
| Subject | Meaning (RFC 3463) | Usually about |
|---|---|---|
x.1.x |
Addressing status | The recipient address or domain |
x.2.x |
Mailbox status | The recipient's mailbox |
x.3.x |
Mail system status | The receiving system |
x.4.x |
Network and routing status | Connectivity between servers |
x.5.x |
Mail delivery protocol status | The SMTP conversation |
x.6.x |
Message content or media status | The message itself |
x.7.x |
Security or policy status | You: authentication, reputation, rules |
The rest of the line is free text chosen by the server. It's useful for humans and unreliable for code, since every provider words it differently. Parse the numbers first and fall back to the text only when the enhanced code is missing.
Basic SMTP reply codes (RFC 5321)
These are the codes defined in RFC 5321 section 4.2, plus two added later by RFC 7504.
| Code | RFC text | What it usually means | What to do with the address |
|---|---|---|---|
421 |
Service not available, closing transmission channel | Server busy, rate-limiting you, or shutting down | Nothing. Retry later. |
450 |
Requested mail action not taken: mailbox unavailable | Greylisting, mailbox busy, temporary policy block | Retry. Don't suppress. |
451 |
Requested action aborted: local error in processing | Their temporary problem | Retry. |
452 |
Requested action not taken: insufficient system storage | Server or mailbox storage problem, or too many recipients | Retry. Watch for repeats. |
550 |
Requested action not taken: mailbox unavailable | Many things. Read the enhanced code. | Depends on the enhanced code |
551 |
User not local; please try a forward-path | Mailbox moved or not hosted here | Suppress, look for a new address |
552 |
Requested mail action aborted: exceeded storage allocation | Mailbox full, or message too big | One retry; suppress if it repeats |
553 |
Requested action not taken: mailbox name not allowed | Address syntax rejected | Suppress, check for a typo |
554 |
Transaction failed (or "No SMTP service here" at connect) | Generic permanent failure, often policy | Read the enhanced code and text |
521 |
Host does not accept mail (RFC 7504) | The server accepts no mail at all | Suppress the domain |
556 |
Domain does not accept mail (RFC 7504) | Typically a null MX domain | Suppress the domain |
550 and 554 are catch-alls in their own right. A 550 can mean "no such user" or "you're on a blocklist", which need opposite responses. Never act on 550 without the enhanced code or the text.
Enhanced status codes that matter (RFC 3463 and later)
Address and mailbox: usually the recipient's problem
| Code | Meaning | Action |
|---|---|---|
5.1.1 |
Bad destination mailbox address. The mailbox doesn't exist. | Suppress permanently |
5.1.0 |
Other address status. Often used for unknown users too. | Suppress if the text says unknown user |
5.1.2 |
Bad destination system address. The domain doesn't exist or can't accept mail. | Suppress; check the domain |
5.1.3 |
Bad destination mailbox address syntax | Suppress; check for a typo |
5.1.6 |
Destination mailbox has moved, no forwarding address | Suppress; look for the person's new address |
5.1.10 |
Recipient address has null MX (RFC 7505) | Suppress the whole domain |
5.2.1 |
Mailbox disabled, not accepting messages | Suppress |
5.2.2 / 4.2.2 |
Mailbox full | Retry on a later send; suppress after repeats |
5.2.3 |
Message length exceeds administrative limit | Fix the message, not the list |
Sender and policy: usually your problem
| Code | Meaning | Action |
|---|---|---|
5.1.7 |
Bad sender's mailbox address syntax | Fix your envelope sender |
5.1.8 |
Bad sender's system address. The receiver can't verify your sending domain. | Fix your sending domain's DNS |
5.7.0 |
Other security or policy status | Read the text; investigate |
5.7.1 |
Delivery not authorized, message refused | Investigate before suppressing. Often a blocklist, a content filter, or a recipient-side allowlist. |
5.7.26 |
Multiple authentication checks failed (RFC 7372) | Fix SPF, DKIM and DMARC alignment |
4.7.x |
Temporary policy deferral, often greylisting or reputation throttling | Retry and slow down |
Gmail's email sender guidelines document two of these directly: unauthenticated mail may be rejected with a 5.7.26 error, and senders over their rate quota typically get 4.7.28, with the advice not to send for at least 10 minutes.
Network, routing and protocol: usually nobody's fault
| Code | Meaning | Action |
|---|---|---|
4.4.1 |
No answer from host | Retry |
4.4.2 |
Bad connection | Retry |
5.4.4 |
Unable to route. Often no MX and no A record. | Suppress if the domain has no mail setup |
4.4.7 / 5.4.7 |
Delivery time expired. Your server gave up after retrying. | Check the earlier deferral reason; one expiry isn't proof the address is dead |
4.5.3 / 5.5.3 |
Too many recipients | Send fewer recipients per message |
5.3.4 |
Message too big for system | Shrink the message |
Codes that lie
Some servers don't use the codes the way the RFC intends, so a strict lookup table gets these wrong:
- Microsoft 365 directory-based edge blocking. Tenants with this enabled reject unknown recipients with
550 5.4.1 Recipient address rejected: Access denied. The enhanced code is a routing code, but the meaning is "no such user". Our prober's classifier has a special case for exactly this wording. 5.2.1used for policy. Some servers send "mailbox disabled" when they're actually blocking you. Check the text for blocklist names.- Accept now, bounce later. Some gateways answer
250atRCPT TOand send a5.1.1bounce minutes later. RFC 5321 section 3.3 permits this. To a pre-send check, these domains look like they accept everyone.
A small classifier you can use on bounce logs
If you export bounces from your sending tool as text, this function sorts them into the three actions that matter. It reads the enhanced code first and falls back to the text.
// classify-bounce.mjs
const ENHANCED = /\b([245])\.(\d{1,3})\.(\d{1,3})\b/;
export function classifyBounce(line) {
const text = line.toLowerCase();
const m = ENHANCED.exec(line);
const basic = Number((/\b([245]\d\d)\b/.exec(line) ?? [])[1]);
if (m) {
const [, cls, subject, detail] = m.map(Number);
if (cls === 4) return 'retry';
if (subject === 7) return 'fix_sending'; // 5.7.x policy
if (subject === 1 && (detail === 7 || detail === 8)) return 'fix_sending'; // sender address
if (subject === 4 && detail === 1 && /access denied/.test(text)) return 'suppress'; // M365
if (subject === 1 || (subject === 2 && detail === 1)) return 'suppress';
if (subject === 2 && detail === 2) return 'retry'; // mailbox full
return 'review';
}
if (basic >= 400 && basic < 500) return 'retry';
if (/blocked|blacklist|blocklist|spamhaus|reputation|policy/.test(text)) return 'fix_sending';
if (/user unknown|no such user|does not exist|not found/.test(text)) return 'suppress';
return 'review';
}
for (const l of [
'550 5.1.1 <sam@example.com>: User unknown',
'550 5.7.1 Service unavailable, client host blocked using Spamhaus',
'452 4.2.2 Mailbox full',
'550 5.4.1 Recipient address rejected: Access denied',
]) console.log(classifyBounce(l), '|', l);
node classify-bounce.mjs
Treat review as a queue for a human, not a default suppress. The hard bounce vs soft bounce article has a suppression policy for repeated soft bounces.
Seeing these codes before you send
Every code in the "recipient's problem" table can show up at RCPT TO time, before a message is sent. That's what mailbox verification relies on: open a session, name the recipient, read the reply, hang up. We walk through it in how to verify an email address without sending an email.
pingutil's /v1/verify returns the server's reply as smtp.code, smtp.enhanced and smtp.message, alongside a decision. The mapping is roughly: 5.1.x becomes invalid / mailbox_not_found, 5.2.1 becomes invalid / mailbox_disabled, x.2.2 becomes risky / mailbox_full, and 4xx deferrals and 5.7.x policy rejections become unknown (greylisted, rate_limited or blocked), because they say nothing about the mailbox. A rejection aimed at the prober's own sender address is also classed as blocked rather than blamed on the recipient. The full list is in email verification statuses explained, and you can see a live reply in the email verification demo.
Pre-send checks won't catch the "accept now, bounce later" servers or catch-all domains, so you still need to process real bounces. The point is to move the obvious 5.1.1 failures out of your sends, where they cost reputation, and into a check, where they cost nothing.
The short version
5.1.xand5.2.1: the address is bad. Suppress it everywhere you send from.5.7.x: you are the problem. Fix authentication, reputation or content.4.x.x: wait. Your server retries. Suppress only after repeated failures.- Bare
550or554: read the text before deciding anything.
Questions people ask
- What does 550 5.1.1 user unknown mean?
- The receiving mail server says the mailbox does not exist. 550 is a permanent failure in RFC 5321, and 5.1.1 is 'bad destination mailbox address' in RFC 3463. Suppress the address and don't retry it.
- What is the difference between 550 and 5.1.1 in a bounce?
- 550 is the basic SMTP reply code, which only says the request failed permanently. 5.1.1 is the enhanced status code that says why: the recipient mailbox is bad. Many different problems share 550, so always read the enhanced code.
- Is 550 5.7.1 a bad email address?
- Usually not. 5.7.1 means delivery was not authorized or the message was refused for policy reasons, which is about your sending (authentication, reputation, content or a recipient-side rule) rather than whether the mailbox exists. Fix the cause before you suppress anything.