Email bounces are delivery failures — messages that couldn't be delivered to the recipient's inbox. Every bounce is a signal that something went wrong between your sending server and the destination mailbox. Not all bounces are equal, though, and handling them incorrectly can seriously damage your sender reputation and long-term deliverability. Knowing the difference between bounce types, what causes them, and how to respond is one of the most practical skills in email marketing.
What Is an Email Bounce?
When you send an email, your sending server communicates with the recipient's mail server using SMTP — the Simple Mail Transfer Protocol. If the receiving server can't accept the message, it returns a numeric status code explaining why. These codes are the foundation of bounce classification, and understanding them helps you diagnose problems quickly.
A bounce is different from a block. A block happens when a receiving server refuses your connection entirely — often because your IP or domain is on a blocklist. A bounce occurs after the connection is established but the message itself is rejected. Both hurt deliverability, but they have different root causes and require different remedies.
Bounces fall into two broad categories based on whether the failure is permanent or temporary: hard bounces and soft bounces. Your ESP should track both, but how you respond to each is very different.
Hard Bounces: Permanent Failures
A hard bounce is a permanent delivery failure. The receiving server has definitively rejected the message, and retrying will not change the outcome. Hard bounces are the most damaging type because they signal to ISPs that you're sending to addresses that don't exist or have been permanently blocked — a hallmark of poor list hygiene.
Common causes of hard bounces include:
- Invalid email address — the address was never valid, was mistyped at signup, or has been deleted
- Domain doesn't exist — the domain in the email address has expired or was never registered
- Address permanently blocked — the recipient's server has permanently rejected your sending identity
The correct response to a hard bounce is immediate and permanent suppression. Remove the address from your list the moment you receive the bounce notification — never retry it. Continuing to send to hard-bounced addresses is one of the fastest ways to destroy your sender reputation. Most ESPs will suppress hard bounces automatically, but you should verify this is happening and audit your suppression list regularly.
The best way to prevent hard bounces is to verify addresses before they ever reach your list. Bulk email verification catches invalid addresses at the source, before they generate bounces that damage your reputation.
Soft Bounces: Temporary Failures
A soft bounce is a temporary delivery failure. The address is valid and the domain exists, but something prevented delivery at the time of sending. Unlike hard bounces, soft bounces may resolve on their own — which is why the correct response is a structured retry strategy rather than immediate suppression.
Common causes of soft bounces include:
- Mailbox full — the recipient's inbox has exceeded its storage quota
- Server temporarily unavailable — the receiving mail server is down or experiencing issues
- Message too large — your email exceeds the size limit set by the receiving server
- Greylisting — the server is temporarily deferring mail from unknown senders as an anti-spam measure
The standard retry strategy for soft bounces is 3–5 attempts spread over 72 hours. Most ESPs handle this automatically. If the message still hasn't delivered after the retry window, suppress the address. An address that soft-bounces repeatedly over multiple campaigns should be treated as a hard bounce and removed permanently — it's unlikely to become deliverable.
🔴 Hard Bounce
- ✗ Permanent failure
- ✗ Address is invalid or blocked
- ✗ Retrying makes things worse
- ✓ Action: suppress immediately
- ✓ Never send to this address again
🟡 Soft Bounce
- ✓ Temporary failure
- ✓ Address is valid
- ✓ May resolve on its own
- ✓ Action: retry 3–5 times over 72 hours
- ✗ Suppress if still failing after retries
Common Bounce Codes and What They Mean
SMTP response codes are three-digit numbers. Codes starting with 5xx indicate permanent failures (hard bounces); codes starting with 4xx indicate temporary failures (soft bounces). Here are the most common ones you'll encounter:
| Code | Type | Meaning | Action |
|---|---|---|---|
| 550 | Hard | User unknown — address doesn't exist | Suppress immediately |
| 551 | Hard | User not local — address has moved or is invalid | Suppress immediately |
| 552 | Soft | Mailbox full — storage quota exceeded | Retry, then suppress |
| 421 | Soft | Service temporarily unavailable — server is down | Retry automatically |
| 450 | Soft | Mailbox unavailable — temporary issue on receiving end | Retry, then suppress |
How Bounces Damage Your Sender Reputation
Every bounce is a negative signal to ISPs. When your bounce rate climbs above 2%, receiving servers start to question the quality of your list. Above 5%, you risk being throttled, filtered to spam, or blocked entirely. The damage compounds: a high bounce rate lowers your sender reputation score, which causes more mail to be filtered, which reduces engagement, which lowers your score further.
The feedback loop is particularly punishing because reputation damage is slow to repair. ISPs update scores in near real-time based on observed behavior, but rebuilding trust after a sustained period of high bounces can take weeks of clean sending. Prevention is always cheaper than recovery.
Hard bounces are the more damaging of the two types because they signal that you're sending to addresses that definitively don't exist — a pattern associated with purchased lists and poor acquisition practices. Even a small number of hard bounces per campaign accumulates into a meaningful reputation signal over time.
How to Reduce Your Bounce Rate
Reducing your bounce rate is primarily a list quality problem. Here's what actually moves the needle:
Verify before you send. Running your list through email list hygiene checks before a campaign can surface invalid, risky, and undeliverable addresses before they generate avoidable bounces. It is one useful part of a broader sending-quality program.
Use double opt-in. Requiring subscribers to confirm their email address eliminates typos and fake signups at the source. Double opt-in lists consistently have lower bounce rates and higher engagement than single opt-in lists.
Clean your list regularly. Bulk verification should be a recurring process, not a one-time event. Addresses can stop working as people change jobs, abandon accounts, and switch providers, so an older result should not be treated as a permanent guarantee.
Monitor after every send. Review your bounce report within 24 hours of each campaign. Look for sudden spikes in either hard or soft bounces — they often indicate a specific segment or acquisition source with quality problems.
The Role of Email Verification in Bounce Prevention
Email verification can reduce avoidable bounces by checking address syntax, domain and mail server configuration, mailbox responses, and risk signals before you attempt delivery. It can identify some clear failures, but catch-all servers, temporary responses, and other limits can leave an address uncertain. It does not guarantee delivery or definitively identify spam traps.
Verification gives you evidence before a send instead of relying only on a later bounce. Use that evidence alongside consent, suppression, engagement, authentication, and campaign monitoring when deciding which addresses to contact.
For a complete picture of how bounce prevention fits into the broader deliverability landscape, see our email deliverability guide. It covers authentication, reputation, list hygiene, and inbox placement in a single end-to-end framework.