A dormant email list — a collection of contacts who have not received email from the programme for 6 months or more — represents both commercial opportunity (contacts who previously opted in and may have residual value) and deliverability risk (contacts who have forgotten the sender, addresses that have become invalid or been repurposed as spam traps, and complaint rates that can be 5-10x higher than an actively managed list). Reactivating a dormant list safely requires specific validation, infrastructure preparation, and sequencing practices that differ significantly from standard campaign deployment.

6 months
Minimum dormancy period that requires the full reactivation protocol
Verify first
Full list validation before any reactivation send — non-negotiable
5-15%
Typical valid re-engageable contacts recovered from a 12-month dormant list
Separate IP
Reactivation sends should use separate IPs from production sending

The Risks of Reactivating a Dormant List

Dormant lists carry three categories of risk that increase with the duration of dormancy:

Address invalidity: Email addresses become invalid at 15-35% per year (higher for B2B lists). A list that has not been used for 18 months may have 25-50% invalid addresses generating hard bounces on the first reactivation send. At a 30% hard bounce rate on a 100,000-contact dormant list, 30,000 hard bounce events in a single campaign will generate SNDS IP status changes and Postmaster Tools domain reputation declines that take weeks to recover from.

Spam trap exposure: ISPs recycle abandoned email accounts as spam traps after 12-24 months of inactivity. A dormant list that contained 500 accounts that were abandoned 18 months ago may now contain 50-100 recycled spam traps. Sending to recycled spam traps generates immediate negative reputation signals at the ISPs whose traps were hit.

Complaint spikes: Contacts who have not received email from the programme for 12+ months frequently do not recognise the sender when the reactivation email arrives. "Who is this? I never signed up for this" is the mental model that leads to spam marking rather than using the unsubscribe link. A reactivation send to an unvalidated dormant list typically generates 5-20x the complaint rate of the same programme's standard campaigns.

These risks are manageable — they do not make reactivation impossible or inadvisable — but they require specific mitigation protocols before the reactivation send begins.

Pre-Reactivation Validation: The Non-Negotiable Step

Full list validation before any reactivation send is the single most impactful risk mitigation available. Run the dormant list through a commercial email validation service (NeverBounce, ZeroBounce, Kickbox) before sending a single message. The validation removes invalid addresses, disposable addresses, known spam trap addresses, and high-risk addresses before they can generate the bounce, complaint, and trap signals that damage reputation.

Typical validation results for dormant lists by age:

List dormancy periodExpected invalid rateExpected high-risk rateSendable fraction
6-9 months dormant8-15%3-8%77-89%
9-12 months dormant12-22%5-12%66-83%
12-18 months dormant20-35%8-18%47-72%
18-24 months dormant28-45%12-25%30-60%
24+ months dormant35-60%15-35%5-50%

After validation, segment the remaining sendable contacts by original engagement history (contacts who previously opened or clicked vs contacts who never engaged). The previously-engaged segment has a much higher probability of responding positively to reactivation than the never-engaged segment — prioritise the engaged segment in the reactivation sequence and treat the never-engaged segment with much lower volume and higher caution.

Infrastructure Preparation Before Sending

Reactivation sends should use separate sending infrastructure from the production active-list sends. The complaint and bounce signals generated by reactivation — even a well-managed reactivation — will be higher than the programme's baseline. Using separate IPs and potentially a separate subdomain for reactivation isolates these elevated signals from the production infrastructure's reputation.

The infrastructure setup for reactivation: (1) Configure a dedicated "reactivation" VMTA in PowerMTA with a separate IP address or a quarantined subset of the production IP pool. (2) Use a subdomain for the reactivation DKIM signing — reactivate.brand.com — so Postmaster Tools tracks the reactivation domain's reputation independently. (3) Set the reactivation VMTA's max-smtp-out at 50% of normal production values (more conservative rate limits since the list quality is lower than normal production). (4) Set the reactivation queue's priority at lower than production sends — if the production list experiences any issues during the reactivation period, production delivery takes precedence.

