Manage suppressions
The suppression list is the server's do-not-send memory. It protects your reputation, since sending into known-bad addresses is how domains end up in spam folders.
How addresses get suppressed
- Hard bounces, where the mailbox does not exist.
- Repeated soft failures beyond the retry budget.
- Manual additions from support or legal requests.
Suppressed recipients are skipped at send time; they do not count against your volume and show up in the send response accordingly.
Work with the list
# inspect GET /api/v2/admin/organizations/{org}/servers/{server}/suppressions # add one manually POST …/suppressions { "address": "gone@example.com" } # remove one (they fixed their mailbox, or opted back in) DELETE …/suppressions/gone@example.com
Practices that keep the list small
- Validate addresses at signup (email-verification template) instead of discovering typos via bounces.
- Subscribe to webhooks and mark users with bounced mail in your own database, so you stop queueing mail your side too.
- Only delete suppressions when you have positive evidence the address works again. Bulk-clearing the list to “fix” delivery numbers does the opposite.
Bounced sends still count as sent volume (the work was done); suppressed recipients don't. Details: pricing FAQ.