What’s the difference between hard suppression and temporary quarantine?

You send an email. It fails. Now what? Do you delete that address forever, or give it a second chance? That's exactly the question that separates hard suppression from temporary quarantine, and getting it wrong costs you either deliverability or good contacts you shouldn't have thrown away.

Hard suppression means permanent removal from sending. The address goes on a list your system will never send to again, no expiry, no retry. It takes a manual override to undo it. You use this when the failure is definitive: a hard bounce like "user doesn't exist", a permanent policy rejection from the receiving server, or a spam complaint. There's no recovery scenario here. The address is genuinely gone or genuinely hostile.

Temporary quarantine (sometimes called a hold) pauses sending to an address for a defined window while you figure out what's happening. Common timelines are 7, 14, or 30 days, depending on your program. After that window, the address either gets cleared for sending or escalates to hard suppression if the problem persists. You use this for repeated soft bounces (mailbox full, server temporarily down), suspicious engagement patterns, or addresses that need verification before you retry.

Here's a quick decision guide:

• Hard bounce (user unknown, domain doesn't exist): hard suppression, immediately.
• Spam complaint: hard suppression, immediately.
• Repeated soft bounces (3+ in a row): quarantine for 14-30 days, then reassess.
• Single soft bounce: no action yet. One soft bounce doesn't tell you much.
• Suspicious pattern (sudden engagement drop, possible role address): quarantine and investigate.

The practical difference is reversibility. Hard suppression protects your sender reputation by making sure you never retry a dead-end address. Quarantine protects good contacts by giving recoverable situations time to resolve before you make a permanent call. Both live as separate status flags in your system, or on separate suppression lists.

One thing worth noting: most ESPs handle hard suppression automatically after a confirmed hard bounce. Quarantine logic is usually something you configure yourself, or rely on your platform's bounce-handling rules. If you're not sure what your current setup does, it's worth checking. Addresses that keep getting retried after multiple soft bounces are a quiet deliverability drain that's easy to miss.

If you want to dig into how bounce types feed into these decisions, our SOS hotline is free and we're happy to walk through your specific setup.