Article

How to Get an ESP Account Reinstated After Bounces: A Step-by-Step Appeal Guide

By Unlimited Verifier Team ·

Flowchart showing four steps to reinstate an ESP account after bounces: stop sending, attribute bounces, verify the list, and ramp slowly.

Summary

To get an ESP account reinstated after bounces, stop all sending, prove with exact counts that bad addresses are removed, verify the remaining list, and submit a written plan that keeps future bounces under 2%. Reviewers want a diagnosis backed by numbers, not reassurance.

To get an ESP account reinstated after bounces, stop all sending, prove with exact counts that the bad addresses are removed, verify what remains, and send a written remediation plan that keeps future bounces under 2%.

Quick answer

Rejected appeals often fail for the same reason: the sender says the list is "clean" but cannot show it. Reviewers read many of those messages. What moves a case forward is a breakdown: where the bounces came from, which error codes they produced, how many addresses you removed, what verification says about the rest, and what the next sends will look like. For the wider picture of why platforms suspend senders, read our pillar guide on high bounce rate account suspension.

What are reviewers actually checking?

Reviewers are asking whether your list could damage shared infrastructure again. ESPs send for many customers through shared IP addresses and sending domains, so one customer's poor data puts its neighbours at risk.

That question breaks into three parts: is the failure a list-hygiene problem or a reputation problem, which part of the list produced it, and what changes in the next send. An appeal that answers only the third part reads as a promise. Reviewers have heard many promises, so the diagnosis comes first and needs numbers behind it.

The evidence they expect also depends on how serious the restriction is:

Restriction type What usually triggers it What the reviewer expects Typical outcome
Automated warning One campaign crosses an internal bounce threshold Acknowledgement and a cleaning commitment Often lifted after a prompt, specific reply
Manual compliance review Repeated spikes, or one severe spike from an imported list Root cause, suppression counts, verification results Usually reinstated if the evidence holds up
Suspension with conditions High bounces plus complaints or spam-trap hits All of the above, plus proof of opt-in for the list Reinstated with a sending cap or segment limits
Termination Bought or scraped lists, repeat offences Often not reversible on the same account Move to a new provider only after the list is fixed

Bottom line: Reviewers want a diagnosis, not reassurance. Identify your tier first, then answer every question with figures.

Which bounce codes count against your list?

Hard list failures are the codes that point to a bad address or domain, mainly the 5.1.x group. Every bounce carries an SMTP enhanced status code in the form class.subject.detail, defined in RFC 3463. The first digit tells you whether the failure is temporary (4) or permanent (5), and the remaining digits describe the cause.

Code What it means Points to your list? What the reviewer expects
5.1.1 Mailbox does not exist Yes Suppression plus verification of the whole list
5.1.2 Bad destination system address (domain missing or no mail server) Usually yes, often a dead or mistyped domain Removal of those domains and a typo check
5.2.2 Mailbox full (a permanent code that many senders retry as soft) No Retry logic, and removal only if it repeats
5.7.1 Delivery refused on policy or authentication grounds Usually no, more often reputation or authentication Authentication audit and complaint trend
4.x.x Temporary failure No Retry log, not a hard bounce

Many providers return generic 5.7.1 messages without explaining the reason. If a large share of your spike is 5.7.x, cleaning the list will not satisfy a reviewer on its own. Say so in the appeal, and show your SPF, DKIM and DMARC setup and your complaint trend next to the list work.

Bottom line: Count 5.1.x list failures separately from 5.7.x policy blocks. Mixing them weakens your cleanup story.

What bounce rate gets an account suspended?

No universal number exists, so plan for the strictest figure you can find. Amazon SES's documentation describes a 5% bounce rate as the level that triggers review and 10% as the level at which sending can be paused. Many other platforms act earlier, especially on a single campaign to an untested list, and most do not publish exact thresholds.

