Bounced Email: What Each Bounce Code Means and How to Stop Them Killing Your Cold Email (2026)

A bounced email is what happens when a receiving mail server refuses to deliver your message. The bounce comes back with an SMTP code that tells you exactly why — and "why" is the difference between an acceptable bounce (the recipient does not exist anymore) and a campaign-killer (your sending IP just got blocklisted).

This guide is the canonical reference for cold email: hard vs soft bounce, the complete SMTP code reference, the math behind cold email's strict bounce thresholds, how to reduce bounce rate at the list-quality layer, the role of warmup in preventing reputation-driven bounces, and how Gmail and Outlook handle bounces differently in 2026.

TLDR — the four bounce categories for cold email:

1. Hard bounce — invalid recipient (550 5.1.1): address does not exist. Suppress and stop.
2. Soft bounce — temporary (4xx codes): retry. Most resolve in under an hour.
3. Reputation bounce (550 / 554 with sender-policy wording): infrastructure problem. Pause and recover.
4. Blocklist bounce (550 / 554 referencing Spamhaus, Barracuda, etc.): delist immediately. See blocklist removal hub.

Read the SMTP code; do not lump every bounce into "list quality." Each category has a different fix.

Table of Contents

• The 30-second answer
• Hard vs soft vs everything else
• Decoding the major SMTP codes
• Full SMTP code reference
• Why cold email's bounce threshold is so strict
• How to reduce bounce rate
• List hygiene playbook
• The role of warmup in bounce prevention
• How Gmail and Outlook handle bounces differently
• How ColdRelay prevents bounce spirals
• FAQ

The 30-Second Answer

The TLDR: the SMTP code tells you what kind of bounce it is. Read the codes; do not lump every bounce into "list-quality problem." Each category has a different fix. For the full code reference, see the SMTP error codes hub.

Hard Bounces vs. Soft Bounces vs. Everything Else

The traditional dichotomy:

Hard bounce = receiving server says "this address will never accept mail." Permanent. SMTP code 5xx (typically 550, 551, 553). The mailbox is gone — recipient does not exist, account closed, domain dead.

Soft bounce = receiving server says "cannot deliver right now." Temporary. SMTP code 4xx (typically 421, 451, 452). Mailbox is full, server is overloaded, or rate limit hit. Try again later.

Hard vs Soft Bounce Decision Tree

When a bounce arrives, the decision tree is:

1. Is the SMTP code 5xx?
   YES → hard bounce path:
       1a. Does the message reference the recipient address itself?
           ("user unknown", "mailbox unavailable", "no such user")
           → True hard bounce. Suppress the address immediately. Do not retry.
       1b. Does the message reference sender reputation, blocklist, or policy?
           ("blocked", "spamhaus", "policy reasons", "rejected for spam")
           → Reputation/blocklist bounce. Infrastructure problem, not list problem.
              Suppress address ONLY for this domain; resume sending after recovery.
       1c. Does the message reference content?
           ("identified as spam", "abusive content", "suspicious attachment")
           → Content bounce. Adjust subject or body before resuming.
   NO (4xx code) → soft bounce path:
       2a. Is it a rate-limit code? (421 4.7.0, 421 4.7.1, 421 4.7.28)
           → Reduce per-mailbox volume. Retry in 30+ minutes.
       2b. Is it greylisting? (451 4.7.1)
           → Receiver expects a retry. ColdRelay's retry logic handles this.
       2c. Is it mailbox full? (452, 552 5.2.2)
           → Retry over 24–72 hours. If still failing after 7 days, treat as bounced.
       2d. Is it temporary local error? (4xx general)
           → Retry. Usually resolves within an hour.

In 2026 the line between hard and soft has blurred because spammers exploit "soft" failures to mask sending to dead addresses. Gmail and Outlook increasingly return soft codes on addresses that are actually permanently dead, to slow spammers down. ColdRelay treats any address that returns three failures in a row (hard or soft) as effectively hard-bounced and auto-suppresses across all mailboxes in your workspace.