The Reactivation Sequence: 3-Email Protocol

The reactivation sequence has three emails sent over 2-3 weeks. Each email serves a distinct purpose in the reactivation funnel:

Email 1 — Re-introduction (Day 1): The first reactivation email re-establishes the sender identity and the relationship context. Subject: something that clearly identifies the sender and the original relationship — "We've missed you at [Brand]" or "Reconnecting from [Brand] — you signed up in [Year]." Body: a clear explanation of who the sender is, why the contact is receiving this email (they opted in previously), what the programme offers, and why they should want to continue receiving it. Include a prominent unsubscribe link. Do NOT lead with a promotional offer on the first reactivation email — lead with relationship re-establishment. Send to 10-15% of the validated sendable list (a test cohort) and monitor complaint and bounce rates for 48 hours before sending to the remainder.

Email 2 — Value delivery (Day 7-10): For contacts who opened Email 1 without unsubscribing, send a second email that delivers genuine value — the programme's best recent content, a useful resource, or a genuinely compelling offer. This email confirms for the recipient that re-engaging with the programme was the right decision. Subject: content-forward, not promotional.

Email 3 — Final re-engagement CTA (Day 14-21): For contacts who have received but not engaged with Emails 1 and 2, send a final re-engagement email with an explicit "Are you still interested?" CTA. Make the opt-out easy and explicit ("Not interested? Click here to be removed"). Contacts who neither engage nor unsubscribe after all three emails should be permanently suppressed — they are either unreachable, disinterested, or potential complaint risks.

Segmenting by Last Engagement Date

Not all dormant contacts carry equal reactivation risk. Contacts who last engaged 6 months ago are much more likely to respond positively to reactivation than contacts who last engaged 24 months ago. Segmenting the dormant list by last engagement date and applying different reactivation approaches to each segment improves overall reactivation success rate and reduces reputation damage from the highest-risk segments.

The segmentation tiers: Tier 1 (6-9 months dormant) — these are the highest-probability reactivation targets; treat them nearly like a normal re-engagement campaign with moderate caution. Tier 2 (9-15 months dormant) — higher bounce risk; validate thoroughly and send at lower volume per day with more conservative rate limits. Tier 3 (15-24 months dormant) — significant bounce and trap risk; validate and send only to the previously-engaged cohort, suppressing the never-engaged cohort entirely. Tier 4 (24+ months dormant) — very high risk; consider whether the expected commercial return from reactivation justifies the reputation risk, given that 35-60% of the list may be invalid and complaint rates from the remainder may be very high.

Content Strategy for Reactivation Emails

Reactivation email content must address the primary reason dormant contacts fail to re-engage: they do not remember who the sender is or why they signed up. The reactivation content strategy centres on recognition, not promotion.

The recognition elements that reduce complaint rates: a clear, prominent From name that matches the original subscription experience, subject lines that reference the original relationship context rather than a promotional hook, opening copy that immediately explains who is sending and why, and a body that reminds the contact of the value they originally found in the programme. Contacts who successfully re-engage with recognition-focused reactivation content have dramatically lower subsequent complaint rates than contacts acquired through promotional reactivation — because the recognition-first approach selects for contacts with genuine residual interest rather than contacts who respond to incentives.

