
The soft bounce vs hard bounce distinction comes down to one question: is the failure temporary or permanent? A soft bounce is a temporary rejection — a full mailbox, a busy server, a rate limit — and the message may be delivered on retry. A hard bounce is permanent — the address doesn't exist or the server refuses you — and retrying won't help. Getting this right matters for cold email, because repeated hard bounces tell mailbox providers your list is poor. This guide explains how to tell them apart from SMTP codes, the common causes of each, how to handle retries, and how to keep bounce rates low.
Soft Bounce vs Hard Bounce: The Short Answer
Soft bounce | Hard bounce | |
|---|---|---|
Nature | Temporary | Permanent |
SMTP reply code | Usually 4xx | Usually 5xx |
Typical causes | Mailbox full, server busy, rate limited, greylisting | Address doesn't exist, domain invalid, blocked |
Retry? | Yes, automatically | No |
Action | Watch; suppress after repeated failures | Remove immediately |
Google explains that codes starting with 4 are temporary failures and codes starting with 5 are permanent failures requiring action (Google: About SMTP error messages).
How to Tell Them Apart From SMTP Codes
A bounce message includes a three-digit reply code (like 550) and often an enhanced status code (like 5.1.1). The first digit tells you the class:
Example | Type | Meaning |
|---|---|---|
421 4.7.0 | Soft | Temporary deferral, often rate or reputation related |
450 4.2.1 | Soft | Recipient receiving mail too quickly |
452 4.2.2 | Soft | Recipient mailbox out of storage |
550 5.1.1 | Hard | Address doesn't exist |
550 5.7.1 | Hard (policy) | Rejected by policy — see SMTP 550 5.7.1 |
554 5.7.x | Hard (policy) | Blocked, often for reputation or content |
Full reference: SMTP error codes explained and Google's Gmail SMTP error list.
Common Causes of Soft Bounces
📦Mailbox full
The recipient's storage is exhausted.
⏳Greylisting
The server asks unknown senders to retry later.
🚦Rate limiting
You're sending too much, too fast, to one provider.
🛠️Server unavailable
Maintenance or outage on the receiving side.
📏Message too large
Attachments over the receiver's limit.
🛡️Temporary reputation deferral
The receiver is unsure about you — a warning sign.
Common Causes of Hard Bounces
❌Invalid address
Typos, departed employees, guessed formats.
🌐Invalid domain
No MX record or the domain no longer exists.
🚫Blocked sender
Policy or reputation-based rejection.
🔐Authentication failure
SPF, DKIM or DMARC requirements not met (authentication guide).
🧱Recipient restrictions
The mailbox only accepts internal or approved senders.
How to Handle Each Type
Situation | What to do |
|---|---|
Single soft bounce | Let your sequencer retry; no action yet |
Repeated soft bounces to one address | Suppress after several failed attempts across days |
Soft bounces across many recipients | Slow down; you may be rate limited or deferred |
Hard bounce (5.1.x) | Remove the address permanently |
Policy hard bounces (5.7.x) rising | Pause the inbox and check authentication and reputation |
Track bounces per inbox, not just per campaign, so a problem inbox is visible quickly (bounce rate thresholds, bounce fixes).
How Bounces Affect Cold Email Deliverability
High hard-bounce rates signal poor list quality, a classic marker of unsolicited bulk mail. Providers may respond with deferrals (soft bounces) and then rejections. Prevention is simple: verify every list (verification tools, ZeroBounce pricing), refresh old data, and avoid guessed addresses. If bounces spike mid-campaign, see mid-campaign drop fixes and deliverability recovery.
Example: Reading a Bounce Report
Illustrative scenario. A campaign shows 6% bounces. Breaking them down: most are 550 5.1.1 (unknown user) from one purchased list segment, a handful are 452 4.2.2 (mailbox full), and a few are 421 deferrals from one provider on one inbox. The team removes all 5.1.1 addresses, re-verifies the segment, lets the 4.2.2 addresses retry, and lowers the daily cap on the deferred inbox. The fix targets each cause rather than pausing everything.
Prevent Bounces Before They Happen
Bounce prevention is mostly setup discipline:
🔐Authenticate every domain
SPF, DKIM and DMARC aligned (authentication guide, Google Workspace setup, Microsoft 365 setup).
🌐Use secondary sending domains
Keep your main domain out of cold outreach (domain setup, domain risks).
🔥Warm or start pre-warmed
Ramp gradually (warm-up guide) or use pre-warmed inboxes (pre-warmed vs fresh).
📉Keep per-inbox volume low
Scale with inboxes, not volume (safe sending limits, inbox sizing).
✅Verify every list
Bounces damage reputation fast (verification tools, list cleaning).
📊Monitor weekly
Spam rate, bounces and blocklists (Postmaster setup, blacklist tools).
Infrastructure That Keeps Bounce Damage Contained
LiteMail | Spread risk across many inboxes
Fresh from $2.50/inbox
Official Google Workspace and Microsoft 365 inboxes for outreach
LiteMail provisions official Google Workspace and Microsoft 365 inboxes on secondary domains, configures SPF, DKIM and DMARC automatically and lists dedicated US and EU IPs. Plans spread volume across many inboxes at about 25 sends per inbox per day, so one bad segment doesn't load a single inbox.
Strengths | Keep in mind |
|
|
Explore pricing, the inbox calculator, infrastructure, bulk inboxes and setups for agencies, SaaS and recruiters. Comparing providers? See Google Workspace vs Microsoft 365.
Clean lists plus distributed inboxes keep bounces contained. Get Pre-Warmed Inboxes →
Frequently Asked Questions
What's the difference between a soft bounce and a hard bounce?
A soft bounce is a temporary failure that may succeed on retry; a hard bounce is permanent and won't succeed.
Which SMTP codes are soft bounces?
Codes starting with 4, such as 421, 450 and 452.
Which SMTP codes are hard bounces?
Codes starting with 5, such as 550 5.1.1 for unknown users.
Should I remove soft-bounced addresses?
Not after one soft bounce. Suppress them after repeated failures over several days.
Should I remove hard-bounced addresses?
Yes, immediately and permanently.
Can a soft bounce become a hard bounce?
Yes — repeated deferrals can turn into rejections if the underlying issue isn't fixed.
What causes many soft bounces at once?
Usually rate limiting or reputation deferrals from one provider; slow down and check your setup.
How do I reduce hard bounces in cold email?
Verify lists before sending, refresh old data and avoid guessed email formats.
Fewer Bounces, Better Inboxing
Official Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs.
Automated DNS · Pre-warmed options · OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Bounce Rate Fix · Bounce Rate Thresholds · Email Verification Tools · List Cleaning · Deliverability Recovery · Pre-Warmed Inboxes