Sources disagree, so pick one number and plan around it. We recommend a 2% overall ceiling and a sub-1% target for each send after reinstatement. Re-entry sends get the most scrutiny, and a 2% average can hide one send that spiked to 6%. For platform-by-platform detail, see what bounce rate gets your ESP account suspended.

Track bounces and complaints separately. Google's sender guidance asks bulk senders to keep the user-reported spam rate below 0.10% and to avoid reaching 0.30%. A complaint problem can trigger action even when bounces look fine.

Bottom line: Plan for 2% overall and under 1% per re-entry send, whatever the platform's published limit.

How do you get an ESP account reinstated, step by step?

Follow these seven steps in order. Each produces evidence you will cite in the appeal.

  1. Freeze, then snapshot the evidence. Pause marketing sends and any automation that draws from the list. Before you delete anything, export the bounce, complaint and unsubscribe reports for the campaign window. Some dashboards show only recent activity, and deleting contacts can erase the records a reviewer will ask for.

  2. Attribute every bounce to its source. Tag each contact by how it entered your system: signup form, a named import file and its date, a partner or event list, or a platform migration. Calculate a bounce rate per source. A single bad source inside a healthy list is the most common pattern, and it makes the strongest story because it shows the problem is contained.

  3. Classify failures by code. Sort bounces into 5.1.x list failures, 5.2.2 mailbox-full bounces, 5.7.x policy blocks and 4.x.x temporary errors. Each needs a different fix, and reviewers check whether your remedy matches the code.

  4. Suppress and archive. Suppress hard bounces, complaints and unsubscribes, and keep a copy outside the platform. ESP suppression lists often do not travel when you export or migrate, so your own file is the proof you can show.

  5. Verify everything that remains. Verify the whole list, not just the segment that bounced. A bounce only tests the addresses you mailed. The rest are untested, which is why reviewers discount "we removed the ones that bounced."

  6. Segment for re-entry. Rank Valid contacts by recent clicks, replies or purchases. Keep Risky contacts out of the first sends, and hold back any source with a high bounce rate until you have tested it. The first sends after reinstatement are the ones being watched.

  7. Appeal, ramp and report. Submit through the channel named in your notice, then increase volume while sharing per-send bounce results. Publishing results lets the reviewer check your plan in near real time.

Bottom line: Steps 2 to 5 produce the numbers. Steps 6 and 7 turn those numbers into a plan a reviewer can monitor.

Which cleaning approach produces evidence a reviewer accepts?

Not all cleaning produces the same proof. Suppressing bounced addresses is necessary, but it says nothing about the untested rest of the list. Bulk verification, backed by your own suppression file, is the approach a reviewer can audit.

Approach What it produces Where it falls short Role in your appeal
Suppress only addresses that bounced A suppression list you own, with exact counts Says nothing about contacts you did not mail in this campaign Required baseline, never sufficient alone
ESP's built-in suppression A platform-side record of past bounces Often stays inside the platform and does not check untested addresses Useful cross-check against your own count
Inactivity sunset (no engagement in N months) A segment of dormant contacts Opens are unreliable since Apple's Mail Privacy Protection launched in 2021, so a real person can look inactive Policy evidence for re-entry, not proof of deliverability
Bulk verification with best email verification tools, such as Unlimited Verifier Each address sorted into Valid, Risky or Invalid, with checks for syntax, domain, MX, SMTP mailbox, catch-all, disposable and role addresses Shows whether an address can receive mail, not whether the person consented Core proof: per-category counts you can quote
API verification at capture Blocks new bad rows before they are stored Does not touch the existing list Evidence for your "what will change" section

Keep verification counts by category and by source. A reviewer responds to "we verified every contact and found X Valid, Y Risky and Z Invalid, broken down by source" far more than to "we verified the list."

For a related playbook on the shorter cleanup that follows a spike, see 5 steps to take after a bounce rate spike.

Bottom line: Bulk verification gives the most direct per-address audit trail for an existing list, and your suppression file proves what you already removed.

How do you clean and verify a list before appealing?

