Home › Blog › Cold Email Bounce Codes Explained: 4xx vs 5xx, Pause, Retry, or Retire?
Cold Email Bounce Codes Explained: 4xx vs 5xx, Pause, Retry, or Retire?
Operators keep mistaking recipient-data bounces for reputation damage and throttling for the end of the world. Bounce codes tell you which problem you actually have, here's how to read 4xx vs 5xx, the specific codes that matter, and the decision tree from code to action.
Quick Answer: The Code Names the Culprit
5.1.1 user-unknown cluster → list problem (fix verification, not sending). 5xx policy/blocklist wording → reputation problem (stop, check blacklists + auth, decision tree). 4xx wall from one provider → throttling (halve volume there, don't retry harder). Scattered 4xx → weather (sequencer retries handle it). Read the code before you act, and you'll stop treating list problems with warmup and reputation problems with retries.
The Two Families, and Why Confusing Them Costs You
Every bounce carries an SMTP status: 4xx means "not now", the server is explicitly inviting a retry, and 5xx means "not ever", a permanent rejection of this message, this recipient, or you. The expensive mistakes all come from crossing the wires: operators see 5.1.1 user-unknown bounces and start "re-warming" (pointless, the mailboxes don't exist); or see a wall of Microsoft deferrals and keep blasting retries (converting polite throttling into hostile blocking); or see a Spamhaus rejection and blame the list (it's you, and every further send makes it worse).
The Codes That Actually Matter
550 5.1.1 "user unknown" → mailbox doesn't exist LIST 550 5.2.1 "mailbox disabled" → dormant/deactivated LIST 552 5.2.2 "mailbox full" → real but overflowing SOFT-ish 550/554 "blocked… Spamhaus/RBL" → you're on a blacklist REPUTATION 550 5.7.1 "access denied / policy" → policy rejection of YOU REPUTATION 421 4.7.0 "try again later" → rate limiting / greylist THROTTLE 451 4.7.x "temporarily deferred" → provider slowing you down THROTTLE 452 4.2.2 "over quota" → mailbox full (temp) WEATHER
Enhanced codes (the x.y.z after the number) refine the story: 5.1.x = addressing (list), 5.2.x = mailbox state, 5.7.x / 4.7.x = policy and security (the ones about you). Wording matters as much as numbers, any bounce that names a blocklist, "reputation," or "unsolicited" is a reputation event regardless of code.
The Decision Tree
- •Cluster of 5.1.1/5.2.1 → pause the affected list segment, not the domain. Autopsy the data source, re-run verification, tighten the catch-all policy. Your infrastructure is fine; your data pipeline lied to you. (Retire the addresses permanently, bouncing twice is unforgivable.)
- •Any blocklist/policy 5xx → stop sending on that identity today. Run the Blacklist Checker and the auth check, then follow the recover/rest/retire tree. Volume through a policy block is self-harm.
- •4xx wall from one provider → you're being throttled. Halve volume to that provider, widen send spacing, and if it's Microsoft, check you're sending provider-matched (the Outlook playbook). Deferrals that persist a week at reduced volume are graduating toward blocks, treat seriously.
- •Scattered 4xx / mailbox-full → normal weather. Sequencer retries handle it; suppress addresses that stay full for a week.
Codes Tell You What; Rates Tell You When
This piece is the diagnosis half. The action-threshold half, what to do at 1%, 2%, 3%, and 5%, and which of those numbers means pause, is its own topic with its own conflicting internet advice, settled with our fleet rules in Bounce-Rate Stop Rules. Read the codes first, though: a 4% bounce rate made of user-unknowns and a 4% made of policy blocks are different emergencies with opposite fixes.
Frequently Asked Questions
What's the difference between 4xx and 5xx email bounces?
4xx = temporary refusal ('try again later'), greylisting, rate limiting, mailbox full, server busy. The receiving server explicitly allows retries, and most 4xx mail eventually delivers. 5xx = permanent rejection, mailbox doesn't exist, policy rejection, or you're blocked. 5xx bounces are the ones that damage sender reputation when they pile up; 4xx bounces are mostly weather.
What does 550 5.1.1 'user unknown' mean for my campaign?
The mailbox doesn't exist, a list-quality bounce, not a reputation one. A cluster of 5.1.1s means your verification failed you (stale data or unresolved catch-alls), and the fix lives in the list pipeline: re-verify, tighten the catch-all policy. It is NOT fixed by warming more, slowing down, or changing copy.
Which bounce codes mean my sender reputation is the problem?
Policy-block codes: 550/554 with wording like 'blocked using Spamhaus', '5.7.1 access denied', 'poor reputation', or Gmail's 'unsolicited mail' rejections. These reference YOU, not the recipient. Response: stop sending on that identity, run blacklist and auth checks, and enter the domain decision tree, pushing through policy blocks digs the hole deeper daily.
Should I retry 4xx soft bounces in cold email?
Your sequencer already does, automatic retries over hours/days are standard and safe. Your job is pattern-watching: scattered 4xx across providers is normal noise; a WALL of 4xx deferrals from one provider (especially Microsoft) is throttling and means halve your volume there, not retry harder. Persistent 4xx on the same address for 3+ days should be treated as a hard bounce.
Do soft bounces hurt sender reputation?
Barely, in normal quantities, providers understand mailboxes fill and servers hiccup. What hurts is what heavy soft-bouncing implies: if you're being mass-deferred, you're being throttled, and ignoring that signal until it converts to 5xx blocks is how reputation damage actually arrives. Treat sustained 4xx walls as the early warning they are.
Get FREE .com Domains
Prewarmed Inboxes So You Can Send Cold Emails Today
Get Prewarmed & Fresh InboxesPrewarmed & Fresh Inboxes
Google, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.
Get Prewarmed & Fresh Inboxes