Hard Bounce vs Soft Bounce: Complete Guide | emails-wipes.com
Learn the difference between hard bounces and soft bounces, how to identify them, and best practices for managing bounce rates to protect sender reputation.
โฑ๏ธ 12 minute read | Published: February 10, 2026
Hard Bounce vs Soft Bounce: Complete Guide
TL;DR: Hard bounces are permanent delivery failures (bad email address). Soft bounces are temporary (full inbox, server down). Remove hard bounces immediately. Retry soft bounces 2-3 times before removing.
What Is an Email Bounce?
An email bounce occurs when a message cannot be delivered to the recipient's inbox. The receiving mail server rejects the email and sends a bounce message (Non-Delivery Report / NDR) back to the sender.
Bounces are categorized into two types based on permanence:
๐ด Hard Bounce
Permanent failure
The email address is invalid and will never accept mail.
Action: Remove immediately
๐ Soft Bounce
Temporary failure
The email address is valid but the message couldn't be delivered right now.
Action: Retry 2-3 times
Hard Bounce: Permanent Failures
What Causes Hard Bounces?
- Non-existent email address - user never existed or account closed
- Invalid domain - domain doesn't exist or has no mail server
- Syntax errors - malformed email address (e.g.,
user@domain,user@@domain.com) - Blocked sender - recipient's server has blacklisted your IP/domain
- Policy rejection - recipient's server rejects based on content rules
Common Hard Bounce SMTP Codes
| Code | Meaning | Example Message |
|---|---|---|
550 |
User not found | "550 5.1.1 User unknown" |
551 |
User not local | "551 User not local; please try <forward-path>" |
553 |
Mailbox name invalid | "553 Requested action not taken: mailbox name not allowed" |
554 |
Transaction failed | "554 5.7.1 Service unavailable; blocked" |
โ ๏ธ Hard Bounces Damage Sender Reputation
Every hard bounce signals to ISPs that you're not maintaining your email list. High hard bounce rates (>2%) can lead to:
- IP/domain blacklisting - Gmail/Yahoo block your messages
- Throttling - ISPs limit how many emails you can send
- Spam folder placement - 50-80% of emails go to spam
- ESP account suspension - Mailchimp/SendGrid shut down your account
Solution: Remove hard bounces immediately. Never retry.
Hard Bounce Examples
Example 1: User Unknown
550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
Cause: Email address doesn't exist
Action: Remove from list
Example 2: Domain Not Found
550 5.1.2 Host or domain name not found
Cause: Domain doesn't exist or has no MX records
Action: Remove from list
Example 3: Blacklisted Sender
554 5.7.1 Service unavailable; Client host [192.0.2.1] blocked using zen.spamhaus.org
Cause: Your IP is on a blacklist
Action: Check blacklist status, request delisting, improve list hygiene
Soft Bounce: Temporary Failures
What Causes Soft Bounces?
- Full mailbox - recipient's inbox is over quota
- Mail server down - temporary outage or maintenance
- Message too large - attachments exceed size limits
- Greylisting - server temporarily rejects first-time senders (anti-spam)
- DNS issues - temporary DNS resolution failures
- Connection timeout - server too slow to respond
Common Soft Bounce SMTP Codes
| Code | Meaning | Example Message |
|---|---|---|
421 |
Service not available | "421 4.3.2 Service not available, try again later" |
450 |
Mailbox unavailable | "450 4.2.1 Mailbox temporarily unavailable" |
451 |
Local error | "451 4.4.0 DNS temporary failure" |
452 |
Insufficient storage | "452 4.2.2 Mailbox full" |
โ How to Handle Soft Bounces
- First bounce: Wait 24-48 hours, retry
- Second bounce: Wait 72 hours, retry
- Third bounce: Mark as "inactive" or remove
Reason: Temporary issues (full inbox, server downtime) often resolve within 24-72 hours. However, persistent soft bounces (3+ in a row) indicate the address is effectively invalid.
Soft Bounce Examples
Example 1: Mailbox Full
452 4.2.2 <[email protected]> Mailbox full
Cause: Recipient's inbox is over quota
Action: Retry in 48 hours (user may clear inbox)
Example 2: Mail Server Down
421 4.3.0 <[email protected]> Temporary system problem. Try again later.
Cause: Mail server maintenance or outage
Action: Retry in 24 hours
Example 3: Greylisting
450 4.7.1 Greylisted, please try again later
Cause: Anti-spam mechanism (rejects first-time senders temporarily)
Action: Most ESPs auto-retry; typically succeeds on second attempt
Hard Bounce vs Soft Bounce: Side-by-Side Comparison
| Criteria | Hard Bounce ๐ด | Soft Bounce ๐ |
|---|---|---|
| Permanence | Permanent failure | Temporary failure |
| SMTP Code Range | 5xx (500-599) | 4xx (400-499) |
| Cause | Invalid email address | Temporary server/mailbox issue |
| Will future sends work? | No, never | Maybe (after issue resolves) |
| Action | Remove immediately | Retry 2-3 times |
| Impact on reputation | High (severe damage) | Low (if infrequent) |
| Typical rate | 1-3% (well-maintained lists) | 0.5-2% (normal operations) |
Bounce Rate Thresholds
ISPs evaluate your sender reputation based on bounce rate (percentage of emails that bounce).
๐ Industry Standards
| Bounce Rate | Status | Impact |
|---|---|---|
| < 0.3% | โ Excellent | Gmail/Yahoo 2024 requirement |
| 0.3% - 2% | โ Good | Normal, minimal impact |
| 2% - 5% | โ ๏ธ Warning | Deliverability degradation |
| 5% - 10% | ๐ด Critical | High blacklist risk |
| > 10% | ๐ Catastrophic | ESP account suspension likely |
Best Practices for Managing Bounces
1. Implement Bounce Processing
Most ESPs (Mailchimp, SendGrid) automatically process bounces. If using custom infrastructure:
- Parse bounce messages (NDR emails)
- Classify as hard or soft based on SMTP code
- Update email status in database
- Suppress hard bounces from future sends
2. Hard Bounce Handling
๐จ Hard Bounce Protocol
- Immediate suppression - add to "do not send" list instantly
- Never retry - hard bounces are permanent
- Remove from active lists - archive or delete
- Investigate patterns - if >5% hard bounce, audit list source
3. Soft Bounce Handling
โ Soft Bounce Protocol
- First soft bounce: Wait 24-48 hours, retry once
- Second soft bounce: Wait 72 hours, retry once
- Third soft bounce (within 30 days): Treat as hard bounce, remove
- Track soft bounce count: 3+ consecutive = likely invalid
4. Monitor Bounce Rate Trends
Set up alerts for bounce rate anomalies:
- Daily bounce rate > 3% โ Investigate immediately
- Sudden spike โ Check for list import errors or compromised data
- Gradual increase โ List decay (emails aging), schedule list revalidation
5. Use Email Validation to Prevent Bounces
The best bounce management is prevention:
๐ก๏ธ Validation Prevents Bounces
- Before first send: Validate new lists (removes 10-30% invalids)
- At signup: Real-time email validation catches typos
- Quarterly: Revalidate entire list (combat 22.5% annual decay)
Result: Bounce rate < 0.3%, excellent sender reputation
Advanced: Decoding Extended Status Codes
SMTP error codes use a 3-digit format (e.g., 550), but many servers also provide an extended status code in Y.Y.Y format (e.g., 5.1.1).
Extended Code Format: X.Y.Z
| Position | Meaning | Values |
|---|---|---|
| X (Class) | Success/Failure type |
2 = Success 4 = Temporary failure 5 = Permanent failure |
| Y (Subject) | What failed |
0 = Undefined 1 = Addressing 2 = Mailbox 3 = Mail system 4 = Network/Routing 5 = Mail delivery protocol 6 = Message content 7 = Security/Policy |
| Z (Detail) | Specific reason | 0-999 (varies by subject) |
Common Extended Codes
| Code | Meaning | Type |
|---|---|---|
5.1.1 |
Bad destination mailbox address | Hard Bounce |
5.1.2 |
Bad destination system address | Hard Bounce |
4.2.2 |
Mailbox full | Soft Bounce |
5.7.1 |
Delivery not authorized (blocked) | Hard Bounce |
4.4.0 |
DNS temporary failure | Soft Bounce |
Bounce Handling by ESP
Mailchimp
- Hard bounces: Automatically removed from lists
- Soft bounces: Tracked, removed after 5 consecutive soft bounces
- Reactivation: Can manually "reconfirm" soft bounced addresses
SendGrid
- Hard bounces: Suppressed automatically
- Soft bounces: Retry for 72 hours, then suppress if unresolved
- Suppression list: Global suppression across all sends
Mailgun
- Hard bounces: Added to suppressions, never retried
- Soft bounces: Retry with exponential backoff (up to 8 hours)
- Webhooks: Real-time bounce notifications
Frequently Asked Questions
Q: Should I ever retry a hard bounce?
A: No, never. Hard bounces are permanent. Retrying damages your sender reputation and wastes resources.
Q: How many times should I retry a soft bounce?
A: 2-3 times maximum, with 24-72 hour gaps. After 3 soft bounces within 30 days, treat as hard bounce.
Q: What's a "block bounce"?
A: A hard bounce where the recipient's server has blocked your IP/domain. Requires delisting and improved list hygiene.
Q: Can a soft bounce become a hard bounce?
A: Yes. Persistent soft bounces (3+ consecutive) indicate the email is effectively invalid and should be removed.
Q: How do I reduce bounce rates?
A: Use email validation before sending, implement double opt-in, revalidate lists quarterly.
Q: What's an acceptable bounce rate?
A: <0.3% is excellent (Gmail/Yahoo requirement). 0.3-2% is acceptable. >2% requires immediate action.
Action Plan: Reducing Your Bounce Rate
โ 30-Day Bounce Reduction Plan
Week 1: Audit
- Export your email list
- Calculate current bounce rate (last 30 days)
- Separate hard bounces from soft bounces
- Identify patterns (domain clusters, list sources)
Week 2: Clean
- Remove all hard bounces immediately
- Validate entire list with emails-wipes.com
- Remove/suppress invalid addresses
- Set up bounce processing automation
Week 3: Prevent
- Implement double opt-in for new signups
- Add real-time email validation to forms
- Set up bounce rate alerts
- Document bounce handling procedures
Week 4: Monitor
- Track daily bounce rates
- Review soft bounce retry results
- Measure deliverability improvement
- Schedule quarterly revalidation
Expected Result: Bounce rate < 0.5%, 95%+ deliverability, improved sender reputation
Key Takeaways
- โ Hard bounces = permanent - remove immediately, never retry
- โ Soft bounces = temporary - retry 2-3 times, then remove
- โ SMTP codes: 5xx = hard, 4xx = soft
- โ Target bounce rate: < 0.3% (Gmail/Yahoo requirement)
- โ Prevention > management - validate before sending
- โ Automate bounce processing - manual tracking doesn't scale
- โ Monitor trends - sudden spikes indicate list quality issues
๐ Eliminate Bounces Before They Happen
Validate your email list and reduce bounce rate to <0.3%
โ 98.5% accuracy | โก < 2 seconds per email | ๐ GDPR compliant
$0.75 per 1,000 emails with code REDDIT50
Start Validation Now โRelated Articles
- Why Email Validation Matters - ROI and business impact
- SMTP Bounce Codes Guide - Complete error code reference
- Email Deliverability Guide 2024 - Inbox placement strategies
Related Articles
How to Reduce Email Bounce Rate by 90%
Learn proven strategies to reduce your email bounce rate by up to 90%. Understand hard vs soft bounces, fix deliverabili...
February 09, 2026 ยท 10 min readHow to Reduce Email Bounce Rate: 7 Proven Strategies
Lower your email bounce rate with these 7 proven strategies. Protect your sender reputation and boost deliverability wit...
February 10, 2026 ยท 5 min readComplete Guide to SMTP Bounce Codes and Error Messages
Decode every SMTP bounce code and error message. Learn the difference between 4xx and 5xx errors, how to fix them, and w...
January 02, 2026 ยท 12 min read