How many soft bounces before suppressing an address?

Three to five soft bounces across separate campaigns is the working rule most senders land on. That gives temporary problems (a full mailbox, a server hiccup, a greylist) time to clear without letting a dead address rot on your list and drag your reputation down.

But the number itself is less important than how you count.

What counts as a soft bounce

A soft bounce is a 4xx SMTP response. The receiving server is saying "not now, try later." Common reasons:

• Mailbox full (4.2.2)
• Greylisting (4.7.x)
• Temporary connection or rate-limit issue (4.4.x)
• Message size or policy reasons (4.5.x, 4.7.x)

A hard bounce is a 5xx. That address is dead, done, suppress on the first one. There is no counter to debate. See RFC 3463 for the enhanced status code definitions if you want the spec.

The counter conversation only applies to softs.

The 3 to 5 rule, in practice

For most B2C senders mailing weekly or more often, suppress after 3 consecutive soft bounces across separate sends. That is roughly three weeks of "this address still will not accept mail." At that point you are not dealing with a temporary issue, you are dealing with an abandoned mailbox or a permanent block dressed up as a 4xx.

For lower-frequency senders (monthly newsletter, quarterly update), 3 sends is 3 months to a year of waiting. Tighten the rule: suppress after 2 consecutive softs, or after a single soft that repeats on the very next send.

For high-volume daily senders, you can stretch to 5 because greylisting and transient rate limits show up more often. The faster you cycle, the more noise you will see in the counter.

Reset the counter on success

This is the part most ESP defaults get wrong. If an address soft-bounces twice, then accepts mail on the third send, reset the counter to zero. Otherwise you are accumulating bounces across the whole lifetime of the address and will suppress people who briefly had a full inbox six months ago.

Count consecutive softs since the last successful delivery, not cumulative.

What to actually track

In your ESP or your own data, you want at minimum:

• soft_bounce_count (consecutive, resets on accept)
• last_soft_bounce_at (timestamp)
• last_soft_bounce_code (the 4xx, parsed)
• last_successful_delivery_at

The 4xx code matters because some "soft" bounces are not temporary at all. A 4.7.1 with text like "blocked" or "policy" is the receiving server politely telling you to stop. Those should suppress faster than a 4.2.2 mailbox-full. M3AAWG's Sender Best Common Practices covers the reasoning if you want the long version.

When you should not even be having this conversation

If you are seeing soft bounce rates above 2 to 3 percent on a campaign, the counter rule is not your problem. Your acquisition source is. Clean the list before you send, not after. See how often to clean a list and what list hygiene actually means.

If the bounces are concentrated on one provider (Gmail spiking soft, the rest fine), it is a reputation issue with that provider, not a list issue. The suppression rule will not fix it. You need to look at your sender reputation and engagement.

The short version

• Hard bounce: suppress on the first one.
• Soft bounce: 3 consecutive across separate campaigns for most senders, 2 for low-frequency senders, up to 5 for daily senders.
• Reset the counter the moment an address accepts mail again.
• Watch the 4xx code, not just the count. A 4.7.x block is not the same as a 4.2.2 full mailbox.
• If your soft rate is above 2 to 3 percent, fix acquisition before you fix the counter.