How to Clean a Newsletter List Without Losing Readers

Key takeaways

• Google asks bulk senders to keep the spam rate reported in Postmaster Tools below 0.10% and never let it reach 0.30%.
• Readers who stopped opening are the ones most likely to report a newsletter as spam, and they lower the share of your list that engages.
• A good cleanup asks quiet readers once whether they want to stay, and keeps them on the list instead of deleting them.
• SendHQ does this automatically: after 6 unopened issues and 90 quiet days by default, one check-in email, then dormant after 7 days without an answer.
• Opens undercount Apple Mail readers, so cleanup should never remove anyone without asking first.

Why inactive readers hurt delivery

Mailbox providers decide where your newsletter lands partly from how people respond to it. Google's sender guidelines ask senders to keep the spam rate shown in Postmaster Tools below 0.10%, and to avoid ever reaching 0.30%. Senders of more than 5,000 messages a day to Gmail must also support one-click unsubscribe.

Readers who signed up long ago and stopped opening are the ones most likely to press "Report spam" instead of looking for the unsubscribe link. They also add nothing: an issue sent to 12,000 people where 4,000 engage looks worse to a mailbox provider than the same issue sent to the 8,000 who still want it.

What a fair cleanup looks like

1. Define quiet carefully. Use several issues in a row with no open or click and a long quiet period, not one missed issue.
2. Ask before you stop. Send one short email asking whether the reader still wants your newsletter, with one clear button to stay.
3. Give them time. A week is enough for most people to see the message.
4. Stop sending, do not delete. Keep the address and its consent record, so a returning reader can come back and you keep your history.
5. Let them return. If a quiet reader opens or clicks an older issue later, they should be active again without signing up twice.

How SendHQ does it

SendHQ runs this for you. Cleanup is on by default, checks every hour, and uses the settings below, which you can change in Newsletter settings or through the API.

The check-in email has a button to stay subscribed. The keep page needs a button press, not just a visit, so a link scanner that follows every link cannot keep the whole list subscribed by accident. Readers who do not answer become dormant: they stay on your list and in your exports, they are not sent issues, and any later open or click makes them active again. Details are on the list cleanup page.

The Apple Mail problem

Apple Mail Privacy Protection loads images on its own, so honest open tracking filters those loads out, as explained in why newsletter open rates are inflated. The catch is that a reader who reads only in Apple Mail and never clicks can look quiet. Asking first is what keeps those readers: they press the button and stay. A cleanup that removes readers on open data alone would drop them without warning.

What else protects the list

• Hard bounces, complaints and unsubscribes are suppressed for every future send, including re-imports of the same addresses.
• Every newsletter email carries a visible unsubscribe link and one-click unsubscribe headers.
• Signup forms use double opt-in, so an address with a typo never becomes an active reader.
• New workspaces ramp from 100 to 50,000 emails a day, and a sender is paused when 7-day complaints reach 0.1% or hard bounces reach 10%. See the deliverability rules.

Doing your own win-back first

If you would rather send a win-back issue before cleanup asks, build a segment of readers with several sends in a row and no open, send them something worth reading, and see who clicks. The check-in emails count toward your monthly allowance like any other email. Starter is $19 a month for 50,000 emails and Scale is $39 a month for 200,000, with no charge per subscriber.

Sources and dates

Google's sender guidelines were read on the published date. SendHQ details describe the product as of the updated date above.

• Gmail email sender guidelines (Google Workspace Admin Help)
• SendHQ list cleanup
• SendHQ deliverability rules
• SendHQ for newsletters

Questions teams ask