This tutorial covers step 5 of the framework using Unlimited Verifier. Check the limits first, because they determine how you split the file.

Review current email verification pricing before you commit, since plans change.

  1. Export the list as CSV. Keep the email column and only the fields you need, such as source and last engagement date. A 25,000-row file with a handful of short columns is usually well under the 10MB upload limit. Check the file size before you upload, because a file with dozens of CRM columns may exceed it.
  2. Add a source column. Use the tags from step 2 of the framework so the source travels with every row.
  3. Split by row count. Pro accepts lists of up to 25,000 emails each, so a 40,000-row list becomes two files.
  4. Sign up and upload. Create your account, then upload your file. CSV and Excel files are accepted, and the email column is detected automatically. Confirm the detected column before you run the check.
  5. Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains, disposable addresses and role accounts are flagged. Spend your deep-verification quota on the highest-risk source first.
  6. Read the three buckets. Valid addresses are re-entry candidates. Invalid addresses get removed and suppressed. Risky addresses are held back, including catch-all domains, which accept any address and so cannot confirm a specific mailbox. The catch-all email verification page explains how these are handled.
  7. Export and save immediately. Download results as CSV, Excel or JSON, and record summary counts by source and category. On the Free plan, results are kept for only 24 hours, so save the file before you leave the session. Keep your own copy on Pro too.
  8. Re-import Valid contacts as a new segment. There are no native ESP, CRM or Zapier integrations, so this step is manual: re-import the CSV, or automate through the API on Pro using API key setup. Spot-check any high-value contact with the free email checker.

Bottom line: Export, tag, split, verify, read, save and re-import, and record your counts before the retention window closes.

What does a real reinstatement case look like?

The example below uses hypothetical results, but the arithmetic is real and the limits match the plans above.

Scenario: An online course company has 41,700 contacts from three sources: 26,400 organic signups, a 9,800-person registrant list shared by a webinar partner, and a 5,500-contact legacy migration. One promotional campaign to all 41,700 produced 1,086 bounces, and the ESP flagged the account.

Step 1: Overall rate. 1,086 ÷ 41,700 = 2.6%.

Step 2: Rate by source.

Source Contacts Bounces Bounce rate
Organic signups 26,400 118 0.4%
Partner registrant list 9,800 742 7.6%
Legacy migration 5,500 226 4.1%
Total 41,700 1,086 2.6%

Check: 118 + 742 + 226 = 1,086. The partner list is 23.5% of contacts (9,800 ÷ 41,700) but produced 68.3% of bounces (742 ÷ 1,086). That is the story the reviewer needs to see.

Step 3: Codes. Of the 1,086 bounces, 1,011 were 5.1.1, 37 were 5.2.2 and 38 were 5.7.1 (check: 1,011 + 37 + 38 = 1,086). The 38 policy blocks were spread across all three sources, which points to sending reputation rather than one list, so the appeal includes an authentication audit.

Step 4: Suppress. Suppress all 1,086 bounced addresses and 143 unsubscribes and complaints from the organic segment. Remaining: 41,700 − 1,086 − 143 = 40,471. By segment: organic 26,139, partner 9,058, migration 5,274 (check: 26,139 + 9,058 + 5,274 = 40,471).

Step 5: Split and verify. Pro requires two uploads: 25,000 rows and 15,471 rows. Standard verification of all 40,471 is unlimited. Deep verifications go to the partner and migration segments first: 9,058 + 5,274 = 14,332 of the 25,000 monthly quota, leaving 10,668 spare.

Free cannot handle this in one month. 40,471 ÷ 150 = 269.8, so you would need 270 lists, and Free allows 25 a month.

Hypothetical results:

Segment Valid Risky Invalid
Organic 24,900 810 429
Partner 7,600 900 558
Migration 4,700 330 244
Total 37,200 2,040 1,231

