Email list hygiene: suppress, sunset, or remove
Build a list-hygiene policy for invalid, inactive, risky, and unengaged recipients without confusing validation with consent.
A clean list is the only list worth sending to. Spamtraps, dead addresses, and the chronically unengaged drag your reputation down faster than any single bad campaign. The fix isn't a one-time cleanup — it's a permanent discipline.
Validate at the source
- Syntax check — RFC 5321 regex, character set, length.
- MX lookup — domain has mail servers; if not, reject the signup.
- Optional SMTP probe — connect to MX, RCPT TO, read response. High accuracy but slow and detectable.
- Confirmed opt-in (COI) — send a verification link before the address joins the list. Highest quality, ~10% friction.
The four suppression buckets
| Bucket | Source | Reactivation |
|---|---|---|
| Hard bounce | 5xx SMTP response | Never |
| Complaint | FBL, "Report Spam" button | Never |
| Unsubscribe | User clicked unsubscribe | Only on explicit re-permission |
| Sunset | No engagement in 90–180 days | Re-engagement campaign possible |
Sunsetting unengaged subscribers
Subscribers who don't open, click, or otherwise engage for months drag down your engagement rate. Receiver filters watch this metric closely. The discipline: identify the unengaged, run one re-engagement campaign, then suppress.
A 90-day sunset workflow
- 01
Define engagement
Open OR click within the window. (Apple Mail Privacy Protection has degraded open tracking — clicks alone are more reliable for iOS-heavy lists.)
- 02
Segment the unengaged
Subscribers with zero engagement in 90 days. For high-volume senders, 60 days is more aggressive; for newsletters, 180 is acceptable.
- 03
Send a re-engagement campaign
One message: "We've noticed you haven't opened in a while. Click here to stay subscribed." Anyone who clicks rejoins. Anyone who doesn't moves to suppression.
- 04
Suppress non-responders
Move to the sunset suppression bucket. Don't delete — keep the record so you can prove permission history if challenged.
- 05
Repeat quarterly
List decay is continuous. Run sunset campaigns on a calendar, not in response to deliverability problems.
Spamtraps
Receivers and blacklist operators seed dead addresses into the wild. Hitting one is direct evidence you're sending to a list you shouldn't have. Two flavors:
| Type | How it gets in your list |
|---|---|
| Pristine traps | Never used by a real person — only via scraping |
| Recycled traps | Was a real address; abandoned for 12+ months; reactivated by provider |
| Typo traps | Common typos like gmial.com; catches sloppy validation |
Acquisition channels by quality
| Channel | Quality | Risk |
|---|---|---|
| Confirmed opt-in (COI) | Excellent | Low |
| Single opt-in with validation | Good | Medium |
| Single opt-in without validation | Mediocre | High — typos, bots |
| Pre-checked checkbox at checkout | Bad | Very high (and illegal in EU) |
| Co-registration (third-party) | Bad | Very high |
| Purchased lists | Toxic | Catastrophic |
Frequently asked questions
| Evidence | Default decision | Review before changing |
|---|---|---|
| Permanent invalid result | Suppress | Confirm the durable reason code |
| Risky or catch-all | Segment | Consent, source, value, and bounce history |
| Long-term inactivity | Sunset or repermission | Message type and recipient expectation |
| Unknown validation | Retry or hold | Provider limits and temporary failures |
Use the email validator for mailbox evidence and the validation status guide for policy mapping. Neither replaces consent or suppression history.
Apply the findings from List hygiene: suppress, sunset, or remove with the deliverability testing workflow, then use the relevant WillItInbox product workflow to collect current evidence.
Last updated June 13, 2026.
Sources reviewed
- Email sender guidelines(official)
Factual review: June 13, 2026 by WillItInbox Editorial.
Keep reading