Beyond the hard/soft split, two more categories matter specifically for cold email:

Reputation bounce — the receiving server did not reject the recipient (which exists fine); it rejected the sender. The bounce message references your sending domain or IP's reputation. This is an infrastructure problem, not a list problem.

Blocklist bounce — explicitly references a public DNSBL (Spamhaus, Barracuda, SORBS) in the bounce message. Your sending IP is listed; mail is being rejected wholesale. See the blocklist removal hub for the delisting workflow.

Decoding the Major SMTP Bounce Codes

550 — Mailbox Unavailable (Most Common Cold Email Hard Bounce)

Variants:

• 550 5.1.1 The email account that you tried to reach does not exist (Gmail)
• 550 5.1.1 User unknown (generic)
• 550 No Such User Here
• 550 5.1.10 Recipient not found (Microsoft)

What it means: the exact address does not exist on the receiving server.

Cold email implication: suppress the address immediately. If a meaningful percentage of your list returns this code, your data provider's accuracy is the problem — re-verify with a second provider before resuming.

Full reference: 550 5.1.1 user unknown, 550 5.1.10 recipient not found Microsoft.

550 — No MX Records / Domain Does Not Exist

Variants:

• 550 5.1.2 The domain name in the email address could not be found
• 550 No MX records for domain

What it means: the whole DOMAIN does not have working mail servers. Either the company shut down, the domain is not actually theirs, or your data is corrupt.

Cold email implication: suppress and do not re-attempt this domain across your workspace.

552 — Mailbox Full

552 5.2.2 The user has exceeded their email storage quota

What it means: real mailbox; recipient has not emptied it.

Cold email implication: retry over 24–72 hours. ColdRelay's retry logic handles this automatically. If the mailbox stays full for >7 days, treat as effectively bounced — recipient is not reading anyway.

Full reference: 550 5.2.2 over quota.

421 — Service Temporarily Unavailable

Variants:

• 421 4.7.0 IP not in whitelist (anti-spam throttle)
• 421 Try later (server overloaded)
• 421 4.4.5 Server busy
• 421 4.7.1 Message rate exceeded

What it means: receiving server is throttling you. Could be rate limiting (sending too fast), reputation-driven (your IP looks suspicious), or actual server load (unlikely in 2026).

Cold email implication: if you are seeing 421s on more than a percent or two of sends, your IP's reputation is dropping. Pause and investigate. ColdRelay's 2-cold-sends-per-mailbox-per-day cap is set specifically to keep volume below the rate-limit threshold that triggers these.

Full reference: 421 4.7.0 IP not whitelisted, 421 4.7.1 message rate exceeded, 421 4.4.5 server busy.

451 — Temporary Local Error / Greylisting

451 4.7.1 Greylisted, please try again later

What it means: the receiver is greylisting you — refusing first-time mail from unknown senders, expecting your server to retry. Legitimate retries within 5–15 minutes typically succeed; spammers do not bother retrying.

Cold email implication: modern infrastructure handles this transparently. ColdRelay's retry logic resolves >99% of 451 deferrals on the first retry. You should not see these in your reported bounce rate at all.

Full reference: 451 local error.

554 — Transaction Failed (Reputation-Driven)

Variants:

• 554 5.7.1 Service unavailable; client ... blocked using Spamhaus
• 554 5.7.1 Message rejected for policy reasons
• 554 5.7.1 Sender denied

What it means: the receiving server has a specific policy against your sender — usually your IP is on a blocklist, your domain reputation is bad, or your content triggered a filter.

Cold email implication: stop sending immediately. Identify the cause:

• Spamhaus mention → check + delist on Spamhaus.
• Barracuda mention → Barracuda removal form.
• Generic "policy reasons" → likely reputation-driven; let domain reputation recover via reduced-volume + clean list.

550 5.7.1 — Spam Policy Rejection

Variants:

• 550 5.7.1 Message identified as spam
• 550 5.7.1 SPF/DKIM/DMARC fail
• 550 5.7.1 No reverse DNS

