Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Email Marketing › Email Fundamentals

Restarting Email to a Dormant List

How to restart email to a list nobody has mailed in a long time: rebuild the consent record, clean it, check authentication, re-permission and send in stages.
Tutorialintermediate11 min readUpdated

Why a quiet list is risky to restart

A list that is mailed every week is tested every week. Dead addresses bounce and are suppressed, people who lose interest unsubscribe, and the sending domain builds a steady pattern that mailbox providers can read. A list that goes quiet stops being tested, and everything that happens to it during the silence arrives at once on the first send back. The email bounce rate diagnosis describes the result: a segment that has not been mailed for a long time returns a burst of permanent failures, because people change jobs, abandon free mailboxes and let domains lapse.

Bounces are the visible part. The larger risk is complaints from people who no longer recognise the sender. The deliverability guide explains that complaints weigh heaviest in a domain's reputation, and that a domain silent for a long period which then mails everyone is harder to trust than one that sends steadily. Google's sender guidelines advise against sudden spikes in volume and recommend a gradual ramp, and a whole-list restart is exactly that spike.

What changed while the list was quietWhy it matters on the first sendStep that deals with it
Addresses went deadHard bounces arrive in a burstRemove bounces and carry opt-outs across
Opt-outs were scattered across old systemsPeople who asked to leave are mailed againRemove bounces and carry opt-outs across
Nobody can say how some addresses joinedThe business cannot show the people agreedRebuild the record of where addresses came from
People forgot they subscribedComplaints rather than clean unsubscribesSort the list; write the return email
DNS records, tools or the platform changedMail fails authentication or alignmentConfirm authentication still passes
The domain has no recent sending patternA sudden spike in volumeSend in stages from the strongest group

Before you start

  • Access to every system that has held the list: the email platform now in use, any older platform, the shop or booking system, the CRM and the spreadsheets people kept. The opt-outs and the consent records are usually spread across them.
  • The person who controls the domain's DNS, booked for the authentication step.
  • Whoever handles data protection, available to decide what happens to addresses whose record is missing or doubtful. The list building and consent guide explains what the record should contain; it is general guidance, not legal advice.
  • Something worth sending, and a cadence the business can keep. Restarting a list only to let it go quiet again repeats the problem, so plan the programme the list is returning to before the first stage goes out.
  • Seed addresses at the major mailbox providers and a way to read full message headers.
  • A quiet calendar: no platform move, list import or large campaign planned for the restart weeks.

If the whole marketing programme has been inherited, not only the list, the tutorial for taking over a marketing programme inventories accounts, tracking and customer data first, and its customer data step feeds straight into this tutorial.

