List hygiene should maintain expectations, not punish quiet subscribers

Silence is an observation with several explanations

A subscriber may stop opening because tracking is blocked, messages are filtered, cadence is wrong, the promised task is complete, content is temporarily irrelevant, the address is abandoned, or attention moved elsewhere. An inactivity label does not identify which explanation is true. The subscriber-state stewardship model keeps delivery status, permission evidence, declared preference, observed activity, lifecycle context, and suppression as separate fields with their own timestamps and confidence. Do not turn quiet into disloyal, low value, or safe to pressure. Opens are particularly incomplete because image loading and privacy features distort them. Use the narrowest evidence available and preserve a neutral state when the system cannot know.

Evidence: Google Gmail Help; Messaging, Malware and Mobile Anti-Abuse Working Group

Hygiene begins before a campaign with acquisition quality

Document signup source, explanation, confirmation where appropriate, address validation, sender identity, expected cadence, and consent or permission record. Remove bot submissions, obvious syntax failures, hard bounces, complaints, and valid opt-outs through governed processes. Purchased or poorly explained addresses create reputation and trust problems that later cleaning cannot legitimize. Gmail, Yahoo, and M3AAWG publish sender or best-practice expectations that emphasize permission, spam prevention, and responsible lists. Those sources do not create one universal legal rule. A clean database is not merely one with fewer rows; it is one where the sender can reconstruct why each active stream is allowed and what the recipient expects.

Evidence: Google Gmail Help; Yahoo

Separate technical invalidity from editorial disengagement

A permanent SMTP recipient failure has different evidence from no click in ninety days. Temporary deferrals need provider-aware retry and investigation, not immediate deletion. Complaints and opt-outs require suppression under applicable rules. Lack of recent action may justify reducing frequency or asking for preferences, but it should not overwrite the original record or provoke increasingly urgent mail. Track accepted, deferred, bounced, complained, unsubscribed, clicked, replied, resource-used, and self-declared preference separately. This separation lets operators stop invalid traffic without pretending an engaged subscriber is defined by a tracking pixel. It also prevents a deliverability fault from being misdiagnosed as weak content.

Evidence: Yahoo; Federal Trade Commission

A re-engagement message is a choice point, not a trick

When continued contact is still within the explained relationship, a bounded message can remind the recipient who sends, why the address is present, what the publication offers now, how to change topic or frequency, and how to stop. Avoid false deadlines, guilt, alarming subjects, disguised account notices, or incentives that reward meaningless clicks. The primary action may be choose a preference rather than prove engagement. A recipient who does nothing should reach a documented endpoint instead of entering an endless rescue series. Commercial-message duties and provider unsubscribe rules still apply. A positive click cannot retroactively fix unclear acquisition, and repermission claims require jurisdiction-specific review.

Evidence: Google Gmail Help; Federal Trade Commission

Sunset, suppress, and delete are different controls

Sunsetting stops or reduces a particular campaign stream under a defined rule. Suppression preserves enough information to prevent prohibited re-addition. Deletion removes data that is no longer needed, subject to legitimate obligations and technical design. These actions should not be used interchangeably. Define which systems receive the state, how queued jobs are cancelled, what essential service messages remain, how identity merges behave, and when retained suppression data is reviewed. A dormant record should not remain forever merely because storage is inexpensive. Conversely, deleting the only opt-out evidence and later reimporting the address can harm the recipient. Assign owners and retention reasoning to each state transition.

Evidence: Yahoo; Messaging, Malware and Mobile Anti-Abuse Working Group

Maintain the relationship with a state ledger

The next action is to map one mailing stream into states for active expected, reduced-frequency, preference requested, technically invalid, complained, opted out, sunset, suppressed, and deletion review. For each transition, state evidence, owner, recipient effect, propagation, and rollback or correction. Stop current sending where permission, identity, or suppression cannot be reconstructed. Limits remain: activity signals are incomplete, mailbox algorithms are private, laws differ, and a retention model needs local privacy and legal review. Reassess after provider, cadence, signup, tracking, product-lifecycle, or message-purpose changes. Good hygiene protects choice and system integrity; it is not a tactic for making a dashboard rate look larger by discarding inconvenient people.