What it means: authentication or content failure at SMTP layer.

Cold email implication: check authentication first. See 550 5.7.1 SPF fail (Gmail), 550 5.7.1 DKIM fail (Gmail), 550 5.7.1 DMARC fail (Gmail), 550 5.7.1 no reverse DNS. The SPF/DKIM/DMARC complete guide covers the underlying setup.

Out-of-Office Auto-Replies

Do not count these as bounces. They are DELIVERIES (the recipient just is not reading right now). Most cold email tools categorize them separately; if yours does not, your bounce rate will look artificially inflated.

The Full SMTP Bounce Code Reference

The complete diagnostic reference for every SMTP code lives at the SMTP error codes hub. Highlights for cold email:

4xx Codes (Soft / Temporary)

5xx Codes (Hard / Permanent)

For any code not in this list, see the full SMTP error codes hub.

Why Cold Email's Bounce Threshold Is So Strict

Marketing email tolerates 2–3% bounce rate indefinitely because providers know the list is double-opt-in and the relationship is consensual. Bounces look like normal list churn.

Cold email's tolerance is much lower:

The reason: when Gmail sees cold email (no prior opt-in) at 2% bounces, the inference is "this sender bought a list and did not verify it." Same 2% on marketing email reads as "stale double-opt-in list, sender is legitimate." Same number, different interpretation, different reputation outcome.

Bounce Rate Math

A simple calculation to keep in your head:

Bounce rate = (bounced sends) / (total sends)

But for cold email, you want this number to be per 7-day rolling window, not lifetime. Why: one bad day can spike rolling-7-day numbers while lifetime average stays healthy — and the rolling number is what receivers look at when scoring your reputation.

Example:

• You send 1,000 emails/week with a healthy 0.5% bounce rate (5 bounces/week).
• One bad campaign of 100 sends has a 20% bounce rate (20 bounces).
• Your rolling 7-day bounce rate jumps from 0.5% to 2.5%.
• Gmail's filters see 2.5% over 7 days and downgrade reputation.
• Even if you stop the bad campaign immediately, you carry the 7-day average for another week.

This is why pre-send list verification matters more than post-send bounce response. By the time you see the bounces, the reputation damage is already partially done.

For a deeper bounce rate analysis, see cold email bounce rate explained.

How to Reduce Bounce Rate (The Step-by-Step)

If your bounce rate is above 1%, here is the remediation order:

Step 1: Pre-Send Email Verification

Verify every email address before sending. This catches 90%+ of would-be bounces before they happen.

• ZeroBounce, NeverBounce, MillionVerifier — pick one.
• Cost: $0.003–0.007 per verification.
• Set up as a pre-send hook so any address that fails verification gets auto-suppressed.

ColdRelay also runs an SMTP-layer verification (RCPT TO check) on every address before the first real send — this catches a meaningful additional ~5% of invalid addresses that third-party verifiers miss.

See check email valid and best email verification tools.

Step 2: Drop Catch-All Domains

Catch-all domains accept mail to any address (real or not). Verification reports them as "valid" because the SMTP check passes — but real delivery often fails because the receiving server silently discards mail to non-existent addresses.

For high-stakes campaigns, exclude catch-all domains or treat them as separate-segment with their own bounce rate tracking.

Step 3: Re-Verify Stale Lists

Email addresses go stale at ~2% per month for B2B lists. A list verified 6 months ago is now 12% stale.

Re-verify any list older than 6 months before re-using it.

Step 4: Suppress Bouncing Addresses Workspace-Wide

When an address bounces, suppress it across every mailbox in your workspace. Do not let a different mailbox try the same dead address next week. ColdRelay does this automatically; standalone sending tools usually require configuration.

Step 5: Reduce Per-Mailbox Volume Temporarily

If bounce rate is spiking despite verified lists, the cause may be reputation-driven (your IP looks bad and receivers are rejecting on principle). Reduce per-mailbox volume to 1/day for 7 days, then resume at 2/day as reputation recovers.

