Soft bounce vs hard bounce: every difference that matters (and how to handle each)

• Which one hurts your sender reputation more? Hard bounces, fast. ISPs treat repeated hard bounces as a signal of bad list hygiene.
• Should you remove soft bounces from your list? Not on the first occurrence — most resolve. Suppress only after 3–5 consecutive soft bounces from the same address.
• What's the safe combined bounce rate? Below 1% total, including soft and hard. Above 2% is a warning sign for any consumer ESP.

The SMTP-code prefix is the cleanest technical signal. A response starting with 5 (e.g. 550 5.1.1 User unknown) is a hard bounce; a response starting with 4 (e.g. 421 4.7.0 Try again later) is soft. Your ESP translates these into 'hard' and 'soft' categories on the reporting screen.

A hard bounce means the receiving mail server has decided the address is permanently undeliverable. The most common reasons:

• The mailbox doesn't exist (550 5.1.1 User unknown)
• The domain has no MX record or the domain itself doesn't resolve
• The receiving server has rejected the mail for policy reasons (550 5.7.1 Message rejected)
• Your sender has been blocklisted by that specific server

There is no point retrying a hard bounce. The next attempt will get the same response, and each repeat tells the receiving ISP that you're not maintaining your list. ESPs that handle this for you suppress hard-bounced addresses automatically; if you're sending raw SMTP, you need your own suppression logic.

A practitioner on r/emailmarketing put the impact bluntly:

'Repeatedly sending to invalid addresses signals poor list management to ISPs and blocklist operators. Hard bounces should be eliminated immediately from your mailing list to prevent further damage to your sender reputation.'

A soft bounce is a temporary failure. The receiving server expects the same message to succeed if retried. Common causes:

• The recipient's mailbox is full
• The receiving server is down or overloaded
• The message hit a per-IP or per-domain rate limit
• Greylisting (server deliberately rejecting first attempts to filter spammers)
• Message size exceeds the recipient's inbox quota
• DNS resolution issues at the receiving end

Most ESPs auto-retry soft bounces for 24–72 hours. The user usually sees the mail eventually if the cause was transient. The exception is greylisting, which by design blocks the first attempt; well-configured senders pass on retry.

Soft bounces become problematic when they persist. The same address bouncing soft for five consecutive sends usually indicates an abandoned mailbox that has filled up and will never be cleared. Treat persistent soft bounces as effectively hard.

Hard bounces damage reputation in two ways. First, individual hard bounces signal poor list hygiene to receiving ISPs. Second, a high hard-bounce rate triggers ESP-level alerts — most ESPs throttle or pause sending if hard bounces exceed 2% on a single send.

Soft bounces are more insidious. They inflate your bounce rate slowly, and by the time the trend is obvious in the dashboard, the underlying reputation damage may already be done. A sender on r/emailmarketing posted a thread where their bounce rate climbed from 1% to 3% over six weeks of consistent soft bounces, at which point Gmail started filtering even legitimate mail to spam.

The combined safe rate, per the 2026 cross-industry benchmark:

• <1% total bounces: Excellent
• 1–2%: Acceptable
• 2–5%: Concerning, investigate immediately
• >5%: Dangerous, expect deliverability damage within days

These guidelines align with Litmus State of Email reports and the explicit thresholds in Gmail's bulk-sender requirements; individual ESPs vary on the exact internal threshold that triggers throttling.

For hard bounces, in order:

1. Suppress the address immediately from all future sends.
2. Move it to a permanent suppression list shared across your tools.
3. If the share of hard bounces on a send is >2%, pause the campaign and verify the rest of the list before resuming.
4. If hard bounces are climbing across consecutive campaigns, run a full list cleaning before your next major send.
5. Investigate the source. Hard bounces often cluster by acquisition source (a specific lead-gen vendor, a particular form).

For soft bounces, in order:

1. Let the ESP retry — most resolve within 24 hours.
2. Tag the address as 'soft-bounced' in your CRM with a count.
3. After 3–5 consecutive soft bounces from the same address, treat it as hard and suppress.
4. Monitor your overall soft-bounce trend monthly; an upward trajectory is an early warning of list decay.
5. Re-engage soft-bounced addresses through a different channel before suppressing if they're high-value.

Hard bounces are almost entirely preventable with email verification before send. The address either exists at the time of verification or it doesn't, and the verifier returns the answer in under a second.

Run the user.cleaning email verifier on:

• Every address at signup (real-time API, before account creation)
• The full list before a major campaign send
• The full list every 60–90 days even without a planned send

Verification doesn't help with soft bounces, by definition — they're transient. A mailbox that's full today might be empty tomorrow; no verifier can predict that. Soft bounces are managed through retry logic, suppression thresholds, and engagement monitoring instead.

Common codes you'll see in bounce notifications:

The exact text after the code varies by receiving server. The first digit is the reliable signal: 4xx always soft, 5xx always hard.