Suppressions

The list of addresses we will not send to, so you stop mailing people who bounce or complain.

How addresses get on the list

Permanent bounces. The address does not exist or refuses mail for good.
Spam complaints. The recipient marked a message as spam.
You add them in the dashboard (Suppressions) or with the API, for example when someone unsubscribes in your app.

The list belongs to your organization, so every project shares it. An address suppressed through one project is not mailed by another.

What happens when you send to one

Suppressed recipients are skipped. If every recipient of a request is suppressed it is rejected with recipient_suppressed. In a batch, that message reports the error in its own slot and the rest still send.

Removing an address

You can remove an address in the dashboard or with the API. Only do it when you are sure the person wants your mail, for example after they fix a full mailbox and ask to hear from you again. Removals are recorded in your audit log, and if the address bounces or complains again it goes straight back on the list.

Never remove an address that complained. Sending to someone who reported you as spam hurts your sending reputation more than anything else.

API access

The API uses its own scope, suppressions:manage, so a key that only sends mail cannot edit the list.