The steps

  1. Find out why the list went quiet

    Write down why mailing stopped, because the reason shapes the return. The person who ran it left and nobody took over. The business paused marketing during a difficult year. The list came with an acquisition and was never used. Or the programme stopped because mail started landing in spam or bouncing, in which case the cause has to be found before anything is sent, using the emails going to spam diagnosis and the bounce diagnosis. Read whatever reports remain from the last sends: bounces, complaints, unsubscribes and any refusals from a provider. Note when the last send went out and to whom. The answer also becomes part of the return email, since subscribers will wonder why the business went silent and why it is writing now.

  2. Rebuild the record of where addresses came from

    For every address, try to recover the record the list building guide describes: the source, the date, the wording the person saw, the choices they made and, where double opt-in was used, the confirmation date. Old platform exports, checkout settings in the shop, form wording kept in old templates and event sign-up sheets are the usual places to look. The GDPR, as that guide summarises it, expects the organisation to be able to demonstrate that consent was given, and the UK regulator's direct marketing guidance explains when consent is needed for electronic marketing and when existing customers can be contacted about similar products, provided they were given a chance to refuse when their details were collected and in every message. Label each address with its source and one of three states: record found, record partial, no record. A bought or rented file is not part of the restart at all: suppress it and leave it out, because the ICO's guidance treats bought-in lists as a risk area, as the list building guide explains.

  3. Remove bounces and carry every old opt-out across

    Before a single send, collect every unsubscribe, complaint and hard bounce from every system that ever mailed the list, including people who asked to be removed by reply or by phone and were noted in a spreadsheet. Load them all into the suppression list of the platform you will send from, as a global suppression that applies to every campaign and flow, and make sure a suppressed address stays suppressed if it also appears in the active list. The person who opted out before the silence is the person most likely to complain when mail arrives again. Remove addresses that hard-bounced on the last sends. If you use a service that checks whether addresses still exist, treat its result as a reason to remove an address, never as evidence that the person agreed to be mailed.

  4. Confirm authentication still passes

    DNS records are edited, new tools start sending as the domain and platforms rotate keys, so authentication that worked when the list was last mailed may not work now. Check that SPF, DKIM and DMARC pass for the domain and the platform you will send from, that DKIM signs with your own domain and that the passing domain aligns with the visible From address. Confirm that marketing sends carry the one-click unsubscribe headers and a visible unsubscribe link, which Google's sender guidelines document for bulk senders, as the deliverability guide explains. The email sending domain setup checklist holds every line of this step. Send test messages to the seed addresses and read the headers before anything else goes out.

  5. Sort the list by consent record and last engagement

    Sort the addresses that remain into groups on two questions: how good is the consent record, and when did the person last do something, such as click, buy, enrol, book or log in. Opens are a weak signal, so do not rely on them. A strong group has a clear record and engaged or bought shortly before the silence. A middle group has a clear record but an old last engagement. Doubtful groups have a partial record, or a record so old the person may not remember it. A group with no record and no relationship stays suppressed unless whoever handles data protection decides otherwise. The segmentation guide explains engagement tiers; the windows are your own choice, set from the cadence subscribers were promised. Write each group's definition and size down, because the stages and the reading of each stage depend on them.

  6. Re-permission the doubtful groups

    For the doubtful groups, write a re-permission message: one plain email that says who is writing, reminds the person how they joined, asks them to confirm with a single click that they want to hear from you again, and says plainly that if they do nothing they will not be mailed again. Everyone who does not confirm is suppressed. The list building guide describes this as converting an unknown list into a small known one, and the email list hygiene SOP sends such a message once, with at most one reminder. The comparison of single and double opt-in explains why a confirmation click is strong evidence that the owner wants the mail. The message is written now and sent in the later stages, after the strong groups have re-established a steady pattern. The one-way and two-way door framework explains the asymmetry that makes this worth doing: suppressing a doubtful group can be undone, because people can rejoin through any sign-up point, while a complaint from mailing it cannot be unsent.

  7. Write the return email

    The first email to the strong groups carries the restart, so it has four jobs. Say who is writing, by a name the subscriber will recognise, and remind them how they joined. Say why the business went quiet and why it is writing now, in a sentence. Say what to expect from here: what kind of email, and how often. And make leaving easy: a visible unsubscribe link near the top as well as in the footer, and a link to the preference centre where one exists. Keep it plain, keep the sender name and reply address consistent with what the list knew, and resist a hard sell or a large discount, which tends to draw the people who will leave again at the next full-price email. A reply address that reaches a person matters here, because some subscribers will answer rather than click.

  8. Send in stages from the strongest group

    Start with the strongest group, most recently engaged first, and widen the audience stage by stage: the rest of the strong group, then the middle group, then the re-permission message to the doubtful groups. Google's sender guidelines advise against sudden spikes and recommend a gradual ramp, and the deliverability guide explains why a reactivation push reads, from a provider's side, as a change in behaviour. The size of each stage and the gap between stages are your own judgement, set from the list's size and how the previous stage read; no provider publishes a schedule. Keep everything else still while the stages run, and keep the content representative of the mail that will follow, so the reputation the restart earns applies to the programme that comes after it.

  9. Read each stage before the next

    After each stage, read hard bounces by type, complaints, unsubscribes, clicks and, for the doubtful groups, confirmations, split by group and by original source. Where the domain is verified in the provider's postmaster tools, read the spam rate there too; Google's guidelines document a threshold for it, and the site points to the source rather than repeating the figure. Compare each stage with the stages before it rather than with an outside figure. Widen the audience when the signals hold steady. Hold, and look at the source, when they worsen: a complaint rate that jumps in one group usually points to a source whose consent was weaker than the record suggested, and that source goes back to suppression or re-permission. Suppress every hard bounce at once. When the re-permission window closes, suppress everyone who did not confirm.

  10. Hand over to routine hygiene

    Once every group has been mailed or suppressed, the restart is over and the list joins the routine in the email list hygiene SOP: bounces, complaints and unsubscribes processed after each send, inactive contacts flagged and re-permissioned once a month, and a sample of consent records checked. Record what the restart did: the groups, their definitions, how many addresses were suppressed and why, and the dates. Then keep the cadence the return email promised, because the bounce diagnosis's advice applies in full: never let a segment go so long unmailed that its first send becomes a test of whether it still exists. Whether suppressing long-inactive subscribers costs more than it saves can be tested later with the inactive subscriber sunset test.

