What is a suppression list and how should I use one?

Suppression lists are the universal "do not send" list maintained by every reputable ESP. Once an address is on the suppression list, the ESP refuses to send any campaign to it, regardless of which segment, audience, or list contains it. This is a deliverability safeguard, not just a compliance feature.

What goes onto a suppression list automatically

• Hard-bounced addresses. After one hard bounce (or your configured threshold).
• Unsubscribed users. When they click the unsubscribe link.
• Complaint reports. Addresses that hit "Mark as spam" on your messages and the complaint reaches your ESP via feedback loops.
• Manual additions. Addresses you explicitly add, such as employees who do not want marketing, known abusers, or journalists who asked to be removed.

Why suppression matters

Without suppression, you might re-add a bounced address to a new campaign by accident. A fresh import overlaps with old data, or an automation pulls from a stale source. The suppression list is the safety net that prevents bounces from accumulating across campaigns.

Compliance angle: unsubscribed addresses MUST NOT receive further marketing under CAN-SPAM (US), CASL (Canada), or GDPR (EU). The suppression list is your enforcement mechanism. Without it, you are one accidental re-import away from regulatory exposure.

How to manage the suppression list

• Review periodically. Most ESPs let you export the suppression list. Quarterly review surfaces any erroneous entries (people accidentally suppressed by a bug, etc.).
• Add proactively. When someone emails you asking to be removed, add them via the suppression interface immediately. Do not wait for them to find the unsubscribe link on the next campaign.
• Coordinate across ESPs. If you send transactional from one ESP and marketing from another, an unsubscribe should propagate to both. Most ESPs do not auto-share suppression. You need to handle this manually or via integration.

Suppression vs. verification

They solve different problems:

• Verification removes addresses that are technically bad (do not exist, disposable, spam traps) BEFORE you send.
• Suppression prevents you from sending to addresses that have already proven problematic, either through bouncing on a previous send or via explicit unsubscribe.

Both layers matter. Verification catches new bad addresses entering your list. Suppression remembers old ones across time.