Suppressions
Addresses we stop sending to after a hard bounce or a spam complaint — why, what you see, and how to remove one.
Your workspace's suppression list holds addresses that hard-bounced or marked your mail as spam. Sending to them again hurts your domain's reputation, and with it every other email you send.
How an address gets there
| Event | Added | For |
|---|---|---|
Hard bounce (email.bounced, type: permanent) | Automatically | The API and Campaigns |
Spam complaint (email.complained) | Automatically | The API and Campaigns |
| Unsubscribe from a Campaigns newsletter | Automatically | Campaigns only |
A temporary bounce (full mailbox, busy server) suppresses no one, though the
email's status reads bounced. Simulated bounces and complaints from
magic addresses never touch the list.
What happens when you send to one
- Suppressed recipients are skipped and not charged; the other recipients get the email as usual.
- Each skipped recipient gets a
suppressedevent on the timeline and its ownemail.suppressedwebhook, withdata.recipientandreasonprevious_bounceorprevious_complaint(Events). - If every recipient is suppressed, the request still succeeds with
200and the email's status issuppressed. - The check runs when you send the request, with test keys too.
Unsubscribed is not suppressed
The API never skips an address only because it unsubscribed from Campaigns — that person still needs their password resets and receipts. Only bounces and complaints count.
Removing an address
Suppressions in the dashboard lists each address with why and when it was added. A teammate who manages sending can let a bounced address back:
- Bounces only. A spam complaint stays on the list — mailing someone who reported you is the fastest way to lose your sending. An unsubscribe can't be taken back either.
- Once per address. If it bounces again, it stays; write to support@charchy.krd if the mailbox really works now.
- Up to 20 a day per workspace — bulk clearing is how senders end up mailing dead addresses.
Let an address back only when the problem is fixed — the person corrected a typo, or asked for your emails again. An address that still doesn't exist only earns a second bounce.
In your app
On email.bounced and email.complained, mark the address in your own
database and ask the user to update it at their next sign-in.