Article
How to Clean an Email List After an ESP Suspension: A Step-by-Step Process
By Unlimited Verifier Team ·

Summary
To clean an email list after an ESP suspension, pause sending, suppress hard bounces, complaints and repeat soft bounces, then verify the remaining addresses. Re-enter gradually with only Valid, recently engaged contacts, keeping bounces under 2% and documenting every removal with a count and reason.To clean a list after an ESP suspension, pause all sending, suppress every hard bounce, complaint and repeat soft bounce, verify the remaining addresses, and re-enter with only Valid, recently engaged contacts while keeping bounces under 2%. The reviewer needs proof at each step, so every removal needs a count and a reason.
For the broader picture of why suspensions happen, start with our high bounce rate account suspension guide. This page covers the cleanup itself: what to remove, how to verify what's left, how to document it, and how to re-enter safely.
Quick answer
- Stop sending first. Each new bounce during review weakens your appeal.
- Suppress what already failed: hard bounces (SMTP 5.1.x), complaints, unsubscribes, and soft bounces that repeated across three or more sends.
- Verify the whole remaining list, not just the bounced rows. Re-enter with Valid contacts only, hold Risky ones back, and suppress Invalid ones.
- Keep a reconciliation report. The starting count, each removal and each verification outcome should add back up to the starting number.
- Re-enter gradually. Start with your most engaged Valid contacts, hold a 2% bounce ceiling on every send, and aim for under 1% on the first sends.
What does cleaning a list after a suspension actually involve?
Cleaning after a suspension is three jobs: suppression (removing addresses you already know failed or objected), verification (testing addresses you haven't mailed recently), and segmentation (deciding who receives mail first). Many senders do the first job, then assume they're finished.
Each job answers a different question for the reviewer. Suppression shows you stopped mailing addresses that bounced. Verification shows you know the rest of the list is deliverable. Segmentation shows the mail is going to people who are likely to want it.
Don't confuse validity with consent. A verifier can tell you a mailbox exists. It can't tell you the person agreed to hear from you. That's a separate question, covered by email verification compliance and hygiene.
Bottom line: A credible cleanup does all three jobs, and the reviewer will check for each one.
Why is post-suspension cleaning different from routine hygiene?
Routine hygiene keeps a list tidy. Post-suspension cleaning has to prove the list is under control, and reviewers judge that proof by your next few sends as well as by what you removed.
The suspended campaign is a sample, not a census. If 1,150 of 48,000 contacts bounced, you know how that send performed, but not which of the other 46,850 addresses are dead. Only verifying them answers that.
Bounces also tend to cluster. A spike often traces back to one source: a purchased list, a scraped list, a years-old import, or a form that let bots in. Find that source first. It tells the reviewer where the process broke, and it tells you which segment needs the most scrutiny. If you're unsure how the spike happened, our guide on why bounce rates jump after an import walks through the usual causes.
The stakes are higher for SaaS and ecommerce senders. B2B addresses churn quickly as people change jobs, so a list that was healthy last year can be substantially stale now. That's why email verification for ecommerce and SaaS needs to be a recurring process, not a one-off.
Timing matters too. Whether one campaign can damage sender reputation depends on how fast you react, so the cleanup and the re-entry plan should be designed together.
Bottom line: The suspended send shows you the symptom. Verifying the whole list shows you the scope.
Which bounce codes should you suppress, and which should you investigate?
Many ESPs log an SMTP enhanced status code with each bounce. RFC 3463 defines these codes. A first digit of 5 means a permanent failure, and 4 means a temporary one. The second and third digits give the reason.
| Signal in your bounce log | Typical code (RFC 3463) | What it usually means | Recommended action |
|---|---|---|---|
| Unknown mailbox | 5.1.1 | The address doesn't exist | Suppress permanently |
| Unknown domain or host | 5.1.2 | The domain or server doesn't exist | Suppress permanently |
| Receiver policy or reputation rejection | 5.7.x (for example, 5.7.1) | The receiving server refused the message, often because of your sending reputation | Investigate. Suppress only if it failed more than once or verifies as Invalid |
| Mailbox full or temporary failure | 4.x.x (for example, 4.2.2) | A temporary problem | Retry. Suppress if it repeats across three or more sends |
| Spam complaint | Reported through feedback loops, not an SMTP code | The recipient marked you as spam | Suppress immediately |
| Unsubscribe | Not a bounce | The recipient opted out | Suppress and honour the request |
The 5.7.x group is the trap. These codes often describe your sending, not the recipient's address. If you suppress every 5.7 failure, you may delete real contacts. If you keep mailing them while your reputation is damaged, you'll keep bouncing. Hold them in a separate bucket until verification results come back.
Bottom line: Suppress permanent address failures and repeat offenders. Investigate policy rejections before you delete anyone.
How do you clean a list after an ESP suspension?
Follow these eight steps in order. Each one produces a number you'll use in the appeal.
Freeze and snapshot. Export every list, segment, suppression file and bounce log, with send IDs, SMTP codes and timestamps. Store the files read-only, with dates in the filenames. Why: reviewers compare what you say you removed against what existed at the time.
Build one master suppression file. Combine hard bounces, complaints, unsubscribes and repeat soft bounces, and add a reason column to each row. Why: a suppression with no reason is hard to defend. Platforms keep their own records too. Mailchimp, for example, tracks bounced addresses as "cleaned," and SendGrid keeps a bounce suppression list. Those records don't automatically travel with a CSV export, so copy them out. Platform-specific steps are in our guides to Mailchimp suspensions, SendGrid reviews and Brevo suspensions.
Normalise before matching. Trim whitespace, lowercase the addresses and remove exact duplicates across lists. Flag likely typos such as
gmial.comfor review instead of correcting them automatically. Why: a case or whitespace mismatch lets a dead address slip past your suppression file, and auto-correction can turn a real address into someone else's.Verify the full remaining list. Include contacts that weren't in the failed campaign. Why: the addresses you didn't mail are where the unknown bad addresses sit.
Classify the results. Sort addresses into Valid, Risky and Invalid. Why: each bucket gets a different sending rule, and the counts become the evidence in your appeal.
Segment by recent engagement. Send first to Valid contacts with recent clicks, replies or purchases, then older engaged contacts, and only then the rest. Opens are a weak signal because mail apps preload tracking pixels, so don't rely on them alone. Why: engagement is the strongest evidence of intent you can show. For the older segments, see our guide on sending to a list that is two years old.
Reconcile every count. Show the starting total, each suppression category, the verification results and the final sendable total. Why: a reconciliation that adds up is the most persuasive exhibit in an appeal.
Re-enter under a ceiling. Send only Valid contacts, starting with the most engaged, and set a bounce ceiling for every send. Why: the reviewer's real question is whether the next send repeats the problem.
Bottom line: Steps 3, 4 and 7 produce the evidence. Steps 5 to 8 stop the next send from undoing it.
Which cleaning method produces the evidence an ESP wants?
Only verification gives you a measurable picture of the whole list. The other methods have their uses, but each answers a narrower question.
| Method | What it catches | What it misses | Value as appeal evidence | Safe during a suspension? |
|---|---|---|---|---|
| Delete only the addresses that bounced | Known failures from one campaign | Every dead address you didn't mail | Low. The reviewer knows the rest is untested | Yes |
| Suppress by inactivity (for example, no engagement in 12 months) | Long-dormant contacts | Recently added bad data. Open-based inactivity is unreliable | Moderate. Good as policy, weak as proof | Yes |
| Re-engagement campaign | Unengaged but deliverable contacts | Sends to unverified addresses, creating new bounces | Poor | No. Don't send it mid-review |
| Bulk verification | Syntax, domain, MX, mailbox, catch-all, disposable and role-based addresses | Consent and engagement | High. Produces per-category counts | Yes, because it sends no mail |
| Verification plus engagement segmentation | Deliverability and likely intent | Consent still needs a separate check | Highest | Yes |
Deleting bounced addresses is the most common first move, and it's the weakest evidence. The rest of the list stays untested, and that's what a reviewer will ask about.
If you're comparing options, our roundup of the best email verification tools and our criteria for choosing a verifier cover what to look for, including how results are categorised and how the tool fits your workflow.
Bottom line: Verification plus engagement is the only combination that gives you both deliverability evidence and intent evidence.
How do you verify a list with Unlimited Verifier?
Unlimited Verifier is a bulk verifier. It checks each address's syntax, domain, MX records and SMTP mailbox, detects catch-all domains, flags disposable and role-based addresses, and sorts results into Valid, Risky and Invalid. Here's how to run the verification step.
Export a lean CSV from your ESP. Keep the email column and one unique contact ID, and drop everything else. Uploads are capped at 10MB, which works out to about 400 bytes per row on a 25,000-row file, so trim unused columns.
Choose the plan that fits the job. The Free plan ($0) covers 25 lists a month, each up to 150 emails, plus 750 deep verifications a month. It has no API access, and results are kept for 24 hours. Pro costs $29 a month, or $25 a month billed annually. It covers lists of up to 25,000 emails, 25,000 deep verifications a month, API access for 100,000 emails a month, and results kept for 30 days. Unlimited standard verification is included on every plan with no per-email fees. Compare email verification pricing by the cost per cleaned contact, as the worked example below does. You can sign up for a free account to test your file first.
Split files at 25,000 rows on Pro. Name each part clearly, for example
cleanup_part1.csv, and keep the ID column intact so you can join results back.Upload the file. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Confirm the detected column before you run the job.
Read the three buckets. Valid addresses are safe for re-entry. Invalid addresses should be removed permanently. Risky rows are where catch-all results and the disposable and role-based flags appear. A catch-all domain accepts any address, so its mailboxes can't be confirmed. For background, see our catch-all email verification page.
Export the results the same day. Download CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so waiting is the easiest way to lose your audit trail.
Rebuild your files by ID. Join the results back to your contact IDs. Valid goes into a re-entry segment. Invalid goes into your suppression file with the reason "verification invalid." Risky is held back.
Re-import, don't just re-send. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the workflow is export, verify, re-import. Teams with engineering support can instead use the email verification API and automation route: get an API key, then run single checks or bulk batches of up to 10,000 emails per request from their own scripts. To spot-check an important individual contact, use the free email checker.
Bottom line: Export lean, verify, export results the same day, and re-import only Valid contacts into a fresh segment.
What does a full cleanup look like with real numbers?
The scenario and percentages below are illustrative. The plan limits and arithmetic are real.
The failure. A B2B company sent one campaign to 48,000 contacts. It produced 1,150 bounces:
1,150 ÷ 48,000 = 2.4% bounce rate
Of those bounces, 890 were hard (5.1.x), 120 were soft bounces that repeated across three or more sends, and 140 were 5.7.x policy rejections.
Suppression. The company suppressed the hard bounces and repeat soft bounces, plus complaints and unsubscribes:
890 + 120 = 1,010 bounces suppressed 1,010 + 45 complaints + 310 unsubscribes = 1,365 suppressed 48,000 − 1,365 = 46,635 contacts to verify
The 140 policy rejections were not suppressed. They went into verification, where their results would decide their fate.
Plan limits. On the Free plan, the cleanup isn't feasible in one go:
25 lists × 150 emails = 3,750 emails a month 46,635 ÷ 3,750 = 12.4, so roughly 13 months
On Pro, the list fits in two files:
25,000 + 21,635 = 46,635
The company ran deep verification on the 9,000 contacts from its 2019 import, using 9,000 of its 25,000 monthly deep verifications and keeping 16,000 for re-checks. Standard verification covered the rest of the list.
Results (hypothetical):
| Result | Contacts | Share of 46,635 |
|---|---|---|
| Valid | 40,100 | 86.0% |
| Risky | 4,200 | 9.0% |
| Invalid | 2,335 | 5.0% |
Check: 40,100 + 4,200 + 2,335 = 46,635.
Reconciliation for the appeal:
| Stage | Contacts |
|---|---|
| Starting list | 48,000 |
| Hard bounces suppressed | −890 |
| Repeat soft bounces suppressed | −120 |
| Complaints suppressed | −45 |
| Unsubscribes suppressed | −310 |
| Sent to verification | 46,635 |
| Invalid, removed | −2,335 |
| Risky, held back | −4,200 |
| Valid, eligible for re-entry | 40,100 |
Cost. One Pro month at $29 works out to:
$29 ÷ 46,635 × 1,000 = about $0.62 per 1,000 contacts cleaned
That's a subscription spread across one cleanup, not a per-email rate. Agencies cleaning several lists should compare the API route. At 10,000 emails per request, 46,635 contacts need five batch requests (46,635 ÷ 10,000 = 4.66, rounded up).
Bottom line: The arithmetic has to add back to 48,000. Here, $29 and two Pro files turn "we cleaned the list" into a 48,000-row audit.
How should you re-enter after cleaning?
Re-entry is where the cleanup gets tested. The company in the example has 40,100 Valid contacts, but it doesn't send to all of them on day one. Its most engaged segment, with recent clicks or purchases, has 14,300 contacts. Sending in tiers gives each send a ceiling you can check:
Send 1: 4,000 contacts. Ceiling 0.5%, so at most 20 bounces. Send 2 (day 4): 6,000 contacts. Ceiling 1%, so at most 60 bounces. Send 3 (day 8): 4,300 contacts. Ceiling 1%, so at most 43 bounces. 4,000 + 6,000 + 4,300 = 14,300 engaged contacts.
The remaining 25,800 Valid contacts (40,100 − 14,300) follow in weekly batches, but only if the last three sends stayed under 1%. For a full ramp plan and volume guidance, see our guide to warming up an old list after cleaning.
Three rules apply to every send:
- Stop on a breach. If a send exceeds its ceiling, pause, check the bounced addresses, suppress any new hard bounces, and wait before the next send.
- Watch complaints. Google's email sender guidelines ask bulk senders to keep the user-reported spam rate below 0.3%, and you should aim well below that. Yahoo's sender requirements set similar expectations.
- Hold the Risky segment. Catch-all and role-based contacts go to the end of the ramp, if at all. Don't add new sources while you're re-entering.
Once the ramp is finished, keep the cleanup going with a regular routine. Our guide to list maintenance practices covers the schedule.
Bottom line: Each send has a ceiling you can measure, and you pause when one breaks.
What mistakes sink a post-suspension cleanup?
- Deleting only the bounced rows. The list you didn't mail is untested, and the reviewer will ask about it.
- Losing the suppression file. Re-importing an old export can bring back addresses you already removed. Keep one master suppression file and check it before every upload.
- Mismatched keys. A trailing space or a capital letter can stop a match. Normalise before you compare.
- Downloading results too late. Free results are kept for 24 hours and Pro results for 30 days. Export on the day you run the job.
- Treating Risky as Valid. Catch-all and disposable addresses carry more uncertainty, so they belong at the end of the ramp.
- Treating Valid as opted in. A valid mailbox doesn't mean the person consented. The FTC's CAN-SPAM compliance guide sets out the US baseline for commercial email.
- Sending a re-engagement campaign during review. It creates new bounces while the reviewer is watching.
- Auto-correcting typos. A "fix" can turn a real address into a different person's. Flag these for manual review.
- Re-importing without fixing sign-up. If forms still accept unverified addresses, the problem returns. Consider real-time email validation at signup, and read how to avoid ESP suspension when importing old lists before any new import.
- Assuming reinstatement is a clean slate. Reinstatement lifts the restriction, but it doesn't reset mailbox providers' view of your sending. Keep the bounce ceiling in place for weeks.
Bottom line: Process failures, such as a lost suppression file or a late export, undo cleanups more often than the verification step does.
How we compared (and limitations)
This guide is based on public documentation: the RFC 3463 enhanced status codes, Google and Yahoo sender requirements, and the FTC's CAN-SPAM guidance. We haven't run controlled tests against any ESP's review team, so the process above reflects documented standards and general practice rather than tested outcomes.
ESP thresholds vary and aren't always published. Amazon's SES documentation is one of the few public sources, and it describes review and pause levels of 5% and 10% bounce rate. Other platforms publish no fixed number and can act on a single campaign. Where sources disagree, we recommend one number: a 2% bounce ceiling, with a target under 1% for re-entry. It's a working guideline, not any platform's trigger. For a platform-by-platform view, see what bounce rate gets an ESP account suspended and our Amazon SES bounce-rate limits explainer.
Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's own stated number, not an independent benchmark. Its verification engine is open source on GitHub, so your technical team can review the checks it performs. The worked example uses hypothetical results, and your own Valid, Risky and Invalid split will depend on list age and source.
Bottom line: The method holds across providers. The numbers depend on your list, so measure them.
Reconciliation Report Example
| Step | Count | Reason |
|---|---|---|
| Starting list | 48,000 | Export before pause |
| Hard bounces suppressed | 1,150 | SMTP 5.1.x during campaign |
| Complaints suppressed | 210 | Spam complaint feedback loop |
| Repeat soft bounces suppressed | 640 | Soft bounce on 3+ sends |
| Verified Invalid suppressed | 2,900 | Verifier result: Invalid |
| Verified Risky held back | 1,800 | Catch-all or role accounts |
| Valid, ready to re-enter | 41,300 | Verifier result: Valid |
| Check | 48,000 | Sums to starting count |
Frequently asked questions
How long should I wait before resuming sends after a suspension?
There is no fixed waiting period set by ESPs. Resume only after your cleanup is complete and documented, and start with a small, highly engaged segment. Many senders take several days to a few weeks, depending on list size and how quickly verification finishes.
Should I remove soft bounces?
Not on the first bounce. Suppress soft bounces that repeat across three or more sends, since they often indicate a full or inactive mailbox. Single soft bounces can usually stay in the list pending verification.
What is a safe bounce rate after re-entering?
Hold a bounce ceiling of 2% on every send, and aim for under 1% on your first sends back. Monitor each campaign and pause if a send crosses the threshold.
Do I need to verify addresses I emailed recently?
Recent successful sends are a good sign but not proof. Verify the full remaining list so you can show the reviewer that the whole database has been checked, not just the rows that bounced.
What does Risky mean in email verification?
Risky addresses are ones a verifier cannot confirm either way, such as catch-all domains or role accounts. Hold them back from your re-entry sends and only mail them later if engagement data supports it.
Can I re-import suppressed contacts?
Do not re-import hard bounces, complaints or unsubscribes. Keep them on a suppression list so they cannot re-enter through a future import or sync from another system.
What should the reconciliation report include?
Include the starting contact count, each removal category with its count and reason, each verification outcome, and the final sendable count. The numbers should add back to the starting total with no gaps.
Does list cleaning alone guarantee reinstatement?
No. Reviewers look at the whole picture: root cause, process changes, documentation, and performance after re-entry. Cleaning is necessary but not sufficient on its own.
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.