Article
How Many Soft Bounces Before Removing a Subscriber? The 3-Strike Rule
By Unlimited Verifier Team ·

Summary
Remove a subscriber after three consecutive soft bounces, each on a separate send spanning at least 30 days, and verify the address before deleting it. Retries within one send and 4.7.x throttling codes should not count against the subscriber.Remove a subscriber after three consecutive soft bounces, each on a separate send and spread over at least 30 days, and verify the address before you delete it. Retries inside one send don't count, and 4.7.x throttling codes shouldn't count against the subscriber at all.
A soft bounce is a temporary failure, so one rarely means the address is dead. A run of them across separate sends usually does. For the full classification system, see our email bounce codes reference.
Quick answer
- Threshold: Three consecutive soft bounces, each on a separate send.
- Span: At least 30 days from the first failure to the last. For a monthly sender, three sends cover about 60 days.
- Don't count: Retries within one send, and 4.7.x policy or throttling codes.
- Before you delete: Verify each address. Suppress Invalid ones, send Valid ones to one final re-test, and hold Risky ones back.
- Budget: Keep total bounces under 2%. On a 60,000-contact list, 2% is 1,200 bounces, so 780 dead addresses alone would use 1.3% of the list.
What is a soft bounce, and how is it different from a hard bounce?
A soft bounce is a temporary failure, reported by an SMTP reply in the 4xx range. A hard bounce is a permanent failure in the 5xx range. RFC 5321 defines these reply classes, and the first digit tells the sending server whether to retry later or stop.
Most servers also return an enhanced status code such as 4.2.2, defined in RFC 3463. The first digit repeats the class. The second digit names the category: 0 other, 1 addressing, 2 mailbox status, 3 mail system, 4 network and routing, 5 delivery protocol, 6 message content, and 7 security or policy. That second digit is what makes correct counting possible. For example, 5.1.1 is an addressing failure, so it stays a hard bounce however often it recurs. For a side-by-side view, see hard bounce vs soft bounce codes.
Soft bounces can turn into hard ones. When a sending server gives up on a transient failure, or the recipient server later answers with a 5xx reply, your logs will record a hard bounce.
Bottom line: A soft bounce is a retryable 4xx reply. The enhanced code tells you whether the problem sits with the mailbox, the network, or your sending.
How many soft bounces should trigger removal?
Three consecutive failures on separate sends is the right default for most lists. No published standard sets this number. It's a convention that balances the cost of losing real subscribers against the cost of mailing dead ones.
| Rule | Removes live subscribers? | Leaves dead addresses in your sends? | Verdict |
|---|---|---|---|
| Remove after 1 soft bounce | Often. A full inbox during a holiday counts | Rarely | Too aggressive |
| Remove after 2 soft bounces | Sometimes | Some | Too sensitive for most lists |
| Remove after 3 consecutive failures spanning 30+ days | Rarely | Rarely. Dead addresses reach the threshold within about three sends | Recommended default |
| Remove after 5+ or never | Almost never | Yes, and each dead address keeps adding failures | Too slow |
| Verify first, then apply the 3-failure rule | Rarely, and only after a check | Rarely | Recommended with the rule above |
Bottom line: Use three consecutive failures spanning at least 30 days as the trigger, and verify before you delete.
Why three, and not one, two or five?
The useful way to think about it is cost per dead address. Every dead address you keep for another send adds one failed delivery to your sending record. With a three-failure rule, each dead address costs you about three failures before it leaves. With a five-failure rule, it costs about five. Across thousands of addresses, that gap is often the difference between a healthy bounce rate and a deliverability review.
Two failures can still be a temporary condition. A recipient server may have been down for a week, or a mailbox may have filled up during a trip. Three consecutive failures across separate sends, spanning weeks, is much harder to explain away. It looks like a pattern, not a bad stretch.
Bottom line: Three is the point where the cost of keeping a dead address outweighs the risk of removing a live one.
What counts as one soft bounce?
One soft bounce is one failed attempt per address per send. A single campaign can produce several SMTP attempts over hours, and counting each as a strike would remove a subscriber after one send.
Count consecutive failed sends. If an address failed three times during Campaign 4, that's one strike. If it failed on Campaigns 4, 5 and 6 with no delivery between them, it has three. A successful delivery resets the streak to zero. An address that failed on Campaign 4 and then delivered on Campaign 5 starts again from zero.
Treat the count as a streak, not a lifetime total. Old failures that were followed by a delivery shouldn't count toward removal.
Bottom line: One strike per send, and any delivery resets the streak.
Which soft bounce codes should count against a subscriber?
Only codes that describe the subscriber's mailbox should count toward removal. Codes that describe your sending or the recipient's network need separate treatment, because counting them punishes good addresses for problems you caused.
| Enhanced code | RFC 3463 category | What it usually means | Count toward removal? | Recommended action |
|---|---|---|---|---|
4.2.1 Mailbox disabled |
Mailbox status | The account has been closed or disabled | Yes | Count it. Verify before removing |
4.2.2 Mailbox full |
Mailbox status | Inbox over quota, often from an inactive user | Yes | Count it. Full mailboxes often clear, so verify first |
4.3.2 System not accepting network messages |
Mail system | Recipient server temporarily refusing mail | Only if it repeats for the same address | If it hits a whole domain at once, treat it as a server issue |
4.4.1 No answer from host |
Network and routing | Recipient server unreachable | Only if persistent | Check the domain's MX records before counting |
4.7.0 / 4.7.1 Security and policy |
Security and policy | Rate limiting, greylisting or reputation controls | No | Slow your sending and check reputation, not the list |
The 4.7.x group needs special care. Gmail, for example, uses 421 4.7.0 for temporary throttling. Our 421 4.7.0 try again later guide covers how to respond. These replies describe a provider limiting your traffic, not a subscriber who has gone. If one domain returns 4.7.x for most recipients in a send, check your sending domain against a blacklist first. Unlimited Verifier's free domain blacklist checker can do that initial check.
Missing mailboxes are a different case. A 550 5.1.1 reply is a hard bounce, and 550 5.1.1 user unknown explains how to handle it.
Bottom line: Count mailbox-level codes, and don't count policy codes (4.7.x) against the subscriber.
Should you delete a soft-bounced subscriber, or verify them first?
Verify first, then decide. A soft bounce records a past attempt. Verification tells you whether the address can receive mail now, which is the question that matters before you remove anyone.
Run candidates through a verifier that checks syntax, domain, MX records and the SMTP mailbox, and flags catch-all, disposable and role-based addresses. Then act on each result:
- Invalid: Suppress permanently. The mailbox doesn't exist.
- Valid: Place the address in a final re-test segment and send once. If it soft-bounces again, suppress it. A Valid result with a soft-bounce history often means a full mailbox that has since cleared.
- Risky: Hold it back from sends. Catch-all domains accept any address, so a Risky result can't confirm a mailbox. Catch-all email verification explains how those results should be handled.
For checks at the point of signup, real-time email validation stops many bad addresses from entering the list in the first place. For the bigger picture, see email verification compliance and hygiene.
Keep soft-bounce removal separate from unsubscribes. Removing a soft-bounced address is a hygiene decision. Honouring an opt-out is a legal duty. Under the FTC's CAN-SPAM compliance guide, opt-out requests must be honoured within 10 business days. Keep unsubscribes in a permanent suppression record that survives any list migration.
Bottom line: Verification separates a dead address from a temporarily full one, and unsubscribes are always a separate obligation.
How long should the soft-bounce window be?
Set the streak length by the number of sends, and check that the span covers at least 30 days. Three failures in a row from a weekly sender only span about two weeks, which is too short. A two-week holiday could then remove people who were simply away.
| Sending cadence | Failed sends needed in a row | Approximate span | Notes |
|---|---|---|---|
| Weekly | About 5 | 30 days | Three weekly failures can come from a two-week holiday |
| Monthly | 3 | About 60 days | Three monthly sends comfortably clear 30 days |
| Quarterly | 3 | About 6 months | Long span, so re-verify before removing |
These windows are our recommendation, not a published standard. Their purpose is to ensure three failures reflect a sustained pattern.
Bottom line: Let the send count set the streak and the calendar set the minimum span, so a weekly sender isn't penalised for a fortnight away.
How do you count soft bounces step by step?
Follow this framework each month. It produces a removal list you can explain to an ESP or a compliance reviewer.
- Export per-send events. You need the email address, send date, outcome (delivered or bounced) and enhanced code for each recipient. Summary totals aren't enough, because you can't rebuild streaks from them.
- Separate the codes. Remove 4.7.x replies from the counting set and log them as sender-side issues.
- Deduplicate. Keep one row per address per send, so retries inside one campaign collapse into one strike.
- Build the streaks. For each address, count consecutive failures in date order. Reset to zero on any delivery.
- Flag streaks that qualify. Mark addresses with at least three consecutive failures spanning at least 30 days.
- Verify the flagged addresses. Sort them into Valid, Risky and Invalid.
- Act and record. Suppress Invalid, send Valid to one re-test, hold Risky, and log the date and count for each action.
- Repeat monthly. Track the soft-bounce rate by send, because a rising trend is an early warning.
Bottom line: Most counting errors are data errors. Keep delivery events in the export, separate the codes, and reset streaks on delivery.
How do you count and verify soft bounces with Unlimited Verifier?
This process takes about an hour for a list under 25,000 contacts. You'll need your ESP's send-level export and a spreadsheet.
- Export the event log. Download per-send results as a CSV with the email, send date, outcome and enhanced code. Include delivered events as well as bounces. If your platform exports only bounces, pull the delivered events separately or through its API.
- Set up the sheet. Put email in column A, send date in column B and outcome in column C. Use real date values, and sort by column A, then column B.
- Remove 4.7.x rows. Delete rows whose code starts with
4.7.. They neither count as failures nor reset the streak, so deleting them is the correct treatment. - Build the streak counter. In cell D2, enter
=IF(C2="Delivered",0,IF(A2=A1,D1,0)+1)and fill it down. Change "Delivered" to match your export's label. In cell E2, enter=IF(D2=1,B2,E1)to record each streak's start date. In cell F2, enter=B2-E2for days since the streak began. - Filter for removal candidates. Keep rows where column D is 3 or more and column F is 30 or more. Copy the unique email addresses into a new CSV.
- Create an account. Sign up for free. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. The Pro plan is $29/month, or $25/month billed annually. It covers lists of up to 25,000 emails each, with 25,000 deep verifications a month and API access. For how costs scale with volume, see email verification pricing.
- Upload the file. Use the upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Run verification and read the buckets. Each address is sorted into Valid, Risky or Invalid.
- Export before you leave. Free-plan results are kept for 24 hours and Pro-plan results for 30 days. Download CSV, Excel or JSON before the window closes.
- Update your ESP. Add Invalid addresses to its suppression list. Create a "final re-test" segment from the Valid addresses. Keep Risky addresses out of sends. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so re-import through your ESP's standard process.
For a single contact, such as a key account that came back Risky, the free email checker gives a quick result. To automate the monthly cycle, the email verification API handles single checks and bulk requests of up to 10,000 emails. API access is included on Pro, with 100,000 emails a month. For how this fits a wider workflow, see email verification API and automation.
Bottom line: Export deliveries and bounces, build streaks, verify the candidates, and suppress Invalid addresses. The cycle takes about an hour, and your ESP's data stays the source of truth.
What does a soft-bounce cleanup look like with real numbers?
This example is illustrative. The counts are hypothetical, but the arithmetic and plan limits are real.
Starting point: A B2B newsletter with 60,000 active contacts, sent monthly. Hard bounces are handled separately.
January send: 1,200 soft bounces, a 2.0% soft rate. These addresses each start a streak at 1.
February send: 1,200 soft bounces.
- 840 are January failures that failed again, so their streaks reach 2.
- 360 are new failures, so their streaks are 1.
- The other 360 January failures delivered, so their streaks reset to 0.
March send: 1,100 soft bounces.
- 780 come from the 840 two-streak addresses, which reach 3.
- 320 come from the 360 one-streak addresses, which reach 2.
- 60 of the two-streak addresses and 40 of the one-streak addresses delivered, so their streaks reset.
That leaves 780 addresses at a three-send streak. Their failures run from January to March, a span of about 60 days, which clears the 30-day minimum. In percentage terms, 780 ÷ 60,000 = 1.3% of the list. Those 780 addresses also account for 780 of March's 1,100 soft bounces, or 71% of that send's failures. Most of the month's damage came from addresses that should have been removed earlier.
Verification of the 780: Assume the results are:
- Valid: 412 (about 53%)
- Risky: 205 (about 26%)
- Invalid: 163 (about 21%)
Check: 412 + 205 + 163 = 780.
Actions:
- Suppress the 163 Invalid addresses permanently.
- Hold back the 205 Risky addresses for a separate test.
- Send the 412 Valid addresses once in a final re-test. Suppress any that bounce again.
- The 368 removed addresses (163 + 205) equal 368 ÷ 60,000 = 0.6% of the list, which comes off the next send.
Plan check: On the Free plan, 780 addresses fit into six lists: five of 150 (750 addresses) plus one of 30. The Free plan's 750 deep verifications cover 750 of the 780, and the other 30 can run as standard verification, which is unlimited on every plan. Export all six result files within the 24-hour window. On Pro, the 780 addresses fit in a single list and use 780 of 25,000 deep verifications, or 3.1%. The Free plan cleanup costs $0. Pro costs $29 for the month.
Bottom line: A 1.3% group of dead addresses drove most of one month's soft bounces, and the cleanup needed no paid plan.
What do ESPs and mailbox providers say about soft bounces?
No authoritative source sets a soft-bounce removal count. The published guidance sets limits on overall bounce and complaint rates, and each ESP writes its own suppression logic. These sources shape a sound policy:
| Source | What it says | How to use it |
|---|---|---|
| RFC 5321 | Defines reply-code classes: 4xx is transient, 5xx is permanent | Treat 4xx replies as retryable, not as verdicts on the address |
| RFC 3463 | Defines enhanced status codes and their categories | Use the second digit to separate mailbox, network and policy failures |
| Amazon SES documentation | Describes a 5% bounce rate as the review threshold, and 10% as a level that can lead to pausing sending | Sets an overall ceiling, not a per-subscriber rule |
| Google's sender guidelines | Describes keeping spam rates below 0.10% and never reaching 0.30% | Complaints are a different metric from bounces, so track both |
These sources measure different things, but they don't conflict. An overall bounce ceiling of 2% leaves room below the 5% review point that SES describes. For the per-subscriber rule, our recommendation is three consecutive failures on separate sends, spanning at least 30 days. Check your own ESP's suppression documentation, because some platforms apply their own cut-offs.
Bottom line: No source sets a soft-bounce count, so choose one rule, document it, and apply it consistently.
What mistakes make soft-bounce removal go wrong?
Most soft-bounce errors come from counting the wrong events or deleting without checking.
- Counting retries as strikes. Three attempts in one hour are one strike. One campaign should never remove a subscriber.
- Counting 4.7.x throttling against subscribers. You'll remove good addresses when the real problem is your sending speed or reputation.
- Leaving soft-bounced addresses in every send. Each send to a dead address adds another failure, and the bounce rate climbs each month.
- Building streaks from bounces alone. Without delivery events, you can't reset streaks, so old failures will wrongly count toward removal.
- Deleting without verifying. You'll lose Valid subscribers whose mailboxes were only full, and you'll miss catch-all or role-based addresses that need a different decision.
- Mixing soft bounces with unsubscribes. Opt-outs must be honoured within 10 business days under CAN-SPAM, so keep them in a separate, permanent suppression record.
- Losing suppression history during a migration. Export your suppression lists and unsubscribes from the old ESP first. A new platform won't know what the old one knew.
- Letting free results expire. Free-plan results last 24 hours, so export before you close the session.
- Treating verification as consent. A Valid address is deliverable, not opted in. Consent is a separate question, covered by how to choose an email verifier only in terms of what a verifier can and can't tell you.
Bottom line: The most expensive mistake is counting the wrong events. Fix the streak logic first, then the deletion step.
How we compared (and limitations)
This article is based on public documentation: RFC 5321, RFC 3463, Amazon SES's documentation, Google's sender guidelines and the FTC's CAN-SPAM guide. We haven't run controlled tests against any ESP's suppression logic or review process, so confirm per-platform behaviour in your own account. The three-failure, 30-day rule is our recommendation rather than a published standard, and it may need adjusting for very low-frequency senders or unusual audiences.
For Unlimited Verifier, plan details come from the company's published plan facts. The company states 99.5% accuracy for deep verification, which is its own figure, not an independent benchmark. The worked example uses hypothetical counts to show the arithmetic.
If you're comparing options, our guides to the best email verification tools and how to choose an email verifier cover the criteria that matter for this work, including how results are categorised and how easily you can export them. For the wider maintenance routine, see email list maintenance best practices.
Bottom line: Use the three-failure rule as a starting policy, confirm your ESP's behaviour, and adjust for your cadence.
Bounce budget on a 60,000-contact list
| Item | Count | Share of list |
|---|---|---|
| Total bounce budget (2%) | 1,200 | 2.0% |
| Dead addresses removed | 780 | 1.3% |
| Remaining budget | 420 | 0.7% |
780 dead addresses use 1.3% of the list, leaving 0.7% for all other bounces.
Frequently asked questions
Is one soft bounce enough to remove a subscriber?
No. One soft bounce often comes from a temporary problem such as a full inbox or a server outage. Removing after a single failure would drop many live subscribers. Wait for a pattern of repeated failures across separate sends before acting.
Do retries within one send count as soft bounces?
No. Retries inside a single send attempt count as one failure event. Only failures on separate sends count toward the three-bounce threshold, so one bad send cannot remove a subscriber on its own.
Should 4.7.x codes count toward removal?
No. The 4.7.x enhanced codes indicate policy or throttling decisions, often from the receiving server limiting your sending rate. They reflect your sending behavior, not the subscriber's address, so they should not count against the subscriber.
What is a soft bounce?
A soft bounce is a temporary delivery failure signaled by a 4xx SMTP reply. It means the message could not be delivered now but may succeed later, such as when a mailbox is full or a server is temporarily unavailable.
What is the difference between a soft bounce and a hard bounce?
A soft bounce is a temporary 4xx failure that may succeed on retry. A hard bounce is a permanent 5xx failure, such as an unknown mailbox, and should be suppressed immediately. RFC 5321 defines these reply classes.
Why should I verify an address before deleting it?
Verification confirms whether an address is invalid, valid, or risky. Invalid addresses can be suppressed immediately, while valid ones may just need a final retest. This prevents removing real subscribers whose mailboxes were only temporarily unavailable.
How long should I wait before removing a soft-bouncing subscriber?
Wait until the failures span at least 30 days, from the first to the last. For a monthly sender, three sends cover about 60 days. Spreading failures out distinguishes persistent problems from short outages.
What bounce rate is acceptable for an email list?
Keep total bounces under 2 percent of sends as a working budget. Most email service providers recommend keeping bounce rates low, and high rates can hurt sender reputation. Regular list cleaning helps keep the rate within budget.
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.