Checks: 24,900 + 810 + 429 = 26,139; 7,600 + 900 + 558 = 9,058; 4,700 + 330 + 244 = 5,274; and 37,200 + 2,040 + 1,231 = 40,471. Overall, that is 91.9% Valid, 5.0% Risky and 3.0% Invalid. The partner list was 6.2% invalid (558 ÷ 9,058), against 1.6% for organic signups (429 ÷ 26,139).

Step 6: Re-entry plan. Only Valid contacts go out, and the 2,040 Risky addresses stay on hold.

Days Audience Volume Bounce ceiling
1–3 Most recently engaged organic Valid contacts 5,000 Under 0.5% (no more than 25 bounces)
4–7 Next organic Valid contacts 10,000 Under 1%
8–14 Remaining organic Valid contacts 9,900 Under 1%
15–21 Migration Valid (4,700), then partner Valid (7,600), as separate sends 12,300 Under 1% per send

Checks: 5,000 + 10,000 + 9,900 = 24,900 organic Valid, and 4,700 + 7,600 = 12,300. Total Valid sent: 37,200.

Cost: One Pro month at $29 covers this 40,471-contact list, which works out to about $0.72 per 1,000 contacts (29 ÷ 40.471). The larger cost is the afternoon of work, and the payoff is an audit trail a reviewer can check line by line.

Bottom line: The arithmetic isolates one bad source and gives a specific fix, which is far more persuasive than a general cleanup claim.

What should the appeal say?

A strong appeal is short and specific. It should fit on one screen and point to attachments that hold the detail. Use this structure:

Subject: Remediation plan, account [ID]: bounce spike on [campaign], [date]

The [date] campaign to [N] contacts produced [N] bounces ([X]%). We traced [N] of those bounces to one source: [source, import date, size]. The cause was [one-sentence cause].

We have stopped all marketing sends. We suppressed [N] bounced addresses and [N] unsubscribes and complaints, and we keep a copy of that file. We then verified the remaining [N] contacts: [N] Valid, [N] Risky, [N] Invalid. Risky and Invalid contacts are excluded from sending.

The campaign produced [N] 5.1.x list failures, [N] 5.7.x policy blocks and [N] 5.2.2 mailbox-full bounces. For the policy blocks we have [audited SPF, DKIM and DMARC / described the fix].

Re-entry sends go only to verified, recently engaged contacts. We will ramp from [N] to [N] over [N] days with a bounce ceiling of 1% per send, and we will share per-send results.

Going forward we will [verify at signup / verify every import before upload / re-verify quarterly].

Send attachments through the channel the ESP specifies. Share counts and suppression data, but avoid sending more personal data than the review requires.

Bottom line: Lead with the cause, quote counts by source and code, and commit to a ceiling you will measure.

How long does reinstatement take?

No public standard exists. Automated warnings are often lifted within a day or two of a credible response. Manual compliance reviews commonly take several business days, and longer if the reviewer asks follow-up questions about consent. Your first reply is the biggest variable: a case that includes the attachments above usually needs fewer rounds of questions.

Inbox placement recovers on a separate clock. Read does one high-bounce campaign hurt deliverability for weeks? for what to expect after restoration. For platform-specific processes, see our guides on Mailchimp suspensions, SendGrid's under-review status, Brevo suspensions and Mailgun warnings.

Bottom line: A complete first appeal is the most reliable way to shorten the wait.

What if the ESP terminates the account?

Termination is harder to reverse, and moving the same unverified list to a new provider reproduces the problem. Before you onboard elsewhere, verify the full list, bring your suppression file and consent records, and warm up volume gradually.

Do not split one problem list across several accounts or sending domains to stay under thresholds. M3AAWG, the industry body for messaging security, publishes best practices that treat spreading mail this way, often called snowshoeing, as abusive. See M3AAWG for its guidance.

If the list was bought or scraped, no verification result will rescue an appeal. The honest route is to stop mailing those contacts. For consent baselines in the US, the FTC's CAN-SPAM compliance guide sets out opt-out and disclosure rules, including honouring opt-out requests within 10 business days. Verification supports email verification compliance and hygiene, but it does not replace opt-in.

