Article
Common Soft Bounce Reasons List: Causes, Codes and Fixes
By Unlimited Verifier Team ·

Summary
A soft bounce is a temporary delivery failure carrying a 4xx SMTP code. The most common causes are a full mailbox (4.2.2), a disabled mailbox (4.2.1), sender throttling (421 4.7.0), greylisting (450 4.7.1) and connection or DNS timeouts (4.4.x). Most describe the sending path or the receiving server's state, not the address itself.A soft bounce is a temporary delivery failure with a 4xx SMTP code, and the most common causes are a full mailbox (4.2.2), a temporarily disabled mailbox (4.2.1), sender throttling (421 4.7.0), greylisting (450 4.7.1) and connection or DNS timeouts (4.4.x). Most of these describe your sending path or the receiving server's state at that moment, not the address itself, so they need different handling from hard bounces.
Quick answer
- Soft bounces carry 4xx codes; hard bounces carry 5xx. Trust the code over the label your platform displays, because platforms file the same code differently.
- Five families explain most soft bounces: recipient mailbox, receiving-server capacity, sender rate and reputation, greylisting, and network or DNS.
- Count only recipient-side soft bounces against an address. Throttling and timeouts are sending problems you fix in configuration, not list problems you fix by deleting people.
- Our suggested rule: suppress after three recipient-side soft bounces on three separate sends, then confirm with verification. For mailbox-full codes, require recurrence across 60 days. These are our recommendations, not an industry standard.
- If soft bounces spike across unrelated domains within one hour, check your sending setup before you check your list.
What is a soft bounce?
A soft bounce is a delivery attempt the receiving server rejected with a transient (4xx) reply, so the message stays eligible for a later retry. RFC 3463 defines enhanced status codes by their first digit: 4.x.x is a persistent transient failure and 5.x.x is a permanent failure. The base SMTP reply codes follow the same split, with 4xx temporary and 5xx permanent, as set out in RFC 5321. For contrast, see examples of hard bounce messages, or compare the two directly in hard bounce vs soft bounce codes.
The first digit is reliable. Labels are not. Amazon SES's documentation separates bounces into Transient and Permanent types, and its transient subtypes include General, MailboxFull, MessageTooLarge, ContentRejected and AttachmentRejected. Platforms draw the line in different places. A 552 5.2.2 "mailbox full" reply carries a 5xx prefix, so the standard treats it as permanent, yet some platforms file it under soft bounces. The platform's label tells you how it will retry. The code tells you what the server actually said.
Bottom line: Read the SMTP code, not the label. A 4xx prefix means the failure is temporary, but your platform's retry rules decide what happens next.
Which soft bounce reasons are most common?
Soft bounces fall into five families. The table lists the reasons that appear most often in public SMTP and platform documentation, with the action for each. Sub-codes vary by receiving provider, so treat them as typical examples rather than a complete registry. For the full set, see SMTP error codes list with meanings.
| Family | Reason | Typical code(s) | Who controls the fix | Action |
|---|---|---|---|---|
| Recipient mailbox | Mailbox full | 4.2.2 (552 5.2.2 on some platforms) | Recipient | Retry; suppress only if it recurs over weeks |
| Recipient mailbox | Mailbox disabled or not accepting mail | 4.2.1 | Recipient | Retry; watch for recurrence |
| Receiving-server capacity | Mail system full or not accepting connections | 4.3.1, 4.3.2 | Receiving provider | Retry; no list action |
| Sender rate and reputation | Rate limit or throttling | 421 4.7.0 (often used for rate or reputation limits) | You | Slow the send rate for that provider |
| Sender rate and reputation | Too many recipients in one session | 4.5.3 | You | Reduce recipients per connection |
| Greylisting | First contact from an unknown sender is deferred | 450 4.7.1, 451 4.7.1 | Receiver's anti-spam policy | Confirm your server retries after the delay |
| Network and DNS | Connection timeout or dropped session | 4.4.1, 4.4.2 | Network or your mail server | Check connection settings and retry queue |
| Network and DNS | Lookup for the domain's mail servers timed out | Often 4.4.3 | DNS infrastructure | Retry; investigate if one domain repeats |
Only the two recipient-mailbox rows describe the address. Greylisting is the family people misread most often. The deferral is deliberate: legitimate senders that retry after the delay get through, while many spam senders never retry. If your own server never retried a greylisted message, that is a configuration fault, not a dead address. A domain that stops resolving can also eventually return a permanent 550 5.1.2 bad destination host error, which moves it out of the soft category.
Bottom line: Only the mailbox rows describe the recipient. The rest describe how you send or how the network and receiving servers behave.
How do you tell a list problem from a sending problem?
Four signals usually separate the two causes, and you can read all of them in the bounce log without touching your list. A list problem repeats on the same addresses. A sending problem arrives in bursts and clusters on one provider.
| Signal | Points to a list problem | Points to a sending problem |
|---|---|---|
| Timing | Spread across the send window | Clustered within minutes of a large send |
| Domain | Scattered across unrelated domains | Concentrated on one provider or organisation |
| Recurrence | Same addresses fail on repeated sends | Different addresses each time, no pattern |
| Code family | Mailbox codes (4.2.x) | Rate, greylisting or timeout codes (421, 4.4.x, 4.7.x) |
Read them together. A mailbox-full address that bounces on every send for two months is a list problem. A burst of 421 responses from one large provider in the 20 minutes after a send is a sending problem. Timeouts across every domain at once usually point to your own server or network, and cleaning the list will not change that.
Watch the newest segment too. Soft bounces concentrated in contacts added in the last 30 days often indicate list quality, because those addresses have never been tested against your sending history. Deleting throttled addresses, by contrast, removes people who were never unreachable, while the real cause keeps generating new failures.
Bottom line: Recurrence on the same address points to the list. Bursts and single-provider clusters point to how you send.
When should a soft bounce become a suppression?
Suppress on repeated recipient-side failures, and confirm with verification first. Suppressing too early removes reachable contacts. Suppressing never leaves dead mailboxes in your sends. The table compares the common approaches.
| Approach | How it works | Strength | Weakness |
|---|---|---|---|
| Platform default | Your ESP retries, then stops or marks the address | No setup needed | Rules vary by platform and are not always documented in detail |
| Three strikes (recipient-side only) | Suppress after 3 recipient-side soft bounces on 3 separate sends | Simple to audit | Counts sending problems unless you filter by code first |
| Age window | Suppress when recipient-side soft bounces continue for 30 days or more | Catches abandoned mailboxes | Slower; some addresses stay in limbo |
| Verify, then decide | Verify flagged addresses and suppress the Invalid ones | Uses independent evidence | Verification can't predict whether a full mailbox will have room later |
We recommend three strikes, counted only on recipient-side codes, followed by verification. For mailbox-full addresses, require recurrence across at least 60 days, because a full mailbox is often a temporary state. This window is our judgement, not a documented standard. An address that verifies as nonexistent and keeps returning 550 5.1.1 user unknown is a different case, and it can be suppressed right away.
Bottom line: Suppress on repeated recipient-side failures, then verify. Don't suppress on throttling or timeout codes.
How long does a sending server keep retrying a soft bounce?
Your sending server keeps retrying until its queue lifetime expires, and then it returns a bounce. Postfix's documentation sets a default maximal queue lifetime of five days, and other mail servers set their own limits. A soft bounce that eventually arrives as a returned notice therefore means the retry window closed, not that the address was confirmed dead.
The practical lesson is that retry windows are finite. If your server treats one 4xx as final, every deferred message is lost on the first attempt. Check your mail server's retry and queue settings before you touch your list. Also note that mailboxes stuck on 4.2.1 for weeks often end in a permanent 5.1.1 once the account closes, so recurrence over time is a strong signal.
Bottom line: Retry windows are finite, so a fault in your retry settings loses mail even when the address is fine.
How do you triage soft bounces step by step?
Follow these five steps in order. Sender fixes come first, because they recover mail already in the queue.
- Export the bounce log for the last 60 to 90 days. Include the SMTP code, diagnostic text, send date and address. If your platform shows only summaries, look for a raw export or a per-message activity report. If bounce notices land in your inbox as mailer-daemon messages, why do I keep getting mailer-daemon bounce messages explains where they come from.
- Group by family. Sort every event into the five families. Recipient-mailbox codes go on the list track, and everything else goes on the sending track. Don't act yet.
- Fix the sending track first. Lower send rates for throttled providers, confirm your server retries 4xx responses instead of treating them as final, and check that DNS resolves reliably.
- Count recurrence for recipient-side codes. Flag any address with three or more recipient-side soft bounces on separate sends. For mailbox-full addresses, also confirm the failures span 60 days.
- Verify the flagged addresses and act on the result. Suppress Invalid addresses, keep Valid ones with a watch flag, and hold Risky ones until they engage again.
Bottom line: Sender fixes come first because they recover mail. List actions come last because they remove contacts.
How do you clean a soft-bounce log in Unlimited Verifier?
This is step 5 in practice. If you'll repeat it every month, check email verification pricing before you commit. You can sign up for the Free plan, which covers 25 lists a month of up to 150 emails each. Free results are kept for 24 hours, so export them the same day.
- Build the flagged list. Filter your export to addresses with three or more recipient-side soft bounces, keep only the email column, and save the file as CSV or Excel.
- Upload and verify a list. Files up to 10MB are accepted, and the email column is detected automatically.
- Check the file size against your plan. Free lists hold 150 emails, so a 1,230-row file needs 9 lists. Pro lists hold up to 25,000 emails each, so the same file fits in one list.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains, disposable addresses and role-based addresses are flagged.
- Read the three buckets. Valid addresses stay in your main list with a watch flag. Invalid addresses go on your suppression list. Risky addresses, including catch-all domains where the mailbox can't be confirmed, are held back. The catch-all email verification page explains how those results are handled.
- Export the results as CSV, Excel or JSON, and save the summary counts.
- Apply the suppressions. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so re-import the Invalid list into your platform's suppression list. If you triage often, consider email verification API and automation. The email verification API handles single-email checks and bulk batches of up to 10,000 emails per request. API access is included on Pro, not Free.
To spot-check one address before you suppress it, use the free email checker.
Bottom line: Export, verify, suppress Invalid, hold Risky, and keep the counts for your records.
What does a soft-bounce cleanup look like with real numbers?
This example is illustrative, and the verification results are hypothetical. The arithmetic and plan limits are real. Consider a B2B software company with 80,000 contacts, the kind of list covered by email verification for ecommerce and SaaS workflows.
The situation: The company mailed all 80,000 contacts six times in 60 days. Its log recorded 4,860 soft-bounce events across 2,410 unique addresses.
Step 1: Compute the overall soft-bounce rate.
4,860 ÷ (6 sends × 80,000 contacts = 480,000 deliveries) = 1.0%
That is a warning level, not a crisis. It also hides the cause until you split it by family.
Step 2: Split by family.
| Family | Events | Track |
|---|---|---|
| Mailbox full (4.2.2) | 1,940 | List: counts toward strikes |
| Mailbox disabled (4.2.1) | 1,210 | List: counts toward strikes |
| Throttling (421 4.7.0) | 1,020 | Sending: fix send pacing |
| Timeouts (4.4.x) | 690 | Sending: check mail server and network |
| Total | 4,860 |
Only 3,150 events (1,940 + 1,210) describe recipients. The other 1,710 (1,020 + 690) describe the company's own sending. Deleting addresses for those 1,710 events would have removed contacts who were never at fault.
Step 3: Apply the three-strike rule to recipient-side events. Of the 1,840 unique addresses with at least one recipient-side soft bounce, 610 reached three or more on separate sends, and their mailbox-full failures spanned 60 days.
610 ÷ 80,000 = 0.76% of the list suppressed on strikes alone
Step 4: Verify the remaining 1,230 addresses (1,840 − 610). Hypothetical results:
- Valid: 760
- Risky: 290
- Invalid: 180
Step 5: Total suppression. The 610 struck addresses plus the 180 Invalid addresses come to 790, or 790 ÷ 80,000 = 0.99% of the list.
Cost: On the Free plan, 1,230 addresses need 9 lists (1,230 ÷ 150 = 8.2, rounded up), which is inside the 25-list monthly allowance. Standard verification is unlimited on every plan. If you run deep verification on all 1,230 addresses, though, Free's 750 deep verifications a month won't cover them, so Pro is the better fit. On Pro at $29 per month ($25 billed annually), the same file fits in one list, well under the 25,000-email limit. Use Free for a one-off run and Pro for a monthly routine.
Bottom line: A 1.0% soft-bounce rate looked like one problem and was really two. Only the recipient-side share justified list action.
What soft bounce rate is too high?
Sources disagree, so pick a working ceiling and track it per send. Amazon SES's documentation says accounts go under review at a 5% bounce rate, measured on total bounces. Other platforms often act well below that, especially on a single campaign to an unproven list. Google's sender guidelines centre on spam complaint rates and authentication rather than soft bounces. In the public documentation we reviewed, limits apply to total bounces and complaints, not to soft bounces alone.
We recommend these thresholds:
- Total bounces (hard and soft combined): keep below 2%. This leaves room before most platform triggers.
- Soft bounces on a single send: investigate above 1%. Check the family breakdown before the next send.
- Recipient-side soft bounces: track per address over 60 days, not per send.
The 1% investigation trigger is our recommendation, not a documented rule.
Bottom line: Set a 2% total ceiling, investigate soft bounces above 1% per send, and track recurrence per address.
What are the common mistakes with soft bounces?
- Treating every soft bounce as a list problem. Throttling and timeout codes describe your sending. Deleting those addresses removes good contacts and leaves the real cause running.
- Retrying without a limit. Endless retries waste send capacity and keep sending to dead mailboxes. Set a retry ceiling and stop.
- Treating a 4xx as final in your own settings. If your server gives up after one deferral, the mail is lost. The fix is in your configuration, not your list.
- Assuming verification predicts mailbox-full bounces. A full mailbox can verify as valid and still fail when mail arrives. Verification tells you whether an address is real, not whether it has room.
- Treating verification as consent. Verification supports email verification compliance and hygiene, but it cannot prove someone opted in.
- Sending re-engagement mail to soft-bounced addresses during a throttling event. You add fresh failures to a problem you haven't fixed yet.
- Losing bounce history during a migration. Export suppression and bounce logs before you move platforms, or the recurrence count resets to zero.
- Reading the label instead of the code. The same 5.2.2 response may be soft in one tool and hard in another.
Bottom line: Most soft-bounce mistakes come from acting on the label, the burst or the first failure, rather than on the code and the recurrence.
How we compared (and limitations)
This article is based on public documentation: RFC 3463 and RFC 5321 for status-code definitions, Amazon SES's published bounce categories, Postfix's documentation on queue lifetime, and Google's sender guidelines. We have not run controlled tests against any ESP's retry logic or review team. Sub-codes, retry windows and platform labels change over time and differ between receiving providers, so confirm current behaviour in your platform's documentation.
The three-strike rule, the 60-day mailbox-full window and the 1% per-send trigger are our recommendations. The worked example uses hypothetical verification results to show the arithmetic. Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's own stated number, not an independent benchmark.
For the full code reference, start with our guide to email bounce codes. If you're still sorting codes, the 10 SMTP error codes every email marketer should know list covers the most common ones. For specific soft codes, see 421 4.7.0 try again later and SMTP 450 requested mail action not taken. Once you've sorted the codes, keep the list clean with email list maintenance best practices, and validate addresses at entry with real-time email validation. When you compare tools, our buyer's checklist for choosing a verifier covers how results are categorised, how catch-all domains are handled and how pricing scales. For an overview of the options, see best email verification tools.
Bottom line: Soft bounces are mostly a sending and timing problem, with a recipient-side minority. Fix the sending first, suppress only on repeated recipient-side failures, and confirm with verification before you delete anyone.
Soft bounce reasons and actions
| Reason | Code | Action |
|---|---|---|
| Mailbox full | 4.2.2 | Retry; suppress only if recurring over weeks |
| Mailbox disabled | 4.2.1 | Retry; watch for recurrence |
| Sender throttling | 421 4.7.0 | Slow send rate; fix config |
| Greylisting | 450 4.7.1 | Allow retry; check reputation if persistent |
| DNS or connection timeout | 4.4.x | Check DNS and network; not a list issue |
Frequently asked questions
What is the most common soft bounce reason?
Mailbox full (4.2.2) and temporarily unavailable mailboxes (4.2.1) are among the most frequently reported soft bounce reasons in platform documentation. Sender-side throttling and DNS timeouts are also common, especially during high-volume sends. Exact frequency varies by list and provider, so check your own bounce logs.
Can a soft bounce become a hard bounce?
Yes, in many platforms. If a soft bounce recurs beyond your retry window or the server later returns a permanent 5xx reply, the address may be reclassified as a hard bounce. Platform retry rules decide the exact timing.
How many soft bounces before I remove an email address?
There is no industry standard. One suggested rule is suppressing after three recipient-side soft bounces on three separate sends, then confirming with verification. Mailbox-full codes can warrant a longer window, such as recurrence across 60 days.
What does 421 4.7.0 mean?
421 4.7.0 is a temporary rejection often used for sender throttling or rate limiting. The receiving server is asking you to slow down. It reflects your sending behavior, so reduce send rate or check reputation rather than removing recipients.
What does 450 4.7.1 mean?
450 4.7.1 commonly indicates greylisting or a temporary policy block. The receiver expects a retry later, and legitimate servers usually succeed on the next attempt. Repeated 4.7.1 results may point to reputation or authentication issues.
Are soft bounces a sign my list is bad?
Not usually. Most soft bounces describe the recipient's mailbox state or your sending path at that moment. A spike across unrelated domains within one hour more often signals a sending configuration problem than a list problem.
Should I delete contacts with soft bounces?
Not after a single soft bounce. Count only recipient-side soft bounces, suppress after a repeated pattern across separate sends, and verify the address before permanent removal. Deleting people for throttling or DNS errors wrongly shrinks your list.
What is the difference between 4.4.x and 4.2.x codes?
4.2.x codes relate to the recipient mailbox or its storage, such as full or disabled. 4.4.x codes relate to network or routing issues, such as connection timeouts or DNS failures. The fix for 4.4.x is usually technical, not list-based.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.