What to avoid in reactivation content: subject lines that could trigger "who is this?" confusion (no sender identity in the subject), heavy promotional content on the first reactivation touch (promoting to contacts who don't yet remember you generates high complaint rates), and urgency-based CTAs that feel manipulative to contacts who are already ambivalent about the programme.

Monitoring During Reactivation

Reactivation monitoring requires more intensive real-time attention than standard campaign monitoring because the reputation signals move faster and the thresholds for intervention are lower. Check Postmaster Tools and SNDS after every reactivation send batch — not daily, but within 4-6 hours of each batch completing. If the reactivation VMTA's spam rate exceeds 0.08% or any IP transitions to Yellow SNDS status, pause all further reactivation sends immediately and investigate before resuming.

The reactivation campaign kill switch: a clear, pre-defined threshold at which the entire reactivation programme is paused. A reasonable kill switch: Gmail domain spam rate for the reactivation domain above 0.10% on any single day, OR any reactivation IP at Yellow or Red SNDS status, OR hard bounce rate above 3% for any send batch. Any of these thresholds triggering means the current approach is not working and the segmentation, validation, or infrastructure needs adjustment before proceeding.

After Reactivation: Ongoing List Management

The contacts who successfully re-engage through the reactivation sequence — who open, click, or explicitly confirm continued interest — can be graduated back to the programme's standard active list with the standard sending cadence. The contacts who did not engage or unsubscribe after all three reactivation emails should be permanently suppressed, not returned to any active or dormant list for future retry.

The lesson the reactivation exercise teaches about ongoing list management: every contact in the active list is on a decay curve from their initial engagement level. Without active maintenance — engagement-based suppression triggers, re-engagement sequences before the contacts become dormant, regular list quality audits — the active list gradually accumulates the conditions that make reactivation necessary. Building the list management practices that prevent contacts from reaching the "requires reactivation" state is the long-term investment that eliminates the need for expensive and reputation-risky reactivation campaigns. Treat the reactivation as a one-time cleanup; implement the ongoing practices that prevent the cleanup from being needed again; and the list will remain actively deliverable without periodic emergency reactivation cycles.

The ROI of Responsible Reactivation

A successful reactivation programme recovers 5-20% of the dormant list as genuinely re-engaged contacts. On a 100,000-contact dormant list, that is 5,000-20,000 contacts returned to active status at the cost of the validation fee (€300-800 for a 100K list) plus the reactivation campaign production costs. If those recovered contacts generate the programme's average email revenue attribution (say €0.03/email delivered × 12 annual sends × €36/year per contact), recovering 10,000 contacts returns €360,000 in annual email revenue from a programme that had been generating zero. Even with conservative recovery rates, the reactivation ROI is typically positive if the dormant list has genuine historical commercial value.

The caveat: reactivation is only ROI-positive if it does not damage the production programme's reputation in the process. The infrastructure separation, validation, conservative volume ramp, and monitoring protocol this guide documents are the protection that keeps the reactivation experiment's downside risk (reputation damage to the production programme) from outweighing its upside potential (recovered contacts and revenue). Implement the protocol correctly; monitor with the appropriate intensity; and dormant list reactivation will be a reliable commercial recovery tool rather than an infrastructure risk that is avoided out of appropriate caution.

List reactivation is the discipline of recovering value from existing infrastructure and relationships rather than building from zero. Done correctly — with validation, separate infrastructure, a recognition-forward content approach, and intensive monitoring — it recovers genuine commercial value safely. Done incorrectly — without validation, using production infrastructure, with promotional-first content — it generates the reputation damage that takes months to recover from. Follow the protocol; monitor closely; and the dormant list's potential will be realised without sacrificing the active programme's deliverability foundation.

Every dormant contact was once an active, opted-in subscriber who found value in what the programme offered. The reactivation protocol is designed to identify which of those contacts still have that potential value — and to recover them into the active programme without disturbing the reputation that serves the contacts who never went dormant. Validate thoroughly; sequence carefully; monitor relentlessly; and the reactivation will be the precision instrument it needs to be to succeed commercially while protecting the infrastructure it uses.

Reactivation done right is a net positive: commercial value recovered, relationship re-established, infrastructure protected. That is the standard to hold it to — and the protocol in this guide is what achieves it.

H
Henrik Larsen

Deliverability Manager at Cloud Server for Email. Specialising in email deliverability, infrastructure architecture, and high-volume sending operations.