Bottom line: A new ESP fixes nothing if the list has not changed.

How do you keep bounces from triggering another suspension?

Verify contacts when they enter your system, then re-verify on a schedule.

If you are choosing a tool for this ongoing work, how to choose an email verifier lists the criteria to compare. Automating checks through the email verification API and automation workflow makes this routine rather than an emergency.

Bottom line: Verification at capture, at import and on a schedule makes the next suspension unlikely.

What mistakes get appeals rejected?

Bottom line: Most rejections come down to sending too soon or claiming a clean list without evidence.

How we compared (and limitations)

This guide draws on public documentation: RFC 3463 for status codes, Amazon SES's published thresholds, Google's sender guidance, Yahoo's sender requirements, and the FTC's CAN-SPAM guide. We have not run controlled tests against any ESP's review team, and platform thresholds and review processes change without notice.

The worked example uses hypothetical results to show the arithmetic, so your numbers will differ. Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's own stated figure, not an independent benchmark. The company publishes its open-source verification engine on GitHub, so you can read how its core checks work. The hosted product may differ from that code, so confirm current plan limits and features before you commit.

Appeal evidence checklist

Evidence What to include Why reviewers need it
Bounce attribution Counts by import, form, and migration source Shows where the problem started
Error codes Split of 5.1.x list failures vs 5.7.x blocks Separates list hygiene from reputation
Removals Exact number of addresses suppressed Proves the fix was carried out
Verification Valid, Risky, and Invalid counts for the rest Shows the remaining list is safe
Opt-in proof Sign-up records for the sending list Confirms consent
Ramp plan 1% per-send ceiling, under 2% overall Gives a measurable commitment

Frequently asked questions

How long does ESP account reinstatement take?

Timelines vary by provider and by how severe the restriction is. Automated warnings can clear quickly after a clear reply, while manual compliance reviews often take days to a few weeks. Delays usually come from incomplete evidence, so a complete appeal with counts and verification results tends to move faster.

What bounce rate is considered too high?

Most ESPs treat hard bounce rates above roughly 2% as a warning sign, though each provider sets its own thresholds, and some act on spikes even when the overall rate looks acceptable. Check your provider's acceptable use or sending policy for the exact figure they apply.

Should I buy a new list to replace the bad one?

No. Purchased or scraped lists are a common reason for termination and are rarely reversible on the same account. Rebuild your list through opt-in sign-ups, then verify it before sending. Reviewers look for proof of consent, so keep records of how each contact joined.

What is the difference between a hard bounce and a soft bounce?

A hard bounce is a permanent failure, such as a nonexistent address, and should be suppressed immediately. A soft bounce is temporary, such as a full mailbox, and is retried for a limited time. Only hard bounces usually count directly against list quality in an appeal, though repeated soft bounces can also be treated as a warning.

Can I keep sending to contacts who have not opened recently?

Sending to long-inactive contacts raises bounce, complaint, and spam-trap risk during a review. Start with recently engaged contacts, and only re-engage older segments after verification and a reconfirmation campaign. Suppress anyone who does not respond.

What should an appeal email include?

A strong appeal includes the timeline of the bounce spike, bounce counts by source and SMTP code, the number of addresses removed, verification results for the remaining list, proof of opt-in, and a sending plan with a per-send ceiling. Keep it factual and specific.

Do bounces from 5.7.1 errors affect my list?

Not usually. Codes beginning with 5.7 typically point to reputation, policy, or authentication problems such as missing SPF, DKIM, or DMARC. Your appeal should address those separately by showing authentication setup and reputation fixes, rather than list cleaning alone.

Will verification guarantee reinstatement?

No. Verification reduces future bounces, but it does not erase past complaints or prove consent. Reinstatement depends on the full picture: root cause, removals, verified sends, and a credible plan. Treat verification as one part of the evidence.

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 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.