Step 6: Investigate by Bounce Code

Group your bounces by SMTP code. Different codes need different fixes:

• High % of 550 5.1.1 → list quality problem.
• High % of 421 4.7.x → rate limit / reputation problem.
• High % of 554 5.7.1 → blocklist or reputation problem.
• High % of 550 5.7.1 → authentication or content problem.

The SMTP error codes hub has diagnostic steps for each code.

The List Hygiene Playbook

List hygiene is the single highest-leverage activity in cold email. The math:

Bad list (5% bounce rate, 100 mailboxes × 2 sends/day × 22 working days):

• Total monthly sends: 4,400.
• Bounces: 220.
• Hit to domain reputation: Domain Reputation drops from High to Medium within 2 weeks.
• Lost capacity to recover: 25–40% reduced effective send volume for 30 days.

Clean list (0.3% bounce rate, same volume):

• Bounces: 13.
• Domain Reputation stable at High.
• Full send capacity maintained.

The difference: ~200 fewer bounces and a 30-day reputation hit avoided. Cost of list hygiene: $20–50 in verification fees and 2 hours of operator time. ROI: catastrophic in favor of hygiene.

The Standard List Hygiene Workflow

1. Source the list. Apollo, ZoomInfo, Clearbit, manual research — note the source.
2. Initial verification (bulk). Run the full list through ZeroBounce or equivalent.
3. Remove role-based addresses. info@, support@, admin@ — these are not real prospects and they generate complaints disproportionately.
4. Flag catch-all domains. Either drop them or send to them as a separate cohort.
5. Verify catch-all flags with manual sampling. Send a test to a few catch-all addresses; see what happens.
6. Re-verify any contact > 6 months old. Even high-quality original verification goes stale.
7. Suppress every bounced address workspace-wide. Build a permanent suppression list that all campaigns reference.
8. Audit by SMTP code monthly. Group bounces by code; if any code is unusually high, fix the root cause.

The Role of Warmup in Bounce Prevention

Warmup does not directly prevent recipient-doesn't-exist bounces (those are a list-quality problem). But warmup is critical for preventing reputation-driven bounces (the 421/554 categories that come from the receiver not trusting your sender).

How warmup protects against reputation bounces:

1. Establishes engagement signal. Warmup creates two-way email behavior — opens, replies, spam-folder rescues — that tells receivers your domain is legitimate. Without this signal, receivers default to "treat as suspicious," which means soft-bouncing more aggressively.

2. Builds IP-domain trust. Receivers maintain trust scores per (sending IP, sending domain) pair. Warmup populates that score before you send real outbound. Skipping warmup means your first real send is from an IP-domain pair receivers have never seen, which gets soft-bounced reflexively.

3. Spreads the volume signature. Warmup is consistent, low-volume daily behavior. This trains receivers to expect modest sending from your domain. A sudden volume spike (no warmup → 30 sends day one) reads as a botnet pattern and triggers 421 rate-limit responses.

4. Generates positive engagement data. Postmaster Tools tracks engagement signals that affect Domain Reputation. Warmup populates this data with positive interactions — opens, replies, no-spam-complaints — before you start cold outbound that inevitably generates some complaints.

The canonical cap (2 outbound + 2 warmup per mailbox per day, sustained indefinitely) is engineered to keep this protective layer active forever. Stop warmup and reputation decays in 30–60 days. See the cold email warmup complete guide for the deeper mechanics.

How Gmail and Outlook Handle Bounces Differently in 2026

Receivers do not handle bounces identically. The two majors:

Gmail (Google Workspace + free Gmail)

