Not all email delivery failures are the same — understanding the difference between hard and soft bounces, and handling each appropriately, is essential for maintaining good sender reputation.
Hard Bounces
Permanent delivery failures — the address doesn't exist, the domain doesn't exist, or the recipient server permanently refuses the message — these will never succeed on retry.
Soft Bounces
Temporary delivery failures — a full mailbox, a temporarily unavailable server, a greylisting delay — these might succeed if retried later.
Why the Distinction Matters for Deliverability
Continuing to send to addresses that consistently hard bounce signals to receiving mail servers (and blacklist services) that you're not maintaining a clean list — a strong negative reputation signal that can affect deliverability for your entire domain/IP, not just the specific bounced messages.
Identifying Bounce Type from SMTP Response Codes
| Code Range | Type | Example |
|---|---|---|
| 5xx | Hard bounce (permanent failure) | 550 5.1.1 User unknown |
| 4xx | Soft bounce (temporary failure) | 450 4.2.2 Mailbox full |
Handling Hard Bounces: Suppress Immediately
Add hard-bounced addresses to a suppression list and never send to them again — this is standard, expected practice; continuing to send to known-invalid addresses is one of the most damaging things you can do to sender reputation.
Handling Soft Bounces: Retry with Backoff
Most mail transfer agents (Postfix included) automatically retry soft-bounced messages with increasing delays — if an address soft-bounces repeatedly over an extended period (commonly configurable, e.g. several days), treat it as effectively a hard bounce and suppress it.
Configuring Postfix's Bounce Queue Lifetime
sudo postconf -e "maximal_queue_lifetime=5d"
sudo postconf -e "bounce_queue_lifetime=5d"Controls how long Postfix keeps retrying before giving up and generating a final bounce notification.
Parsing Bounce Messages for Marketing/Transactional Platforms
If using dedicated email marketing software (see Best Email Marketing Software for a VPS), verify it correctly parses and categorizes bounce notifications automatically, updating recipient status without manual intervention for every bounce.
Setting Up Automated Bounce Processing
For high-volume sending, configure a dedicated bounce-handling mailbox and automated processing that parses bounce messages, categorizes them, and updates your suppression list programmatically — manual review doesn't scale for meaningful sending volume.
Monitoring Bounce Rates
See How to Monitor Email Deliverability and Sender Reputation — track your bounce rate over time; a rate significantly above what's typical for your list quality/type indicates a data hygiene problem needing attention.
Common Errors
Bounce rate climbing over time despite suppression — verify your suppression list is actually being checked before sending, not just recorded; a suppression list that exists but isn't consulted before send provides no actual protection.
Continue Reading
- How to Monitor Email Deliverability and Sender Reputation
- Email Marketing Best Practices & Common Pitfalls to Avoid
- How to Troubleshoot Email Not Sending or Going to Spam
Browse more articles in Email Hosting & Deliverability.
