Hard bounce vs soft bounce: what to do with each, not just what they mean

Every bounced email asks you a single operational question: is this address gone for good, or did delivery merely hit a temporary obstacle? Get the answer right and you remove dead addresses before they damage your reputation while keeping subscribers a full-mailbox hiccup almost cost you. Get it wrong in one direction and you mail the dead for months; wrong in the other and you delete real readers over a server's bad afternoon.

The two-word vocabulary for this is hard bounce versus soft bounce. We keep the formal definitions in the glossary — hard bounce and soft bounce — so this guide can do the more useful thing: walk the decision. What each classification implies, when to trust it, and when the label on the bounce is wrong.

The classification in one table

| | Hard bounce | Soft bounce | |---|---|---| | Meaning | Permanent failure | Temporary failure | | Typical SMTP class | 5xx | 4xx | | Common causes | Address doesn't exist, domain doesn't exist, recipient server permanently refuses | Mailbox full, server down, message too large, greylisting, rate limiting | | Correct response | Suppress immediately | Retry; escalate if it persists | | Reputation weight | High — receivers read repeated hard bounces as a stale or purchased list | Low, unless chronic |

The SMTP status class is the mechanical basis: a 550-style permanent rejection versus a 450-style temporary deferral. Your sending platform reads those responses and assigns the label you see in your campaign report.

What to do with a hard bounce

Suppress the address, immediately and permanently. That's the whole playbook, and every reputable platform runs it automatically by adding hard-bounced addresses to your suppression list. Your job is mostly to not undermine the mechanism: don't re-import old exports over your suppression list, don't "give it one more try" from a second platform, and treat any workflow that resurrects suppressed addresses as a bug.

Why the severity? Because a hard bounce is the strongest evidence available that an address was never valid or is no longer in use, and receivers score senders on how much of their traffic targets such addresses. A high hard-bounce rate is the classic fingerprint of a purchased or decayed list — the same lists that harbor spam traps, which are invalid-looking addresses that never bounce but quietly convict you. Suppression is cheap; the reputation it protects is not. What bounce volume does to your metrics overall, and where the acceptable line sits, is covered in our guide to email bounce rate.

One genuine exception exists, covered below: the hard bounce that shouldn't have been one.

What to do with a soft bounce