• Hard bounces are returned fast. Gmail returns 550 5.1.1 within seconds for invalid addresses.
• Soft bounces are aggressive. Gmail will 421-throttle senders with even mild reputation issues. The threshold is conservative; legitimate senders rarely trip it.
• Spam-classification at SMTP layer: Gmail returns 550 5.7.1 at the SMTP connection for messages it strongly classifies as spam, rather than accepting and dumping in the spam folder.
• Bulk-sender requirements (Feb 2024+): senders pushing > 5,000/day to Gmail must have SPF, DKIM, DMARC, one-click unsubscribe, and spam complaint rate below 0.3%. Violations result in increased rejection rates over days, then outright rejection.
• Postmaster Tools: the primary feedback channel. See Google Postmaster Tools for cold email.

Outlook / Microsoft 365 / Outlook.com

• Hard bounces are returned slower. Microsoft sometimes accepts the message at SMTP, then bounces it 24–48 hours later if it cannot deliver.
• Soft bounces vary by tenant. Microsoft 365 commercial tenants behave differently from free Outlook.com. Commercial tenants are more tolerant; consumer Outlook.com is stricter.
• Aggressive 421-throttling on reputation: Microsoft's IP reputation system (SmartScreen) returns 421 4.7.0 for senders it does not trust, even when the recipient address is valid.
• SNDS feedback channel: Smart Network Data Services is Microsoft's equivalent of Postmaster Tools. IP-level only (no domain reputation).

Yahoo / AOL

• Now governed by Yahoo's 2024 bulk-sender requirements (same Feb 2024 update as Google's). SPF, DKIM, DMARC required. One-click unsubscribe required for bulk.
• Engagement-driven filtering. Yahoo weights engagement signals (opens, replies) heavily. Unopened cold email accumulates negative signal fast.

Apple iCloud / Me / Mac

• Conservative spam classification. Apple's filters are stricter than Gmail's for unknown senders.
• No direct feedback channel. Apple does not publish a Postmaster equivalent. You can only infer reputation from inbox placement testing.

How ColdRelay's Infrastructure Prevents Bounce-Rate Spirals

Five design choices:

1. Pre-send SMTP verification on every recipient. Before the first send to any address, ColdRelay's SMTP layer verifies the receiving server accepts mail for that address (RCPT TO check). Addresses that fail get auto-marked invalid and never receive a real send. This catches most invalid-recipient bounces before they hit your bounce rate.

2. Auto-suppress on first hard bounce. A hard-bounced address is suppressed across every mailbox in your workspace immediately. You do not accidentally send to the same dead address from a different mailbox later in the week.

3. Workspace-level bounce-rate monitoring. If your rolling 7-day bounce rate exceeds 1.5%, sending automatically pauses and we require a list-quality review before unblocking.

4. Volume cap of 2 cold sends per mailbox per day. Below every major provider's rate-limit threshold. Rate-limit bounces (421) become structurally impossible at this cadence.

5. Continuous blocklist monitoring. Hourly DNSBL scans across 30+ major blocklists. If any IP gets listed, you get an alert in under an hour — long before the listing affects your bounce rate visibly. See the blocklist removal hub for the delisting workflow.

The volume cap is the most counter-intuitive: every new customer asks why we do not let them send more. The answer is the math — at higher volume, complaint rate spikes linearly, bounce rate creeps up from reputation drops, and the next thing you are looking at is 421s and 554s. Two per mailbox per day is the volume that keeps Postmaster Tools Domain Reputation pinned at High over multi-month campaigns.

FAQ

My bounce rate is 4% — what should I do?

Pause campaigns on the affected domain. Identify the contact source producing most bounces. Re-verify before resuming. If you keep sending at 4%, expect your Postmaster Tools Domain Reputation to drop from High to Medium within a week — at which point inbox placement starts declining and reply rates follow.

Do soft bounces count toward my bounce rate?

Depends on your sending tool. Most modern tools count only persistent failures (3+ retries failing) toward bounce rate, which is the right approach. If yours counts every soft bounce immediately, your reported number will look worse than reality. ColdRelay's bounce categorization treats 3-consecutive-failures as bounced regardless of soft/hard code.

Why am I getting bounces from addresses I just verified?

Several reasons:

