Hard Bounces, Soft Bounces, and Suppression Lists: A Complete Guide

What Email Bounces Are Costing Your Deliverability

Every time you send an email, one of three things happens: it gets delivered, it gets filtered into spam, or it bounces. Bounces are the ones that come back with an error — and how you handle them has a direct impact on your sender reputation and long-term deliverability. Understanding the difference between bounce types and building a solid suppression strategy is one of the most practical steps any sender can take.

Hard Bounces vs Soft Bounces

Not all bounces are equal. The email industry splits them into two categories, and treating them the same is a common mistake that damages sender reputation faster than most people expect.

Hard Bounces

A hard bounce is a permanent delivery failure. The receiving server has told you clearly that this email address does not exist or will never accept mail. Common causes include:

• The email address doesn't exist (user unknown)
• The domain doesn't exist or has no MX records
• The recipient server has permanently blocked your sending address

Hard bounces generate SMTP 5xx errors — codes like 550 5.1.1 User unknown or 550 5.4.1 Recipient address rejected: domain not found. These are final rejections. There is no retry logic that will fix them.

Every hard bounce you ignore and continue sending to signals to ISPs that your list hygiene is poor. That signal accumulates. It doesn't take long for a reputation score to drop.

Soft Bounces

Soft bounces are temporary failures. The address exists, but delivery couldn't complete right now. Typical causes:

• The recipient's mailbox is full (over quota)
• The receiving server was temporarily unavailable
• The message was too large
• A transient network or DNS error

Soft bounces produce 4xx SMTP codes — like 452 4.2.2 Mailbox full or 421 Service temporarily unavailable. Most sending systems automatically retry these for 24–72 hours before giving up.

If an address soft bounces repeatedly across multiple send attempts over several days, it starts to look a lot like a dead address. Many senders treat an address as a hard bounce after 3–5 consecutive soft bounces with no successful delivery in between.

Why Bounce Rates Matter More Than You Think

ISPs like Gmail, Outlook, and Yahoo track bounce rates at the domain level. A bounce rate above 2% on a campaign is a yellow flag. Above 5% is a red one. At those levels, your messages start getting throttled or filtered — even the ones going to valid addresses.

The problem compounds: if you're sending from a shared IP pool, high bounce rates affect every other sender on that IP. That's why managed SMTP relay services enforce bounce rate limits and will suspend accounts that consistently exceed them. It's not punitive — it's infrastructure self-defense.

Suppression Lists: The Right Response to Bounces

A suppression list is a set of email addresses you've committed to never sending to again. Every serious email sender needs one. Here's what belongs on it:

• All hard bounce addresses — add them immediately and permanently
• All unsubscribe requests — required by CAN-SPAM and GDPR
• Addresses with repeated soft bounces (set a consistent threshold)
• Spam complaint addresses from feedback loop reports
• Known invalid addresses identified through list hygiene tools

Your suppression list isn't a sign of failure — it's evidence that your sending practices are mature. Most ESPs and SMTP platforms let you upload a suppression list directly, so new campaigns automatically exclude those addresses before a single message leaves your server.

How to Structure Suppression in Practice

Keep suppression data in a central store if you're sending across multiple systems or subdomains. The worst situation is suppressing an address in one system while a different tool sends to the same address because it maintains its own isolated list. Centralize suppression at the infrastructure level, not just at the campaign tool level.

If you're using a hosted email service, confirm that suppression is enforced globally across your account — not just within individual sending streams. Check your provider's documentation to understand how suppression lists are applied and whether they're shared across sub-accounts.

Monitoring and Auditing Bounce Data

Setting up suppression once isn't enough. You need to actively monitor bounce rates per campaign, per domain, and per IP. Look for patterns:

• A sudden spike in hard bounces often means someone imported an old or purchased list
• Consistent soft bounces to a particular domain could mean that domain is blocking your IP range
• High bounce rates on a new segment suggest that list segment was never properly validated

Most professional SMTP platforms expose bounce data through dashboards or webhook callbacks. If your provider supports webhooks, configure bounce events to feed into your CRM or database in real time — that way addresses get suppressed before the next campaign runs, not after you've reviewed a report manually.

List Hygiene Before You Send

The best way to reduce bounces is to validate addresses before they hit your sending infrastructure. Email verification services check whether an address actually exists at the mailbox level — not just whether the format looks correct. Run new lists through verification before your first send, especially if those addresses came from a form signup, import, or third-party source.

Equally important: don't let lists go cold. An address that was valid 18 months ago might be abandoned now. If a segment of your list hasn't been mailed in over six months, run it through verification again before re-engaging.

What Good Bounce Management Looks Like

A healthy sending operation handles bounces systematically, not reactively. That means:

1. Hard bounces get suppressed automatically and immediately
2. Soft bounces are tracked, and addresses with repeated failures get suppressed after a defined threshold
3. Suppression data is centralized and applied across all sending tools
4. Bounce rates are monitored per campaign and per domain segment
5. List hygiene runs before new segments are mailed for the first time

If you're building out email infrastructure or reviewing your current setup, talking to someone who handles this at scale can save you from discovering the hard way that your bounce rate has been quietly damaging your reputation for months. Check the MailDog FAQ for common questions about bounce handling, or browse the blog for more on building a solid sending foundation.