How to Run a Re-Permission Email Campaign (Safely)

Learning how to run a re-permission email campaign is really learning how to make your riskiest send safely. You are about to email people who have not heard from you in months or years, and a stale list is the fastest way to a spike in spam complaints, a wave of hard bounces, and a sending reputation that takes weeks to rebuild.

Done carefully, a re-permission campaign trims a dead list down to the people who still want your mail, and protects the deliverability of everyone you email afterward. The core idea is simple: treat it as a controlled experiment, not a single blast. Send to your best contacts first, from a dedicated sending subdomain, in small batches you can stop the moment the numbers turn.

The short answer#

A re-permission (or re-opt-in) campaign asks an old list to confirm they still want your email. Run it in this order: authenticate the sending domain with SPF, DKIM and DMARC; move the send to a dedicated subdomain so a bad reaction cannot damage your primary domain; sort the list by engagement and email your most recently active contacts first; then send in small batches, reading the response to each one before releasing the next.

Set an abort condition before you start. A spam-complaint rate creeping toward 0.3%, or a bounce rate above a few percent, means stop. When the campaign ends, keep only the people who re-confirmed and delete the rest. That deletion is the point: a smaller list that engages beats a large one that gets you filtered.

What a re-permission campaign is — and when you need one#

A re-permission campaign is a deliberate email, sometimes a short series, that asks dormant subscribers to actively confirm they still want to hear from you. Everyone who clicks "yes" stays; everyone who ignores it is removed. It is also called a re-opt-in or reconfirmation campaign.

You need one when you are about to email a list you have not touched in a long time. Is it safe to email a list you haven't used in a year? Not as-is. Addresses decay: people change jobs, abandon inboxes, and forget they ever signed up. Some of those old addresses have since become spam traps — addresses that mailbox providers and blocklist operators use to catch senders mailing stale lists. Hitting a few can be enough to damage your reputation, which is why M3AAWG publishes guidance specifically for senders who have hit one.

• You are restarting a newsletter or product that has been quiet for six months or more.
• You inherited or merged a list and are unsure when or how each contact last engaged.
• Your open and click rates have collapsed while complaints or bounces are rising.
• You are moving to a new sending platform and want to start from a clean, confirmed list.

Before you start: the pre-flight checks#

Three things must be true before the first email goes out. Skip them and the campaign becomes the very reputation problem it was meant to prevent.

• Authentication is live. SPF, DKIM and DMARC must be set up and passing for the domain you send from. As of 2026, Gmail, Yahoo and Microsoft all require SPF, DKIM and DMARC from senders above roughly 5,000 messages a day, and a re-permission send to an old list often crosses that line.
• You have a dedicated subdomain. Send from something like news.yourdomain.com, not your primary domain. A subdomain carries its own sending reputation, so if the campaign goes badly your main domain's mail — invoices, replies, password resets — keeps landing.
• One-click unsubscribe works. Marketing mail to Gmail, Yahoo and Apple must support one-click unsubscribe (the List-Unsubscribe-Post header defined in RFC 8058) and show a visible unsubscribe link. A re-permission email is marketing mail; it needs both.
• You can measure per batch. Connect Google Postmaster Tools, plus the Yahoo and Microsoft equivalents, before you send. Without them you cannot see your complaint rate, and you are flying blind on the one number that decides whether to keep going.

How to run the campaign, step by step#

Work through these in order. The sequence is what keeps the risk bounded: your best contacts and smallest batches go first, so early signals to the inbox providers are positive and any problem shows up while it is still small.

1. 1

   Segment by engagement

   Sort the list by last activity. Anyone who opened or clicked in the last few months goes in the first batch. The truly cold addresses — the ones most likely to be traps or complainers — go last, or not at all. Emailing your best segment first builds positive history before the harder addresses arrive.

2. 2

   Write a clear re-opt-in email

   Say who you are, why they are getting this, and give exactly one thing to do: confirm. Remind them where they signed up and roughly when. Make the confirm a single obvious button, and keep a visible one-click unsubscribe alongside it. The structure is laid out in the next section.

3. 3

   Warm the subdomain first

   If the subdomain is new, do not open with your largest batch. Send low volumes to your most engaged contacts over several days so the subdomain builds a sending history before harder addresses arrive. A brand-new subdomain sending thousands of messages on day one looks exactly like a spammer.

4. 4

   Send in small, stoppable batches

   Split each engagement tier into batches small enough that one bad batch cannot wreck the whole send — a few hundred to a few thousand, scaled to your normal volume. Send one, wait, read the numbers, release the next. Batching a re-permission send is what turns a single high-risk blast into a series of low-risk experiments.

5. 5

   Read the numbers before the next batch

   After each batch, check the delivered rate, bounce rate, spam-complaint rate, and how many people re-confirmed. Rising complaints or bounces mean the next, colder tier will be worse — stop, do not push through. Healthy numbers mean you may proceed to the next batch.

6. 6

   Delete the non-responders

   When the campaign closes, keep everyone who re-confirmed and remove everyone who did not — including people who opened but never clicked confirm. This is the hard part and the whole point. The addresses you delete were the ones dragging your deliverability down.

What a re-opt-in email should contain#

The email itself is short and single-purpose. Every extra ask lowers the confirm rate, so cut anything that is not the reminder, the confirm, and the consequence. Here is the structure that reconfirms the most people without tripping filters.

Platform and inbox-provider differences#

Your email service provider handles the sending mechanics, but the rules that decide whether the mail lands come from the inbox providers. The requirements below are the ones that bite a re-permission send hardest, verified against each provider's own guidance as of 2026 — always re-check the live page before you rely on a number.

How the batched send flows#

The picture below is the whole method at a glance: the list is sorted warmest-first, each tier is broken into small batches, and every batch passes through a checkpoint that can stop the campaign before the next one goes out.

What to do when it doesn't work#

A re-permission campaign fails in a handful of predictable ways. Match your symptom to the table, and in almost every case the fix is to stop, narrow the audience, and slow down rather than push more volume through.

A faster way — and where AI Emaily honestly fits#

A re-permission campaign is a sending job, and AI Emaily does not send it. We are a receiving-side email client, not an email service provider, a mail-merge tool, or a deliverability platform — we do not blast a list, warm a subdomain, or read your Postmaster Tools spam rate. For the send itself, use your ESP; that is the right tool, and this method works with any of them.

Where AI Emaily fits is the wave that comes back. A re-permission send generates real inbound — confirmations, "yes, keep me," the occasional "who are you," unsubscribe-by-reply, and out-of-office — all landing in the mailbox you actually read. AI Emaily triages that inbound, drafts replies in your voice from a context brain you set, and its spam protection flags anything that looks like a phishing reply, with approve-before-send, undo, and a full audit trail. We build AI Emaily, and it comes with a 7-day free trial on the Pro and Autopilot plans. That is the honest scope: we handle the responses, not the campaign.