Article
How to Avoid ESP Suspension When Importing an Old Email List
By Unlimited Verifier Team ·

Summary
To avoid an ESP suspension when importing an old list, merge suppressions first, quarantine the whole batch, and verify every address before any campaign. Mail only Valid contacts and ramp volume while each send stays under 1% bounces.To avoid an ESP suspension when importing an old list, verify the file before it reaches your ESP, quarantine every contact until verification ends, then mail only Valid contacts while each send stays under 1% bounces.
Usually the upload itself sends nothing. The restriction comes from the first campaign to those contacts, so the protection has to happen before the file touches your ESP. This guide covers the full sequence. For the wider picture of why accounts get restricted, start with our pillar guide on high bounce rate account suspension.
Quick answer
- Merge suppressions first. Remove anyone who unsubscribed, complained or bounced before, so the import cannot re-subscribe them.
- Quarantine the whole batch. Load it into a tagged segment with no campaigns mailed to it until verification is done.
- Verify, then split by result. Keep Valid addresses, hold Risky ones and suppress Invalid ones.
- Ramp under a bounce ceiling. Start with a re-permission send to about 2,000 Valid contacts, then grow in steps of roughly 2–2.5× while every send stays under 1% bounces.
Why does importing an old list cause a suspension when the import sends nothing?
The upload sends nothing, but it decides what your next campaign will hit. ESPs judge your account on the bounce and complaint rates of your sends, so a risky import shows up later as a spike on a campaign that looked routine.
Three properties of old lists create that risk:
- Closed mailboxes. An address that was valid two years ago may no longer exist. A closed mailbox returns a permanent failure, such as SMTP enhanced status code
5.1.1(bad destination mailbox), defined in RFC 3463. - Recycled spam traps. Some abandoned addresses are reactivated by mailbox providers and used to catch senders who never clean their lists.
- Forgotten consent. People who signed up for a webinar years ago often don't remember it. They are more likely to report you as spam than to look for your unsubscribe link.
Import can also undo earlier protection. An opt-out recorded in your old platform but missing from the new one brings that contact back as subscribed. Many ESP import screens offer an option to update existing contacts, and that option can overwrite a stored opt-out, so check it before every upload. If you have already seen the symptom, our guide to why bounce rates jump after importing a list covers diagnosis.
Bottom line: An import is a risk decision made at upload time, and its cost appears as a bounce or complaint spike at send time.
Which old lists carry the most risk?
The source of a list predicts its risk better than its size does. SaaS teams often accumulate old CRM exports, and that is where email verification for ecommerce and SaaS workflows tend to need the most care. Tag each batch with its origin and last mail date before you touch it.
| Source | Risk | Why | What to do |
|---|---|---|---|
| Purchased or rented lists | Highest | Consent is usually undocumented, and trap exposure is a known concern | Do not import. ESP acceptable-use policies commonly prohibit them, and an account can be terminated for it |
| Scraped or harvested addresses | Very high | No relationship with the recipient | Do not import |
| Old CRM export, not mailed in 18+ months | High | Many business addresses have changed employers or closed | Verify, quarantine, re-permission |
| Event registrants and badge scans | Medium to high | Real consent, but often stale and sometimes mistyped at capture | Verify, suppress Invalid, re-permission |
| Previous ESP export with suppression history | Medium | Consent is documented, but bounce history often doesn't travel | Merge suppressions from the old platform first |
| Customers who bought within 12 months | Lower | Recent relationship, recent addresses | Verify, then send with a short re-engagement |
No published standard says how fast business addresses decay. Treat any batch older than about 12 months as a fresh-risk list rather than a known-good one.
Bottom line: Rank each batch by source and age before importing, and rule out purchased or scraped data entirely.
What is the safest order for importing an old list?
Follow these eight steps in order. Each one closes a route to a bounce or complaint spike, and later steps depend on the cleanup in earlier ones.
- Pause anything that could reach the new contacts. Check automations and drip sequences as well as campaigns, because they can mail an unverified contact on their own.
- Export every suppression list you hold. Include the ESP's bounce and unsubscribe lists, the old platform's suppressions and your own opt-out log. Suppressions often don't transfer automatically when you change platforms, so keep a copy you control.
- Remove duplicates and suppressed addresses from the file. Match on lowercase email. Drop suppressed addresses rather than importing them and hoping the status sticks.
- Tag every row. Add
import_source,import_dateandlast_mailedcolumns. These let you quarantine or delete a bad batch later without touching the rest. - Import into a quarantine segment. Name it for the batch and block mailing until verification completes. Keep it in place through a confirmation window. We suggest 14 days as a starting point; that is our recommendation, not a platform rule.
- Verify the whole batch. Run every row through a verifier that checks syntax, domain, MX records and the SMTP mailbox, and flags catch-all, disposable and role-based addresses.
- Re-import Valid contacts into a separate sending segment. Suppress Invalid addresses in the ESP and keep Risky addresses in quarantine.
- Send a re-permission message to the first tranche. Ramp only after each send passes the bounce check described below.
Step 2 is where teams most often slip. Re-subscribing people who unsubscribed in 2021 produces complaints, and complaints are harder to recover from than bounces because they are recipients actively choosing to report you.
Unlimited Verifier has no native ESP, CRM or Zapier integration, so steps 6 and 7 are a CSV export and re-import, or API calls from your own script.
Bottom line: Suppress first, tag everything, quarantine, verify, and only then send.
How should you verify an old list before importing it?
Verification answers one question: can this address receive mail? It does not tell you whether the person wants it. Knowing that boundary shows you what risk remains.
| Result | What it means | Action |
|---|---|---|
| Valid | Syntax, domain, MX and mailbox checks passed | Eligible for the first tranche after the test send |
| Risky | Catch-all domain, disposable address, role account such as info@, or a result that can't be confirmed |
Hold in quarantine and decide address by address |
| Invalid | Failed syntax, domain, MX or mailbox checks | Suppress permanently |
Verification has two limits to plan around:
- Catch-all domains. A catch-all server accepts every address, so the mailbox cannot be confirmed. B2B lists often contain many of these, so a large Risky bucket is normal. The catch-all email verification page explains how these results are handled.
- Traps that look deliverable. Some spam traps exist only to catch harvested or bought lists, and they can pass a mailbox check. No verifier can identify all of them from outside, which is why source matters more than verification for this risk.
Verification also doesn't establish consent. A Valid address is deliverable, not permitted.
Bottom line: Verification removes dead and risky addresses but cannot catch every trap or prove consent, so keep the first sends small.
How do you split an import so one bad batch can't sink the account?
Batching limits the blast radius. If one source produces a spike, you quarantine that batch alone instead of pausing everything.
Plan the split around your plan's real limits. Unlimited Verifier's Pro plan costs $29/month, or $25/month billed annually, and allows lists of up to 25,000 emails each, with 25,000 deep verifications a month. The Free plan ($0) allows 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. Standard verification is unlimited on every plan with no per-email fee. Before you commit, compare email verification pricing on the units you will actually use: list size, deep checks and monthly volume.
The arithmetic matters:
- Free plan ceiling: 25 lists × 150 emails = 3,750 emails a month. A 35,400-row import would need 236 Free lists, so it needs Pro.
- Pro split: A 35,400-row file becomes two lists, 25,000 and 10,400.
Two practical rules:
- Keep batches small enough to act on. 2,000 to 5,000 contacts from one source is easy to pull. 40,000 contacts mixing three sources is not.
- Never mix sources in one file. Once a bad source is blended in, you cannot remove it without re-checking everything.
Bottom line: Split by source and date, not just by row count, so a single bad batch can be pulled cleanly.
How do you verify an old list step by step?
This tutorial assumes suppressions are already merged out of the file.
- Export the list as CSV. Include the email column and any date or source field. Keep the source tag so you can split later.
- Create an account. You can sign up for a free account to test a few hundred addresses on the Free plan.
- Upload the file. On the upload and verify a list page, CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. A row with an email and two short fields is typically under 100 bytes, so 25,000 rows come to roughly 2.5MB. Long free-text columns change that quickly, so check file size if your export is wide.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox, with catch-all, disposable and role-based flags applied.
- Read the three buckets. Valid goes to the test segment. Risky stays in quarantine. Invalid is suppressed.
- Download results the same day. Free results are kept for 24 hours and Pro results for 30 days. Export as CSV, Excel or JSON and store the files outside the tool.
- Re-import only Valid contacts into a new segment in your ESP, and add Invalid addresses to the ESP's suppression list.
- Spot-check important addresses with the free email checker before they go into a campaign.
For recurring imports, the email verification API and automation workflow runs the same checks from a script. API access is included on Pro, not Free, and Pro covers 100,000 emails a month. Bulk requests accept up to 10,000 emails each, so a 35,400-row file needs four requests: 10,000, 10,000, 10,000 and 5,400. You can generate API keys from your account.
Bottom line: Export, verify, download the same day, re-import only Valid, and suppress Invalid.
What does a worked example look like for 40,000 legacy leads?
This example is illustrative. The result percentages are hypothetical, but the limits and arithmetic reflect the plans described above.
The situation: A B2B SaaS company has 15,000 active subscribers and wants to import 40,000 leads from an old CRM export. Most of those leads haven't been mailed in more than two years.
Step 1: Remove duplicates and suppressed addresses.
- 40,000 raw rows
- Minus 2,000 duplicates within the file: 38,000
- Minus 2,600 matching prior unsubscribes, complaints or bounces: 35,400 to verify
Step 2: Split.
- List A: 25,000 rows (the Pro per-list maximum)
- List B: 10,400 rows
- Standard verification of all 35,400 rows is included, with no per-email fee.
Step 3: Spend deep verifications on the risky rows.
Pro includes 25,000 deep verifications a month. The company deep-verifies the 8,100 Risky addresses, which leaves 16,900 of the monthly allowance (25,000 − 8,100) for later batches.
Step 4: Hypothetical results.
| Bucket | Count | Share | Action |
|---|---|---|---|
| Valid | 23,900 | 67.5% | Imported to a tagged sending segment |
| Risky | 8,100 | 22.9% | Held in quarantine |
| Invalid | 3,400 | 9.6% | Suppressed in the ESP |
Check: 23,900 + 8,100 + 3,400 = 35,400.
Step 5: Ramp the Valid segment.
Each day's send is a re-permission message to that tranche, and every send is checked against a 1% bounce ceiling before the next one goes out.
| Send | Audience | Volume | Bounce ceiling (1%) |
|---|---|---|---|
| Day 1 | Most recent Valid contacts from the newest source | 2,000 | 20 |
| Day 4 | Next Valid tranche | 5,000 | 50 |
| Day 8 | Next Valid tranche | 10,000 | 100 |
| Day 15 | Remaining Valid contacts (23,900 − 2,000 − 5,000 − 10,000) | 6,900 | 69 |
Why the ramp matters: If 0.4% of the Day 1 contacts bounce, that is 8 bounces out of 2,000, which passes. If 3% bounce because one source was worse than its tag suggested, that is 60 bounces, which fails. The company pauses, re-verifies that source and holds the rest back. Sending all 23,900 at that same 3% rate in one go would have produced 717 bounces, enough to create a real spike.
Cost: One month of Pro at $29, with standard verification of all 35,400 rows included.
Bottom line: A small first send with a fixed bounce ceiling turns a risky import into a test you can pass or fail cheaply.
What should the first sends after an import look like?
The first sends should be small, relevant and checked after every tranche, with a rule that pauses sending when bounces cross a threshold.
- Use a stop-loss at 1% bounces per send. If hard bounces exceed 1% in any send, pause, re-verify that batch and check its source tag. In a 500-contact send, five bounces is exactly 1%, so pause at six.
- Lead with re-permission. Ask contacts to confirm they want your mail. Contacts who never respond should stop receiving regular campaigns, and you should confirm your consent basis for any continued mailing.
- Send to recent engagers first. Anyone who opened or clicked in the last 90 days goes to the front of the ramp, because they are the most likely to be wanted and deliverable. For the broader playbook, see how to send to an old list safely.
Which threshold should you plan around? Sources disagree, and no platform publishes one universal number. Amazon SES's developer documentation describes a 5% bounce rate as the point where an account is placed under review and 10% as a level that can lead to pausing. Other ESPs act at lower levels on single campaigns to unproven lists. Our recommendation is to plan around a 2% total bounce ceiling, and keep each import send under 1%. Platform-by-platform figures are in our guide to what bounce rate gets your ESP account suspended.
For complaints, Google's sender guidelines ask bulk senders to keep user-reported spam below 0.1% and never let it reach 0.3%. A re-permission step protects that number directly.
Bottom line: Ramp in stages, pause at 1% bounces per send, and treat 2% total as your hard ceiling.
What if the import has already gone out?
Stop sending to the batch, suppress every hard bounce and complaint from the campaign, and quarantine the rest of the batch before anything else goes out.
- Pause every automation and campaign that includes the batch.
- Export the campaign's bounce and complaint report and suppress every hard bounce and complaint.
- Check the source tag. If the spike sits in one source, quarantine that whole source. If it is spread across sources, verify the full batch.
- Verify what remains and apply the same Valid, Risky and Invalid split.
- Record the counts of what you removed. Those numbers form the core of any appeal.
Recovery lags the fix. One high-bounce campaign can affect inbox placement for weeks, so keep the ramp slow even after the account is stable. Our guide on deliverability recovery timelines explains why. For the immediate response, use our 5 steps after a bounce rate spike checklist. If the account is already restricted, platform-specific steps are in our Mailchimp suspension guide and our note on SendGrid's under-review status.
Bottom line: Stop, suppress, segment by source, verify, and record every count before you send again.
What compliance rules apply to imported contacts?
Compliance depends on where your recipients are and what consent you hold, not on how clean the list looks. Verification supports email verification compliance and hygiene, but it is not proof of consent.
- United States. CAN-SPAM covers commercial email regardless of where the list came from. You need a working opt-out, a valid physical postal address, and you must honour opt-outs within 10 business days. The FTC's CAN-SPAM compliance guide sets out the details.
- United Kingdom and EU. Marketing to individual consumers generally requires consent under PECR and GDPR. B2B rules differ, and the ICO's guidance explains where the lines sit. Take advice on your specific list.
- Imported opt-outs. Anyone who opted out in the old system must stay opted out. Re-subscribing them is among the most common compliance failures after an import.
If you can't show how and when a contact opted in, treat them as a re-permission candidate, not a sending contact.
Bottom line: Verify for deliverability, but base sending on consent, and never re-subscribe someone who opted out.
Which import strategy should you choose?
Each option trades speed against risk. This table compares the realistic choices for an old list.
| Strategy | Bounce risk | Compliance risk | Best for |
|---|---|---|---|
| Import and mail the whole list now | Very high | High | Nothing. Avoid it |
| Import and mail only the most recently engaged contacts | Medium | Low to medium | Lists with reliable engagement data |
| Quarantine, verify, then re-permission Valid contacts | Low | Low | Most old CRM and event lists |
| Verify and import Valid only, with no re-permission | Low to medium | Medium | Recent lists with confirmed consent |
| Import purchased or scraped data | Very high | Highest | Nothing. Discard the list |
The third row suits most teams. It costs a few extra days and a small test send, and it turns an unknown list into one you can defend.
Bottom line: Quarantine, verify and re-permission protects both your bounce rate and your compliance record.
What mistakes cause suspensions after an import?
- Mailing the whole import on day one. The first send is your test, so make it small enough that a failure is cheap.
- Importing suppressed contacts as subscribed. Merge suppressions before upload, and check your "update existing contacts" setting.
- Verifying but not segmenting. One send that mixes Valid and Risky addresses undoes the work.
- Treating Risky as Valid. Catch-all and role-based addresses need a decision for each one.
- Blending sources in one file. Once mixed, a bad source can't be pulled out cleanly.
- Losing results. Free results are kept for 24 hours and Pro results for 30 days, so export on the day you verify.
- Assuming verification proves consent. A deliverable address is not a permitted one.
- Skipping per-send checks. A tranche that is clean at 1,000 contacts can spike at 10,000 if the larger group includes a worse source.
Bottom line: Most import-related suspensions come from sending too much, too early, to contacts whose status nobody checked.
How do you keep the list clean after the import?
Verify at the point of entry, then re-check on a schedule. Real-time validation at signup stops new bad addresses before they reach your list, and API access on Pro lets you do this from your own forms. Re-verify the list on a regular cadence, such as quarterly for most lists, and treat monthly as the right rhythm for fast-moving B2B data. Our guide to email list maintenance covers how to schedule both.
Bottom line: Validate at entry and re-verify on a schedule, so the next import is a routine task rather than a crisis.
How we compared (and limitations)
This guide is based on public documentation: RFC 3463 for SMTP status codes, Amazon SES's published bounce guidance, Google's sender guidelines, the FTC's CAN-SPAM guide and the ICO's published material. We have not run controlled tests against any ESP's review team, and thresholds vary by platform and can change without notice.
Unlimited Verifier's plan limits, file size limit, API batch size and results retention come from its published plan details. The company states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. All worked-example percentages and bounce counts are illustrative. To compare verifiers on criteria beyond price, see our guide on how to choose an email verifier and our overview of the best email verification tools.
Ramp schedule under a 1% bounce ceiling
| Step | Audience | Gate to proceed |
|---|---|---|
| 1. Re-permission | About 2,000 Valid contacts | Bounces under 1%, clear confirm rate |
| 2. Expand | About 2.5x prior step | Bounces under 1%, complaints low |
| 3. Expand | About 2.5x prior step | Same gates as step 2 |
| 4. Full list | Remaining confirmed Valid | Stop and reverify if any send breaches 1% |
Frequently asked questions
Does uploading a list to an ESP send emails automatically?
Usually no. A bulk upload typically just stores contacts. The risk appears when you send a campaign to those contacts, because bounces and complaints from that send count against your account's reputation metrics.
What bounce rate causes an ESP suspension?
Thresholds vary by provider and are set in each provider's acceptable-use or sending policy. Many senders aim to keep bounces under 1% per send, which is the ceiling this guide uses as a conservative target. Check your ESP's published limits.
Should I import old contacts into my existing list?
Not directly. Keep them in a separate, tagged quarantine segment with no campaigns until verification is complete. Only move addresses into active lists after they pass verification and a re-permission check.
What is a re-permission send?
It is a single email asking old contacts to confirm they still want to hear from you. Only those who click to confirm should move into your active list, which protects both deliverability and your complaint rate.
Can an import re-subscribe people who unsubscribed?
Yes, if your old opt-outs are missing from the new platform or if the import overwrites existing contact status. Merge all previous unsubscribes, bounces and complaints into your suppression list before uploading.
Why does an old list cause spam trap hits?
Some abandoned addresses are later recycled by mailbox providers as spam traps to catch senders who never clean their lists. Verification helps identify many of these, but no tool catches every trap, so ramp volume gradually.
Should I buy or rent a list to grow faster?
No. Purchased or rented lists usually lack documented consent and carry high trap exposure, and ESP acceptable-use policies commonly prohibit them. Growing through opt-in forms is the safer route.
How long should I wait before mailing an old list?
There is no universal number. Mail only after verification and suppression are complete, and treat anyone not mailed in 18 months or more as a re-permission candidate before any campaign.
What should I do if my account is already restricted?
Stop sending to the affected list, review your bounce and complaint reports, remove risky addresses, and contact your ESP's support with a remediation plan. Restarting with a verified, engaged segment is usually the path back.
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.