Soft Bounce vs Hard Bounce: The Difference

A hard bounce is a permanent delivery failure — the address doesn't exist, and it never will. A soft bounce is a temporary one — the mailbox is full, the server is down, or the message is too large. Hard bounces must be removed from your list immediately. Soft bounces get retried, then removed if they keep failing.

The distinction that actually matters

Every bounce arrives with an SMTP response code, and that code is what separates the two categories. Codes in the 5xx range are permanent failures. Codes in the 4xx range are transient. Your email platform reads the code and classifies the bounce automatically.

The practical consequence: a hard bounce is a signal about the address, and a soft bounce is a signal about the moment. Treating them the same way is how sender reputations get destroyed. Repeatedly hammering addresses that returned 550 tells mailbox providers you either bought your list or you don't process bounces — and both conclusions land you in the spam folder.

	Hard bounce	Soft bounce
SMTP code range	5xx	4xx
Nature	Permanent	Temporary
Typical cause	Address doesn't exist, domain doesn't exist	Mailbox full, server busy, greylisting, message too big
Retry?	Never	Yes, automatically for 24–72 hours
Action	Suppress immediately	Track and suppress after repeat failures
Reputation impact	Severe if the rate is high	Mild unless chronic
Healthy rate	Under about 0.5%	Under about 2%

What causes hard bounces

Hard bounces almost always trace back to how an address entered your list, not how you sent to it.

• Typos at signup. gmial.com, yaho.com, a missing letter in the local part. Extremely common on forms without validation.
• Abandoned or deprovisioned mailboxes. Someone leaves a company and IT deletes the account. This is why B2B lists decay faster than consumer lists.
• Fake addresses. People typing no@no.com to get past a gated download.
• Dead domains. The company folded or the domain lapsed, so there's no MX record to deliver to.
• Purchased or scraped lists. The fastest way to a double-digit hard bounce rate and a suspended account.

Common 5xx responses you'll see in bounce logs:

• 550 5.1.1 User unknown — the mailbox doesn't exist
• 550 5.1.2 Host unknown — the domain has no mail server
• 553 5.3.0 Invalid recipient — rejected as malformed or nonexistent
• 554 5.7.1 Message rejected — often a blocklist or policy rejection, and worth reading carefully because it can indicate a reputation problem rather than a bad address

That last one deserves attention. Some platforms classify 554 as a hard bounce, but a policy rejection is a message about you, not the recipient. If you see a cluster of them from one provider, you have a reputation issue to investigate, not a batch of addresses to delete.

What causes soft bounces

Soft bounces are noise most of the time. The receiving server is saying "not right now" rather than "not ever."

• Mailbox over quota — 452 4.2.2. The single most common soft bounce.
• Server temporarily unavailable — 421 4.3.2. Maintenance, outage, overload.
• Greylisting — the receiver deliberately rejects a first attempt from an unfamiliar sender and accepts the retry. Normal, and it resolves on its own.
• Rate limiting — 421 4.7.0. You're sending too fast for that provider, common during a warm-up or a sudden volume spike.
• Message too large — an oversized image or attachment exceeding the recipient's limit.
• Content-based deferral — the message triggered a filter and was held rather than rejected outright.

Your sending platform retries soft bounces on a backoff schedule, typically for 24 to 72 hours. Many resolve without you doing anything.

How to handle each one

For hard bounces, the rule is simple and non-negotiable: suppress on the first occurrence. Any reputable platform does this automatically, and you should never override it. Then work backward — if a batch of hard bounces all came from one signup source, that source needs validation.

For soft bounces, use a threshold. A reasonable policy:

1. Let the platform retry automatically over the first 72 hours.
2. If an address soft bounces on three consecutive campaigns, flag it.
3. If it soft bounces on five consecutive campaigns, suppress it. A mailbox that has been full for a month is functionally abandoned.
4. Investigate patterns. Twenty soft bounces spread across providers is normal. Two hundred from a single provider on one day is a rate-limit or reputation signal, not a list problem.

The bounce rates you should be hitting

Bounce rate is calculated as bounces divided by total sends. Rough targets for a healthy list:

Metric	Healthy	Watch	Act now
Hard bounce rate	Under 0.5%	0.5%–2%	Over 2%
Soft bounce rate	Under 2%	2%–5%	Over 5%
Total bounce rate	Under 2%	2%–5%	Over 5%

Most sending platforms take enforcement action somewhere above the 5% total bounce mark, and mailbox providers start throttling well before that. If a single campaign comes back with a 10% hard bounce rate, stop sending to that segment entirely until it's been verified — continuing will cost you far more than the campaign is worth.

Preventing bounces before they happen

Bounce management is damage control. Prevention is cheaper.

• Validate at the point of capture. Real-time syntax and MX checks on your signup form catch typos while the person is still on the page and can fix them.
• Use confirmed opt-in for high-risk sources. Contest entries, gated content and offline collection benefit most.
• Verify before big sends. Run any list you haven't mailed in 90+ days through a verifier first. The free email verifier flags invalid, disposable and role-based addresses before they cost you reputation.
• Never import a purchased list. There is no cleaning process that makes bought data safe.
• Mail consistently. Lists decay at roughly 20–30% per year. Regular sending surfaces dead addresses gradually instead of all at once.
• Sunset dormant subscribers. Addresses that haven't engaged in a year are disproportionately likely to have become spam traps.

That last point matters more than it sounds. A recycled spam trap is an address that hard bounced for months, then got reactivated by the provider specifically to catch senders who ignore bounces. If you had processed the hard bounce the first time, you'd never have hit it. For a fuller walkthrough of validation workflows and how they fit into list hygiene, see the guide to email verification.

Reading your bounce log like a diagnostician

The pattern tells you more than the number. Three quick reads:

• Hard bounces clustered in one import batch → bad list source. Find where those contacts came from and fix or remove the source.
• Soft bounces clustered at one provider on one day → rate limiting or a temporary block. Slow your send rate to that provider and check your authentication.
• Bounce rate climbing gradually across all providers → natural list decay. Time for a verification pass and a sunset policy.

Frequently asked questions

What is a good bounce rate for email marketing?

Under 2% total is healthy, with hard bounces ideally below 0.5%. Above 5% total, most sending platforms and mailbox providers begin throttling or restricting your account.

Do soft bounces hurt my sender reputation?

Occasional soft bounces are normal and largely harmless. Chronic soft bounces to the same addresses across many campaigns do hurt, because repeatedly mailing mailboxes that never accept messages looks like poor list management.

Should I ever email an address that hard bounced?

No. A hard bounce means the address is permanently invalid, and continuing to send to it is a strong negative signal to mailbox providers. Suppress it on the first occurrence.

How many times should a soft bounce occur before I remove the address?

Three to five consecutive campaigns is a sensible threshold. Automatic retries handle genuine temporary issues within 72 hours, so an address still failing after five sends is effectively dead.

Can good emails bounce for reasons unrelated to the address?

Yes. Oversized messages, blocklisted sending IPs, missing SPF or DKIM records, and provider rate limits all produce bounces on perfectly valid addresses. Read the SMTP code before assuming the recipient is at fault.

Tired of guessing which addresses are killing your deliverability? Start with IGSendMail — automatic bounce handling and suppression, built-in verification, 99% inbox deliverability, and unlimited contacts on paid plans from $19/mo.