• Verification accuracy is not 100% (95–98% is the industry best). Long-tail data has more misses.
• The address might be on a catch-all domain — verification passes but real-world delivery fails.
• The mailbox got disabled between verification and send (especially long-cycle enrichment data).
• Reputation-driven rejections look like address bounces but are not (the mailbox exists; the receiver does not trust your sender).

What's the difference between a "rejected" message and a bounced one?

Rejection = receiving server refused at SMTP layer (during the initial connection, before accepting the message). Bounce = receiver accepted the message, then later returned a delivery failure. From the sender's POV they look the same. From a deliverability-diagnostic POV, rejections at SMTP time tend to be reputation/blocklist-driven; bounces accepted-then-returned tend to be address-quality issues.

Should I retry hard bounces ever?

No. Hard bounce = permanent failure. Retrying a hard bounce signals "we do not verify our list" to inbox providers. Suppress the address immediately and do not re-attempt. The SMTP error codes hub has the canonical "retry vs suppress" decision per code.

What is a good bounce rate for cold email in 2026?

Below 1% is healthy. Above 2% triggers reputation damage. Below 0.5% is excellent and indicates strong list quality. The bounce rate threshold for cold email is roughly half what marketing email tolerates because receivers infer "no opt-in" intent from cold email bounces.

How does Postmaster Tools relate to bounce rate?

Bounces show up in Postmaster Tools as "Delivery Errors." Spam-filtering rejects and rate-limit rejects are also counted here. Keep the Delivery Errors chart below 5%. See Google Postmaster Tools for cold email for the full Postmaster reference.

How do I tell if a bounce is reputation-driven vs address-quality?

Read the bounce message. Address-quality bounces reference the recipient ("user unknown," "mailbox not found," "no such user"). Reputation bounces reference the sender ("blocked," "policy reasons," "rejected for spam," any blocklist name). The decision tree in the hard vs soft bounce section covers the full classification.

Does ColdRelay's pre-send verification cost extra?

No — it is included in the per-mailbox price. Pre-send SMTP verification is part of the infrastructure tier and runs automatically on every push to a campaign. See the pricing page for the full feature/price ladder.

My mailbox is "healthy" in ColdRelay but I am getting bounces — what is happening?

ColdRelay verifies the address exists when you push it to a campaign. If bounces still happen post-push, it is usually one of:

1. The address went dead between push and send (contact left the company, etc.).
2. The receiving server has a temporary issue.
3. Your bounce rate was already trending up before the verification step caught up — back-pressure from earlier bad data.

Check the bounce-rate dashboard at the per-domain level to localize the issue.

What is "spam trap" and how do I avoid it?

A spam trap is an email address that exists solely to catch lazy senders. There are two types: (1) "pristine traps" — addresses that have never been opted into any list (only scraped lists hit these), and (2) "recycled traps" — addresses that were once real users but got abandoned and converted to traps by the provider. Hitting either is a major reputation signal. Avoid by: never buying scraped lists, never sending to addresses you cannot verify by an opt-in or recent activity signal, and dropping any address that has been inactive on your list for 12+ months.

Are bounce rates worse for free email domains (gmail.com, outlook.com) vs business domains?

Sometimes, depending on your data source. Free email domains have higher staleness rates (users abandon free accounts more often) but also stricter verification. Business domains are more stable but more likely to be catch-alls or role-based. Track bounce rate by recipient-domain segment to localize issues.

Bounces are mostly a list-source problem. ColdRelay's infrastructure prevents the rate-limit and reputation-driven categories that are not list problems, but list hygiene is on you — and the platform makes it harder to wreck things by accident.

Related reading:

• Cold email deliverability complete guide
• Cold email bounce rate explained
• Google Postmaster Tools for cold email
• SPF, DKIM, and DMARC for cold email
• Check email valid
• Best email verification tools
• SMTP error codes reference
• Blocklist removal guides

Infrastructure that pauses itself when your bounce rate goes bad → Try ColdRelay free · Test your sending IP for blocklist issues → Free blacklist check