Emailing an Old List: How to Restart Without Getting Blocked

An old list is dangerous because a big share of it no longer belongs to the people who signed up. Mailboxes get abandoned and closed, and some of those closed addresses get turned into spam traps. If you send to the whole thing at once, the bounces, complaints and trap hits arrive together and can get your domain or IP blocked in a single send. The safe way back is in stages: mail the most recent and most engaged people first, run a permission pass on the rest, and suppress everyone who bounces or doesn't respond.

"Old" here means any list, or part of a list, you haven't mailed in a long time. A year is old. Three years is very old. The rest of this page assumes you have the right to email these people in the first place. If the list was bought, scraped or came from a partner, don't restart it at all.

Why old lists cause blocks

Addresses die, and some come back as traps

People change jobs, abandon personal accounts and switch providers. Mailbox providers close inactive accounts on a schedule:

• Google may delete a personal Google Account that's been inactive for at least 2 years (the policy doesn't apply to work or school accounts).
• Yahoo says a mailbox becomes inactive after 12 months without access, and an account can be deactivated after 18 months without a sign-in.

Work addresses disappear even faster, as soon as someone leaves the company.

Closed addresses hard bounce. That's bad on its own, because a high bounce rate is one of the clearest signs of a sender with poor list hygiene. Worse, Spamhaus and AWS both describe recycled spam traps: addresses that reject mail for a period, often 12 months or more, and are then reactivated to catch senders who never stopped mailing them. A list that's been sitting for years will have some. See what spam traps are for the background.

The people who are still there forgot you

Someone who signed up three years ago and hasn't heard from you since may not remember doing it. The easiest way for them to get rid of you is the "report spam" button. Google requires senders to keep the spam rate in Postmaster Tools below 0.3% (and recommends below 0.1%), and Yahoo uses the same 0.3% figure. A sudden send to a forgotten list can blow past that in one day. See the Gmail spam rate threshold for what those numbers mean.

Volume spikes look suspicious

If your domain normally sends a few thousand messages a week and suddenly sends 200,000, receivers notice. A sudden jump in volume is a classic pattern of compromised or abusive senders, and it can draw deferrals like Gmail's 421 4.7.0 or 4.7.28 even before anyone complains.

Before you send anything

1. Confirm you have permission. Check how and when these people signed up. If you can't say, don't mail them.
2. Check authentication. Make sure SPF, DKIM and DMARC all pass for the domain you'll send from. Run it through the email checker. Old lists sometimes get restarted on a new platform, and the new platform is the part nobody set up.
3. Suppress what you already know is bad. Past hard bounces, past unsubscribes and past complaints stay suppressed forever, no matter how old.
4. Clean out the obviously invalid. A verification service can remove syntactically invalid and undeliverable addresses before you send. It won't catch recycled traps, which accept mail like real mailboxes, but it cuts the bounce rate.
5. Segment by age and last engagement. You want groups like: engaged in the last 6 months, 6 to 12 months, 1 to 2 years, more than 2 years, and never engaged. If you don't have engagement data, use signup date.

A staged restart

The specifics (how many addresses per stage, how long to wait between them) depend on your normal volume and how old the list is. The shape is the same:

1. Start with the freshest segment. Mail the most recent and most engaged group first, at a volume close to what you normally send. These are the people most likely to recognize you.
2. Make the first message a reintroduction. Remind people who you are, how they signed up and what they'll get from you. Put a clear unsubscribe link near the top. For older segments, make it a permission pass: ask them to click to stay on the list.
3. Watch the results before the next stage. Look at hard bounces, spam complaints, deferrals and any blocklist or block notices for each receiving domain. Read the bounce messages, not just the counts; the blocklist playbook explains what the common ones mean.
4. Suppress as you go. Remove every hard bounce immediately and every complaint. For permission-pass segments, people who don't confirm come off the list.
5. Move to the next older segment only if the last one was clean. If a stage produced a bounce or complaint spike, stop, look at what went wrong and decide whether the next segment is worth the risk at all.
6. Consider leaving the oldest segment alone. Addresses with no engagement for several years carry the most risk and the least value. Often the right answer is to suppress them and grow the list again through current signups.

Stop rules

Decide in advance what makes you stop: a hard bounce rate well above your normal level, any trap or blocklist notice, a complaint spike, or a wave of deferrals from one provider. Write it down before the first send so nobody argues for "just one more segment" mid-campaign.

How to confirm it's working

Your bounce and complaint rates on each stage should drift back toward your normal levels as the dead addresses get removed. Check Google Postmaster Tools for your spam rate if you send enough to Gmail, and check whether your sending IPs or domain picked up any listings on the blocklists that matter. Inbox placement for the rest of your program shouldn't change. If it does, the restart is hurting your reputation, and you should pause.

How to keep it from happening again

The real fix is to not let a list go stale. Mail people regularly enough that they remember you, and set a sunset policy: addresses that haven't engaged in a set period get a re-engagement attempt, and then stop getting mail. Yahoo's sender guidance suggests periodically sending a reconfirmation email to inactive subscribers, and AWS's guidance is not to keep mailing people who haven't engaged in 6 months or longer. If you've already hit traps, how to find and remove spam traps covers the cleanup.

When to get help

If the list is large, valuable to the business and more than a couple of years old, or you've already had a restart go wrong, it's worth planning it with someone who's done it before. Get in touch.

FAQ

Is it legal to email an old list?

It depends on where your recipients are and how they consented. Laws like CAN-SPAM, GDPR and CASL treat consent differently, and some forms of implied consent expire. Check with whoever handles compliance for you before restarting.

Should I just run the whole list through a verification service and send?

No. Verification removes invalid addresses but can't detect recycled spam traps, and it does nothing about the complaints you'll get from people who forgot you. It's a useful step before a staged restart, not a replacement for one.

How old is too old to email?

There's no official cutoff, but recycled traps are commonly reactivated after an address has bounced for about a year, and Yahoo and Google close inactive accounts after 12 to 24 months. Segments with no engagement for two years or more carry real risk.

Will switching to a new ESP or IP make it safe?

No. Receivers judge your domain as well as your IP, and the bounces and traps are in the list, not the platform. A new IP with no history plus an old list is one of the riskier combinations you can try.