Skip to content
All articles

Guides · 6 November 2026 · 7 min read

How an email suppression list works

Rampsend team

Stop before it costs you

A suppression list is the quiet safety net behind every healthy sending programme. It is a list of addresses you must not send to, checked automatically before each message goes out. When it works, you never think about it. When it's missing or incomplete, you keep emailing dead mailboxes and people who asked you to stop, and mailbox providers notice long before you do.

What a suppression list is

Your contact list says who you could email. Your suppression list says who you must not, whatever list, segment or API call they turn up in. The distinction matters because addresses enter your systems from many places: a signup form, a CSV import, a CRM sync, an order record, an AI agent adding a contact. If suppression lived inside one list, a re-import or a new integration would bring blocked addresses straight back.

So a suppression list sits in front of sending, not alongside your lists. Every recipient of every message is checked against it at send time. If there's a match, the message to that recipient is skipped.

What goes on it

Three events should add an address automatically.

Hard bounces

A hard bounce is a permanent delivery failure: the mailbox doesn't exist, the domain doesn't exist or doesn't accept mail. The receiving server says so in the SMTP response, typically with a 5xx status. Nothing you do will make the next attempt succeed, so the address should be suppressed after the first hard bounce.

Repeatedly sending to addresses that don't exist is one of the clearest signals of a poorly maintained list. Spam filters treat high bounce rates as a sign that a sender bought, scraped or neglected its list.

Spam complaints

When a recipient clicks "report spam", many mailbox providers send a complaint back to the sender through a feedback loop. That person has told you, in the strongest way available, that they don't want your mail. Suppress them immediately and permanently for marketing.

Complaints weigh heavily. The Gmail and Yahoo sender requirements set a ceiling of 0.3% for bulk senders, and sending again to someone who already complained is the fastest way to add more.

Unsubscribes

An unsubscribe is a request, often a legal requirement to honour, and it should be processed without delay. With RFC 8058 one-click unsubscribe, a mail client can send the request on the recipient's behalf from a button next to your From name. On Rampsend, unsubscribe_header: true adds those headers, and the unsubscribes they generate are suppressed automatically.

EventWhy it's suppressedTypical scope
Hard bounceThe address can't receive mailEverything you send
Spam complaintThe person reported your mail as unwantedEverything you send, or at least all marketing
UnsubscribeThe person asked to stop receiving this kind of mailMarketing; transactional mail they need may continue
Manual additionA request by email or support ticket, a legal request, a known bad addressWhatever you decide

How soft bounces fit in

A soft bounce is a temporary failure: the mailbox is full, the receiving server is busy, the message was deferred, or it was too large. The receiving server typically answers with a 4xx status, and delivery is retried for a while before the attempt is abandoned.

One soft bounce shouldn't suppress anyone; that would remove real people whose inbox was briefly full. But a soft bounce that repeats across many sends usually means the mailbox has been abandoned. A sensible policy:

  • Retry deferrals automatically for a period, which mail servers do on their own.
  • Count consecutive soft bounces per address across separate sends.
  • Suppress, or at least stop sending marketing to, an address after a run of soft bounces over several weeks.
  • Reset the count when a message is delivered.

Also look at the pattern across your list, not just per address. A sudden wave of soft bounces from one provider often means that provider is throttling you because of reputation, not that thousands of mailboxes filled up at once. Bounce and complaint rates goes into how to read those signals.

Global and account-level lists

Suppression often works at more than one level.

An account or workspace list holds addresses that bounced, complained or unsubscribed from your mail. It's yours: you can see it, export it and add to it, for example when someone asks by reply to be removed.

A global list is maintained by the sending platform across all its senders, for addresses known to be undeliverable. An address that hard-bounced for many senders is very unlikely to work for you, and blocking it protects the shared infrastructure everyone sends through.

Rampsend keeps both: a global suppression list and a list per workspace. Both are checked on every send, from the API, the dashboard or an AI assistant using the MCP server.

Why sending to suppressed addresses hurts

It can be tempting to "try once more", especially with a large old list or an address that belongs to a valuable customer. The cost is rarely worth it.

  • Your bounce rate rises. Mailbox providers judge your sending by its outcomes. Mail to non-existent mailboxes says the list isn't maintained.
  • Your complaint rate rises. Someone who complained once is likely to complain again, and complaints are counted against your domain.
  • Spam traps. Some abandoned addresses are eventually recycled as traps that exist only to catch senders who don't remove dead addresses. Hitting them can get you blocklisted.
  • The damage is shared. Reputation belongs to your domain and sending IPs, not to one campaign. Poor results on a re-sent old segment can push your password resets and receipts into spam.
  • Legal exposure. Emailing someone who unsubscribed from marketing can breach CAN-SPAM in the US and consent rules in the EU and UK.

There's also a direct cost: on most platforms you pay for every message you attempt, deliverable or not.

How Rampsend handles suppression

On Rampsend, the safety net is on by default:

  • Hard bounces, complaints and unsubscribes are suppressed automatically, with no rules to configure.
  • Every recipient is checked against the global and workspace suppression lists at send time.
  • Suppressed recipients are skipped and not charged. Credit is only taken for recipients that are actually sent, and it's returned if an email can't be handed to the mail server.
  • If bounce or complaint rates spike, sending pauses itself, so a bad import can't burn your domain overnight.

You can see the result in the send response. Each recipient gets their own entry and status:

JSON
{  "data": [    { "id": "0b3e…", "to": "ada@example.com", "status": "queued" },    { "id": "9d71…", "to": "grace@example.com", "status": "suppressed" }  ]}

A suppressed status isn't an error. The call returns 200, the other recipients are sent normally, and you don't need to retry. If you look the email up later with GET /api/v1/emails/:id, its status shows suppressed too. The response section of the API reference has the details.

Good habits around suppression

A few practices keep the list doing its job:

  1. Keep contacts and suppressions apart in your head. Deleting an unsubscribed contact to free up room is fine. Clearing the suppression record itself to "clean up" isn't: it is the only thing standing between that address and your next send.
  2. Don't re-import around it. If an address is suppressed, a fresh CSV containing it shouldn't make it sendable again. Check that this holds in any tool you use.
  3. Add manual requests promptly. "Please stop emailing me" in a reply is an unsubscribe. Put it on the list.
  4. Treat removals from the list as exceptions. Only lift a suppression when you have a clear reason, such as a customer confirming a mailbox works again, and only for that address.
  5. Watch the rates, not just the list. Suppression stops repeat damage; it doesn't fix a list that produces too many first-time bounces. Warm new domains carefully (warming up a new sending domain) and keep authentication in order (SPF, DKIM and DMARC setup).

Frequently asked questions

Frequently asked questions

What is the difference between a suppression list and an unsubscribe list?

An unsubscribe list holds only people who opted out. A suppression list is broader: it also includes hard bounces, spam complaints and any address you add by hand, and it's checked before every send.

Should soft bounces be suppressed?

Not after one. A soft bounce is temporary, so retry and count. If an address soft-bounces across many separate sends over several weeks, stop sending to it.

Can I remove an address from my suppression list?

You can, but treat it as an exception. Only lift a suppression for a specific address when you have a clear reason, such as the person confirming their mailbox works again or asking to resubscribe.

Do I pay for emails to suppressed addresses on Rampsend?

No. Suppressed recipients are skipped, returned with status suppressed, and not charged. See the API reference.

Does suppression apply to transactional email too?

Hard bounces and complaints should block all mail, because the address is dead or the person objected. On Rampsend, one suppression list covers both streams, so a complaint about a newsletter also protects your receipts' reputation.