When should soft bounces be converted to hard bounces?

You've sent to an address three times. It bounced soft each time. Now you're wondering: is this address ever coming back, or are you just making noise? That's the soft-to-hard conversion question, and the answer depends on the type of bounce you're seeing.

The widely accepted rule of thumb is 3 to 5 consecutive soft bounces within a 30-day window. After that, you're not waiting for recovery. You're wasting sends on an address that's almost certainly not going to deliver.

But not all soft bounces age the same way. A "mailbox full" bounce (error code 452) might genuinely clear up in a day or two if the user cleans their inbox. A repeated server timeout on the same address over several weeks is a different story. Pattern matters more than raw count sometimes.

Here's a practical way to think about conversion thresholds by bounce type:

• Mailbox full: retry for 7 to 10 days. If it hasn't cleared, convert.
• Server timeout or connection refused: 3 to 5 retries over 7 days before converting.
• Policy or rate limit rejections: these can look soft but may signal a spam reputation issue on your side. Worth investigating before assuming the address is dead.

A tiered approach works well here. After the first couple of soft bounces, reduce send frequency for that address. After the threshold is crossed, suspend sends entirely. Convert to hard after the full window expires with no successful delivery. This gives legitimate addresses a chance to recover while you're not hammering a dead one.

Whatever threshold you pick, document it and apply it consistently. Different rules across different lists or campaigns will muddy your bounce reporting and make it harder to spot real patterns. Most reputable ESPs let you configure automatic conversion rules so you're not doing this by hand for every address.

If you're unsure how many retries are standard before giving up, the retry question is worth reading first.