Definition
A suppression list holds email addresses, or contact records, that are excluded from sending regardless of which list, segment or workflow they appear in. Where a mailing list says who may receive a message, the suppression list overrides it and says who never will. Most email platforms keep one automatically for unsubscribes, bounces and complaints; organisations with more than one sending tool usually also keep a global version that all of them check.
Suppression is different from deletion. A deleted contact leaves no trace, so the same address can be imported again from a spreadsheet, an event list or a CRM sync and mailed as if nothing had happened. A suppressed address stays on file precisely so that it can be recognised and blocked. The email list hygiene SOP makes that the rule: keep opted-out contacts on the suppression list indefinitely, and suppress rather than delete.
What belongs on it
- Unsubscribes. Anyone who opted out of marketing email. The FTC's CAN-SPAM guide and the UK regulator's direct marketing guidance both describe honouring opt-outs promptly; the list is how a sender keeps that promise across every future send.
- Spam complaints. People who marked a message as spam. Mailing them again harms the sender's DeliverabilityWhether sent email reaches the inbox rather than spam or rejection, decided by sender reputation. as well as ignoring a clear signal.
- Hard bounces. Addresses that do not exist or permanently reject mail. Retrying them tells mailbox providers the list is not maintained.
- Policy and legal exclusions. Contacts with no consent record, people who asked not to be contacted by any channel, legal holds, and regional exclusions.
- Sunset suppressions. Long-inactive subscribers who did not respond to a re-engagement attempt, moved to a dormant state that is excluded from marketing but kept for records.
Not every entry means the same thing. An unsubscribe from marketing does not stop a receipt or a password reset, and a sunset suppression can be reversed if the person engages again; a complaint or a do-not-contact request should not be. Recording the reason and date for each entry keeps those distinctions usable.
In practice: syncing across tools
The list is only as strong as its weakest copy. A business that sends from an email platform, a marketing automation tool, a CRM and an SMS service has four places where someone can be mailed, and an address removed in one stays live in the others unless the suppression is synced. The data operations and taxonomies guide treats this as the point where data hygiene meets legal obligation, and warns that suppression lists kept separately in each tool drift apart. Customer lists uploaded to ad platforms are part of the same picture where an objection covers them.
Inside automation, the check has to happen before every send, not only when a contact enters a workflow, because someone can unsubscribe halfway through a sequence. The automation governance guide describes one global suppression list that every workflow checks at entry and before each message, owned centrally so that bypassing it is a reviewable change. The simplest proof that it works is a seeded test address that has unsubscribed: if it receives anything, the sync is broken.
Migrations and the cost of losing it
Moving to a new email platform is when suppression lists most often disappear. The export carries the active contacts; the list of people who asked to leave is a separate file, or a status that does not map across, and it is easy to forget. The new platform then sees those people as ordinary subscribers. The email sending domain setup checklist includes carrying suppression lists across from the old platform as an explicit step for exactly this reason. The consequences arrive with the first send: complaints from people who opted out, a breach of the consent they withdrew, and damage to a new domain's reputation before it has had time to build one.
A garden-room builder restores the file it left behind
Larchwind Garden Rooms moved its newsletter to a new email platform in spring, importing 14,000 contacts from the old one. The import did not include the old platform's suppression file of about 2,300 unsubscribes and complaints, and the CRM, which had never synced suppressions, still held most of those people as contacts. The launch email for a new range went to all 14,000. Within two days it drew 41 spam complaints, against fewer than 5 on a typical send, and several replies from people who had unsubscribed years earlier. The team exported the old file, loaded it as a global suppression list in the new platform, set the CRM to read suppression status from it nightly, and added a seeded unsubscribed address to every send.
Related terms
Every opt-out counted in Unsubscribe RateShare of delivered emails that led the recipient to opt out. and every complaint counted in Spam Complaint RateShare of delivered emails that recipients marked as spam. should end up as an entry on the suppression list, and each Hard BounceAn email rejected permanently by the receiving server, usually because the address does not exist or the domain cannot receive mail. should be added automatically. Together they protect DeliverabilityWhether sent email reaches the inbox rather than spam or rejection, decided by sender reputation., which depends on not mailing people who do not want the mail or cannot receive it. The email deliverability guide sets suppression alongside engagement tiers as the response to an inactive list, and the inactive subscriber sunset test measures whether suppressing non-responders costs more revenue than it saves in complaints.
Common confusions
- A suppression list is not the unsubscribe list. Unsubscribes are one input; bounces, complaints and policy exclusions are others.
- Removing a contact is not suppressing it. Deletion lets the address back in at the next import.
- The platform's own list is not enough when other tools send too.
- Checking at entry is not checking before send. People opt out mid-sequence.
- Suppressed is not always permanent. A sunset suppression can be lifted if the person returns; an opt-out lasts until they actively opt back in.
