Does my ESP handle bounce processing automatically?

Yes, every major ESP processes bounces automatically. That is the easy part. The hard part is knowing what your ESP actually does with the data, because the rules vary and the defaults are not always sender-friendly.

When a mailbox provider rejects your message, the receiving server sends back an SMTP reply code. Hard bounces are permanent failures (550, 5.1.1 user unknown). Soft bounces are temporary (421, 4.2.1 mailbox busy, 4.7.0 throttled). Your ESP reads those codes, maps them to its own categories, and decides whether to suppress the address, retry later, or keep trying. The standard for these codes is RFC 3463 for enhanced status codes and RFC 5321 for basic SMTP replies.

Here is what the big ESPs do by default:

• Mailchimp suppresses hard bounces immediately. Soft bounces get retried, and an address moves to cleaned status after roughly 7 soft bounces in a row. See Mailchimp's bounce documentation.
• Klaviyo suppresses hard bounces on the first occurrence. Soft bounces are retried for 7 days, after which the address is suppressed. Documented in Klaviyo's bounce guide.
• HubSpot auto-suppresses hard bounces. Soft bounces trigger suppression after 5 in a row to the same address.
• SendGrid drops hard bounces into a suppression group immediately. Soft bounces are retried up to 72 hours before being classified as a block.
• Brevo (formerly Sendinblue) marks hard bounces as blocked. Repeated soft bounces (usually 3-5) also move to blocked.
• ActiveCampaign suppresses hard bounces and lets you configure soft bounce thresholds.

The number that matters is the threshold, not the fact that suppression exists. An ESP that retries a soft bounce for 7 days is more forgiving than one that gives up after 24 hours. That matters when a real subscriber's mailbox is temporarily full or their corporate mail server is having a bad afternoon.

What ESPs do NOT do automatically:

1. Catch invalidations before sending. If you import a list with 8% known-bad addresses, your ESP will happily send to all of them, log the bounces, and ding your reputation. This is why validation up front beats waiting for bounces.
2. Flag spam traps. A pristine trap looks like a normal address until you hit it. Your ESP cannot tell the difference. See how ISPs detect poor hygiene.
3. Catch engagement decay. Addresses that accept mail but never open are still "deliverable" to your ESP. They are dead weight to inbox placement. We cover this in silent hygiene issues.
4. Read the bounce reason in detail. Most ESPs collapse dozens of distinct SMTP reasons into 2-3 buckets. A 550 5.7.1 (blocked by recipient policy) is treated the same as a 550 5.1.1 (user unknown), even though one is a reputation problem and one is a list problem.

What to actually do:

• Open your ESP's bounce documentation and write down the exact soft bounce threshold. If you cannot find it, ask support. "We suppress after a few bounces" is not an answer.
• Export your suppression list quarterly and look at the bounce reasons. Patterns matter. If 40% of your hard bounces come from one acquisition source, that source has a problem.
• Do not rely on bounces alone to keep your list clean. By the time an address bounces, the damage to your reputation is done. Most senders should clean before importing and re-validate engaged-but-aging segments every 3-6 months. See how often to clean a list.

Automatic bounce processing is a safety net, not a strategy. It catches what slips through. It does not replace knowing what is on your list before you send.