A language school's return to email (illustrative)

Illustrative example — not a real result

Wrenvesper Language School restarts its list in five stages

Wrenvesper Language School, an evening language school, stopped emailing two years ago when its only marketer left. The new coordinator finds 9,300 addresses across the old platform, the enrolment system and two spreadsheets. Before any send she suppresses 430 old unsubscribes, 520 addresses that hard-bounced on the last sends and a 650-address file a previous manager had bought. The remaining 7,700 are sorted into four groups: A, students enrolled in the year before the pause, with consent ticked at enrolment (1,900); B, website sign-ups with a double opt-in record but no enrolment (2,400); C, enquirers from open-day sheets with partial wording (1,300); and D, past students from an older system with no wording on record (2,100), mailed only after the school's data protection adviser agreed to a single re-permission message.

StageGroup and messageSentHard bouncesComplaintsUnsubscribesConfirmations
1A, most recent half, return email9509012n/a
2A, remainder, return email95021117n/a
3B, return email2,40074241n/a
4C, re-permission1,30096322230
5D, re-permission2,100260435170

The stages ran over five weeks. Group D's bounces were the highest, so the school held for a week before its reminder, which brought most of the 170 confirmations. The 400 people who confirmed in C and D joined the main list; the 2,644 who neither bounced nor confirmed were suppressed. The list the school now mails holds about 4,500 addresses, and its first regular monthly newsletter drew fewer complaints than stage 2.

Common mistakes

  • One send to everyone. The bounces, the complaints and the volume spike arrive together, on the first day.
  • Restarting before the opt-outs are found. People who left years ago are mailed again and are the likeliest to complain.
  • Assuming authentication still works. DNS and tools changed during the silence; test before sending.
  • Re-permissioning the strong groups. People with a clear record and recent engagement are lost for nothing when they do not click.
  • Mailing a bought file "just once" to ask. Bought lists stay out of the restart entirely.
  • Reading stages against an industry figure. Compare each stage with the stages before it.
  • Keeping non-responders "in case". Everyone who did not confirm is suppressed, or the re-permission meant nothing.
  • Letting the list go quiet again. Without a cadence and the hygiene routine, the next restart starts from the same place.

The fundamentals hub sets out the hygiene routine that keeps a restarted list in the state this tutorial leaves it.

Frequently asked questions

How long does a list have to go unmailed before it counts as dormant?

There is no documented figure, and the right answer depends on the cadence subscribers were promised. A useful test is practical rather than numerical: if the next send would be the first evidence of whether the addresses still exist and whether the people still remember joining, treat the list as dormant and follow the staged restart. The segmentation guide treats inactivity windows as the sender's own choice for the same reason.

Should the whole list receive a re-permission message?

Usually not. Subscribers with a clear consent record who engaged or bought shortly before the pause can be restarted with an ordinary return email, and asking them to click to stay loses good people who simply never click. Re-permission is for the doubtful groups, where the record is weak or the last engagement is old, and everyone in those groups who does not confirm is suppressed. A group with no record and no relationship stays out until whoever handles data protection decides; nothing here is legal advice.

Can we restart a list that came with an acquired business or was bought by a previous manager?

A bought or rented list should stay out entirely; the list building and consent guide explains why such files almost never show that the people agreed to hear from the buyer. A list acquired with a business is a question of what the people were told when they joined: whether they agreed to this kind of mail from an organisation that is now yours. Rebuild the record for those addresses, treat any doubt as a reason to re-permission or suppress, and ask whoever handles data protection before mailing them.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Email sender guidelines — Google Workspace Admin Help
  2. Direct marketing guidance — Information Commissioner's Office (UK)
  3. Regulation (EU) 2016/679 (GDPR) — EUR-Lex

Related