How a suppression list works
It is a separate register that sits alongside your mailing list rather than inside it. Before a campaign goes out, the platform compares the send audience against that register and silently drops anyone who appears on it. The rule applies no matter how the address arrived — a fresh import, a form fill, a spreadsheet from the sales team — which is the whole point of keeping it separate.
Four kinds of address belong there. Anyone who unsubscribed. Anyone who marked a message as spam, because a spam complaint is an unambiguous instruction to stop. Every hard bounce, since the mailbox does not exist and retrying only damages your standing. And anyone you have manually excluded — a competitor, a former client, a contact who asked by phone or in person.
Why a suppression list matters
Deleting a contact feels like the same thing and is not. Deletion removes the record of the request, so the next import from a CRM, an event spreadsheet or an old backup puts the address straight back into the sending pool. A suppression entry survives that, because it is checked at send time rather than stored on the contact.
It is also the evidence that you honoured an opt-out. Consent rules in most markets require you to act on a withdrawal and to be able to show that you did, and “we deleted them” is a weaker answer than a dated record that the address is permanently blocked.
Common mistakes with suppression lists
The most damaging is deleting instead of suppressing, and the second is keeping suppression in only one place. A business that unsubscribes someone in its email platform but keeps mailing them from a CRM sequence, a helpdesk tool or a colleague’s personal mailbox has not really stopped, and the recipient will not distinguish between systems when they reach for the junk button.
The other frequent error is treating the list as disposable during a platform migration. Suppression data is rarely included in a standard contact export, so it is exactly the file that gets left behind — and the first campaign from the new platform then reaches everyone who had asked to be left alone.
How to act on it
Export the suppression file before any migration and import it into the new system as the very first step, before a single contact is uploaded. Keep one authoritative register for the whole organisation rather than one per tool, and make sure anything that sends email — automation platform, CRM, helpdesk — checks against it.
Store the minimum needed to enforce the block, keep the date and reason so you can answer a query later, and never let a well-meaning re-import quietly overwrite it. That discipline belongs with the rest of your email marketing groundwork: unglamorous, invisible when it works, and expensive the first time it is missing.