> ## Content Index
> Fetch the complete content index at: https://www.millionverifier.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Email an Old List Without Wrecking Your Sender Reputation
- URL: https://www.millionverifier.com/blog/how-to-email-an-old-list-without-wrecking-your-sender-reputation/
- Published: 2026-10-22T05:36:31.000Z
- Updated: 2026-10-22T05:36:31.000Z
- Author: Tamas Ham-Szabo

**To email an old list safely, verify every address first, then restart with your most recently engaged contacts in small batches, and grow volume only while bounces and complaints stay low.** Ask the least engaged contacts to reconfirm before you send them anything else. A contact counts as old once they haven't engaged for about six months. Past twelve months, some of the list's dead addresses may already have become spam traps.

- **Verify before anything else.** Even a reconfirmation email can damage your reputation if it goes to dead addresses.
- **Restart small.** Send to recent, engaged contacts first and add older segments only while results stay healthy.
- **Set stop rules below the platforms' limits.** Pause at 1% hard bounces on any batch, and review the message before growing if a small batch draws even one complaint.

## How old is too old for an email list?

![](https://www.millionverifier.com/content/images/2026/10/Section-01---How-Old-Is-Too-Old-selection.png)

Treat a contact as old once they haven't engaged for six months. Treat them as high risk after twelve.

| Time since last engagement | What has probably happened                                                                                                                                                                                                                                                                                                                                                                                                                                                | What to do                                                                                            |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Under 6 months             | Some addresses have decayed, but most still work                                                                                                                                                                                                                                                                                                                                                                                                                          | Verify, then send normally and watch the first send closely                                           |
| 6 to 12 months             | Engagement has gone cold. AWS advises against mailing subscribers who haven't engaged for 6 months or longer ([AWS](https://aws.amazon.com/blogs/messaging-and-targeting/what-is-a-spam-trap-and-why-you-should-care/?ref=millionverifier.com)), and Apollo doesn't offer the same bounce guarantee for verified emails older than six months ([Apollo](https://knowledge.apollo.io/hc/en-us/articles/4409227148045-Troubleshoot-Bounced-Emails?ref=millionverifier.com)) | Verify, segment, ramp up gradually, and reconfirm unengaged contacts                                  |
| Over 12 months             | Some dead addresses may now be spam traps. Mailbox providers often let an abandoned address hard bounce for 12 months or more before turning it into a trap ([AWS](https://aws.amazon.com/blogs/messaging-and-targeting/what-is-a-spam-trap-and-why-you-should-care/?ref=millionverifier.com))                                                                                                                                                                            | Verify, then send only a reconfirmation email to the oldest segment and keep the contacts who confirm |

HubSpot uses the same 12-month line. Its suspension appeal asks whether you have contacts you haven't emailed in over 12 months ([HubSpot](https://knowledge.hubspot.com/marketing-email/why-is-my-email-suspended?ref=millionverifier.com)).

Count from the last time a contact engaged, not the last time you sent. A contact you mailed last month who hasn't clicked, replied or bought anything in two years is still an old contact. Don't rely on opens: Apple Mail Privacy Protection loads images automatically, which inflates open rates.

## What goes wrong when you email an old list?

![](https://www.millionverifier.com/content/images/2026/10/Section-02---What-Goes-Wrong-selection.png)

Four things, and they compound. A single send to a stale list can trigger all of them at once.

1. **Dead addresses hard bounce.** People change jobs and abandon accounts, so an old list carries more addresses that no longer exist. Brevo can suspend campaigns above a 2% hard bounce rate, and HubSpot, MailerLite and Amazon SES act at 5%. See [What Is a Good Email Bounce Rate?](https://www.millionverifier.com/blog/what-is-a-good-email-bounce-rate-benchmarks-for-newsletters-and-cold-email/) for each platform's limit.
2. **Recycled spam traps accept your mail.** Once a provider turns an abandoned address into a trap, it stops bouncing, so it looks like a working address. Sending to traps can lead to a blocklist listing that blocks much of your mail.
3. **People who forgot you report spam.** Mailchimp warns that even a contact with a valid address may report spam if they don't want to hear from you ([Mailchimp](https://mailchimp.com/help/reconfirm-contacts/?ref=millionverifier.com)). Gmail wants your spam rate below 0.1%, which is one complaint per thousand emails, and treats 0.3%, three per thousand, as the line you must never reach.
4. **The sudden volume looks suspicious.** Going from silence to a full-list blast is a spike. Google warns that increasing volume too quickly can cause delivery issues and recommends consistent sending volumes ([Google](https://support.google.com/mail/answer/15256272?ref=millionverifier.com)).

Verification fixes the first problem and shrinks the second: it removes addresses that still bounce before they can turn into traps. It can't detect a trap that already accepts mail, and it can't fix the third or fourth. For more on what verification can and can't catch, see [The Ugly Truth About Spam Traps](https://www.millionverifier.com/blog/the-ugly-truth-about-spam-traps-and-what-email-verification-can-actually-fix/).

## Step 1: Verify the whole list before you send anything

![](https://www.millionverifier.com/content/images/2026/10/Section-03---Step-1-Verify-selection.png)

Verify every address before the first email, including the reconfirmation email. Mailchimp notes that a reconfirmation message sent to unengaged contacts can itself affect your sending reputation, so it needs a clean list too.

1. **Export the list without its suppressions.** Leave past unsubscribes, complaints and hard bounces out. Never re-add them, however old the list is.
2. **Run it through the** [**Bulk Email Verifier**](https://www.millionverifier.com/services/bulk-email-verifier/)**.**
3. **Act on each result:**
  - **Good:** eligible for the restart.
  - **Risky** (catch-all and unknown): set aside. These go last, in small batches.
  - **Bad:** remove, and add to your sending platform's suppression list so they can't come back with the next import.

For example, suppose an 8,400-contact list comes back with 610 Bad and 940 Risky results. You restart with the 6,850 Good addresses, and the 940 Risky ones wait until the Good segments have gone out cleanly.

## Step 2: Segment by last engagement and signup date

![](https://www.millionverifier.com/content/images/2026/10/Section-04---Step-2-Segment-selection.png)

Split the Good results by how recently each contact engaged. Engagement means a click, reply, purchase or login, not an open. If you have no engagement history, use the signup date instead.

| Segment | Who is in it                                                    | What they get                                                             | Send order                                |
| ------- | --------------------------------------------------------------- | ------------------------------------------------------------------------- | ----------------------------------------- |
| A       | Engaged in the last 6 months                                    | Your normal email, with a short note that you're back                     | First                                     |
| B       | Last engaged 6 to 12 months ago                                 | A "we're back" email that reminds them who you are and why they signed up | Second                                    |
| C       | No engagement for 12 months or more, or never engaged           | A reconfirmation email only (Step 4)                                      | Third                                     |
| D       | Risky verification results, split by age the same way as A to C | The email for their age group, in small batches                           | Last, and only if A to C went out cleanly |

Segment A protects you. Recent, engaged contacts are the most likely to open, click and not complain, and those signals help offset the weaker results from older segments.

## Step 3: Set stop rules before the first send

![](https://www.millionverifier.com/content/images/2026/10/Section-05---Step-3-Stop-Rules-selection.png)

Decide in advance when you'll pause, so nobody has to make that call in the middle of a bad send.

| Signal                                      | Stop rule                                                                        | Why this line                                                                                                                                               |
| ------------------------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hard bounce rate on any batch               | Pause at 1%                                                                      | A list you've just verified shouldn't come near 1%. It also leaves room below Brevo's 2% suspension line and the 5% lines elsewhere                         |
| Complaints on a batch of under 1,000 emails | Review the message and the segment before growing if even one complaint comes in | One complaint in a 500-email batch is already 0.2%, so a percentage can't work at this size                                                                 |
| Complaint rate across the whole restart     | Pause if the running total reaches 0.05%                                         | Our recommendation: half of the 0.1% line that Gmail, HubSpot and Amazon SES all use                                                                        |
| Block bounces (5.7.x) at one provider       | Stop sending to that provider                                                    | The provider is refusing your mail, and more volume makes it worse                                                                                          |
| Deferrals (4.x.x)                           | Hold volume flat                                                                 | Google advises waiting before you increase volume when deferrals appear ([Google](https://support.google.com/mail/answer/15256272?ref=millionverifier.com)) |

Your platform's complaint count also undercounts Gmail recipients. Gmail reports spam rates in aggregate through Postmaster Tools instead of passing on each complaint, and Postmaster Tools may show no data at all when your volume to Gmail is low. Treat any complaint you do see as a sign of more you can't see.

Check each batch 24 to 48 hours after sending before you send the next one. Some bounces arrive as separate bounce emails, and complaints can come in days after delivery. For how to read the codes behind a block, see [Hard Bounces vs. Spam Complaints](https://www.millionverifier.com/blog/hard-bounces-vs-spam-complaints-how-to-survive-the-gmail-yahoo-outlook-sender-rules/).

## Step 4: Send a reconfirmation email to the oldest segment

![](https://www.millionverifier.com/content/images/2026/10/Section-06---Step-4-Reconfirmation-selection.png)

Ask segment C to confirm they still want your emails, and keep only the contacts who do. AWS calls this a permission pass: a one-time campaign that lets recipients confirm they still want your mail, after which only confirmed contacts stay on future lists.

A good reconfirmation email has five parts:

1. **Who you are and where they signed up.** "You joined our newsletter at the 2024 Leeds trade show" beats "You're on our list".
2. **What they'll get and how often.** One line is enough.
3. **One clear button** that confirms the subscription.
4. **An easy way out.** A visible unsubscribe link, so leaving is easier than reporting spam.
5. **A deadline.** Say when you'll remove anyone who doesn't confirm, then do it.

Here's a short version you can adapt:

> **Subject:** Do you still want our emails?  
>  
> Hi Anna, you signed up for our product updates in 2024, and we haven't written in a while. We're restarting with one email a month. Want to stay on the list?  
>  
> \[Yes, keep me subscribed\]  
>  
> If we don't hear from you by 15 November, we'll remove you. No hard feelings.  
>  
> Not interested? \[Unsubscribe\] and you won't hear from us again.

Send it to segment C in small batches, under the same stop rules as everything else. Email marketing laws vary by country, so check the rules that apply to your contacts before you send.

**If you use Mailchimp,** its process works the other way round. You export the audience, unsubscribe the subscribed contacts, and send them a link to your signup form so they can opt back in. In that case, the button links to your signup form, and the deadline line can go, because nobody stays subscribed unless they sign up again.

Mailchimp also suggests sending reconfirmations from your business's own email client or another service, where permitted, because a reconfirmation sent to unengaged contacts can affect your Mailchimp sending reputation. Be careful with that for large segments. A staff mailbox has its own daily sending limits and shares your domain's reputation, so use a separate sending service, or keep the batches small.

## Step 5: Ramp up volume gradually

![](https://www.millionverifier.com/content/images/2026/10/Section-07---Step-5-Ramp-Up-selection.png)

Start with a small batch of your most engaged contacts and grow each send by 25% to 100%. That range comes from Google's own guidance for raising volume after delivery problems, and it works just as well for a restart.

Here's how the 6,850 Good addresses from Step 1 could go out, split into segment A (2,300), segment B (2,850) and segment C (1,700):

| Send      | Who gets it                                          | Batch size   | Change on the previous send |
| --------- | ---------------------------------------------------- | ------------ | --------------------------- |
| 1         | Segment A, most recently engaged first               | 500          | Start                       |
| 2         | Segment A                                            | 1,000        | +100%                       |
| 3         | Rest of segment A, plus the start of segment B       | 1,500        | +50%                        |
| 4         | Rest of segment B                                    | 2,150        | +43%                        |
| 5         | Segment C, reconfirmation email                      | 850          | Smaller                     |
| 6         | Rest of segment C, reconfirmation email              | 850          | Same                        |
| 7 onwards | Risky results, split by age, in batches of about 300 | 940 in total | Smaller                     |

Leave at least 24 hours between sends, and 48 if the previous batch came close to a stop rule. Move to the next row only when the previous batch has stayed under every stop rule. If a batch comes close to a limit, repeat that batch size instead of growing it. Once the restart is done, keep sending at a steady rhythm. Google recommends consistent volumes over random spikes.

## How do you keep the list from going stale again?

![](https://www.millionverifier.com/content/images/2026/10/Section-08---Keep-the-List-Fresh-selection.png)

Send regularly, remove people who stop engaging, and verify any data before it enters the list.

- **Run a sunset policy.** Decide when an unengaged contact gets one last re-engagement email and then leaves the list. A common rule for weekly senders is no click in 90 days. Klaviyo recommends sunset flows for exactly this reason: they remove unengaged recipients before their mailboxes become invalid ([Klaviyo](https://help.klaviyo.com/hc/en-us/articles/115005250408?ref=millionverifier.com)).
- **Verify before every import.** Event lists, partner lists and CRM exports go through the [Bulk Email Verifier](https://www.millionverifier.com/services/bulk-email-verifier/) before they reach your sending platform.
- **Verify at signup.** The [Email Verifier API](https://www.millionverifier.com/services/email-verifier-api/) checks addresses when people submit your form, so typos and disposable addresses never get in.
- **Don't go quiet for months.** A list you mail steadily never needs a restart plan.

## Frequently asked questions

#### Can I email a list I haven't used in two years?

Yes, but not with a normal campaign. Verify it first, then send only a reconfirmation email and keep the contacts who confirm. After 12 months, some abandoned addresses may have been turned into spam traps, so the people who confirm are the only part of the list you can trust.

#### When does an email list become stale?

Treat contacts who haven't engaged for six months as old, and anything over twelve months as high risk. AWS advises against mailing subscribers who haven't engaged for 6 months or longer, and recycled spam traps often bounce for 12 months or more before they go live.

#### Will email verification remove spam traps?

No. Verification removes addresses that still bounce, before they can become traps, and it flags risky ones. A trap that already accepts mail looks like a working address, so no verifier can detect it.

#### Should I send the reconfirmation email from my email platform?

Check your platform's guidance. Mailchimp suggests sending reconfirmation messages from your business's own email client or service where permitted, because reconfirmations sent to unengaged contacts can affect your sending reputation on Mailchimp. A staff mailbox has its own daily sending limits and shares your domain's reputation, so for anything beyond a small segment, use a separate sending service or keep batches small. Wherever you send it, verify the list first.

#### How fast can I ramp up sending to an old list?

Grow each send by 25% to 100%, starting with your most engaged contacts. Google uses the same range in its guidance for raising volume after delivery problems. Only move up while every batch stays under your bounce and complaint stop rules.

#### What should I do if bounces spike during the restart?

Pause that segment and read the bounce codes. 5.1.x codes mean dead addresses, which point to a list problem. 5.7.x codes mean the provider refused your mail, which points to a sender problem. [550 5.1.1 and Other Hard Bounce Codes](https://www.millionverifier.com/blog/550-5-1-1-and-other-hard-bounce-codes-when-to-suppress/) explains each code.

## Restart with a clean list

The safest restart starts before the first email. Run your old list through MillionVerifier, remove the dead addresses, and send your first batch knowing that every Good address can still receive mail. See how it works for dormant lists on the [Clean Old Email Lists](https://www.millionverifier.com/solutions/clean-old-email-lists/) page.

[Create your free account](https://app.millionverifier.com/register?ref=millionverifier.com) to get 100 free credits, no credit card needed.

---

[Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com)

---

Why Choose Millionverifier

![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp)

We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy.

[99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate)

![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp)

We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs.

[Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices)

![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp)

Our customers love what we do. We work hard to deliver the best results and user experience for our customers.

[Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service)