Nothing, at first. Temporary means temporary: your platform retries delivery over a window (commonly hours to a few days, per each platform's published retry policy), and most soft bounces resolve without you ever noticing. A mailbox was full on Tuesday and had room on Wednesday. A server rebooted. Greylisting — receivers deliberately deferring first contact from unknown senders — produces soft bounces that are not merely harmless but expected.

The decision point arrives with repetition. An address that soft bounces on every campaign for weeks is telling you something permanent in temporary language — most often an abandoned mailbox sitting over quota. Abandoned mailboxes don't open, don't click, and drag engagement down; some will eventually be closed and start hard bouncing anyway. The standing rule most platforms implement, and that we recommend adopting where yours lets you configure it: after some number of consecutive soft bounces to the same address (platforms commonly convert somewhere in the range of three to seven), treat it as hard and suppress. Consult your platform's documentation for its exact conversion rule; it's a claim worth knowing rather than guessing.

When the labels lie

The hard/soft framework is trustworthy for address-level failures and misleading for sender-level ones. Three cases to recognize:

Blocks dressed as bounces. A receiver refusing your mail because of your sending reputation or a blocklist entry may respond with either a permanent or temporary code, and the text is what carries the truth — phrases about "policy reasons", "listed at", or a provider-specific error code. This is not information about the address, so suppression logic is the wrong tool. It's information about you. Check your standing with the blacklist checker and read the bounce text; a bounce message naming a specific blocklist or policy page has told you your actual next step.

A burst of hard bounces from one domain. If addresses at a single company all hard-bounce at once, suspect a receiver-side change — a migration, a misconfigured filter, an expired accept-all — rather than simultaneous mass resignation. Domain-clustered bounces deserve a look before bulk suppression, especially in B2B lists where one domain can be a large customer.

The bounce that names authentication. Rejection text citing SPF, DKIM or DMARC failure means your infrastructure failed, not the recipient's. Suppressing addresses here compounds the damage. Run your domain through the email authentication checker and fix the actual fault.

The pattern across all three: the binary label triages, the bounce text diagnoses. Platforms vary in how much of the raw response they expose, and the ones that show full bounce text make this whole decision guide easier to apply.

Prevention beats classification

The most effective bounce handling happens before the send. Collecting addresses with double opt-in filters out typos and fakes at the door — an address that confirmed receipt of one email demonstrably exists. Regular list hygiene retires addresses that have stopped engaging before they start bouncing, which is the order you want: mailboxes are typically abandoned long before they're closed. And steady sending cadence keeps you continuously informed; a list untouched for a year delivers its accumulated decay as one bounce-heavy, reputation-denting campaign.

The decision, compressed

• 5xx on an address → suppress, and trust the suppression.
• 4xx on an address → let retries run; convert to suppressed only when it repeats across campaigns.
• Bounce text mentioning policy, blocklists or authentication → stop reading it as address data; it's about your sending, and the address list is innocent.
• Bounces clustering on one domain → investigate before suppressing.

Related guides

• Hard bounce — the formal definition and SMTP mechanics
• Soft bounce — temporary failures and retry behavior
• Email bounce rate — what the aggregate number means and where the line sits
• Suppression list — the mechanism that makes hard-bounce handling permanent
• List hygiene — retiring addresses before they bounce
• Blacklist checker — when bounce text points at your reputation instead of the address

About this guide

Written by InboxRatio Editorial. Bounce classification described here follows SMTP status code semantics; platform-specific behavior (retry windows, soft-to-hard conversion thresholds) varies by provider and is described as the range platforms document, not as a single standard. No vendor sponsorship influences this guide.

Methodology

InboxRatio's benchmark sends real campaigns through the platforms we review to controlled seed lists and records delivery outcomes, including how each platform reports and classifies failures. The guidance here rests on SMTP semantics and platform documentation rather than our measurements; the testing protocol is documented in how we test.

Last updated

2 September 2026. Classification guidance reviewed quarterly.

Frequently asked questions

What is the difference between a hard bounce and a soft bounce? A hard bounce is a permanent delivery failure — the address or domain doesn't exist, or the receiver permanently refuses — and the address should be suppressed. A soft bounce is a temporary failure like a full mailbox or busy server, handled by automatic retries.

Should I remove soft bounces from my email list? Not on the first occurrence. Remove addresses that soft-bounce persistently across multiple campaigns — repeated "temporary" failure usually marks an abandoned mailbox. Most platforms convert chronic soft bounces to suppressions automatically; check your platform's documented threshold.

Do soft bounces hurt my sender reputation? Occasional soft bounces are normal traffic and carry little weight. Chronic soft bouncing at scale hurts indirectly: it usually means a stale, unengaged list, and those correlated signals — not the 4xx responses themselves — are what receivers punish.

Can a hard-bounced address become valid again? Occasionally — a person rejoins a company, a domain's DNS problem gets fixed. But mailing into suppression on that hope costs more than it earns. The defensible route back is the subscriber re-confirming through a signup form, which lifts the suppression with fresh consent.

Why did a valid address hard bounce? Usually a receiver-side event: a migration, an overzealous gateway, a temporary DNS failure misclassified by the receiving side, or a reputation block returned as a permanent code. Domain-clustered or text-inconsistent bounces warrant investigation before you trust the label.

What bounce rate is acceptable? Platforms publish their own enforcement thresholds, and the working convention across the industry sits near a couple percent per campaign — the full context, including hard-versus-soft weighting, is in our bounce rate guide.

When the next bounce report lands, read it as a queue of decisions rather than a statistic: suppress the 5xxes, schedule the chronic 4xxes, and pull the bounce text on anything that smells like a block — starting with a reputation pass through the blacklist checker.