Suppressions
The list of addresses BillionSend will not mail again, to protect your sender reputation.
The suppression list holds addresses that should not be mailed, so you never send repeatedly to an address that bounced or marked you as spam. It protects your reputation and your sending limits. Find it in the dashboard under Audience → Suppressions.
How addresses get on the list
- Hard bounce. The receiving server permanently refused the address. Soft bounces do not count.
- Complaint. The recipient marked an email as spam.
- Invalid address. Deep list verification found that no mailbox answers there.
- Full mailbox. A contact’s mailbox reports full twice, between 1 and 30 days apart.
- Manual. You added it, in the dashboard or with the API.
Bounces and complaints are added automatically. The list is per team and holds one entry per address. It describes the address, not a brand: an address that does not exist is the same fact whichever of your domains mails it.
A recipient who clicks unsubscribe is not added here. That choice is recorded as an unsubscribe for the domain whose email held the link, and stops marketing mail only. The suppression list stops every email to the address, transactional mail included.
What it does
- Every send skips suppressed recipients:
POST /emails, the SMTP relay, topic sends and broadcasts. They are removed fromto,ccandbcc. - If every recipient is suppressed, the send is refused with
422 all_recipients_suppressed. The SMTP relay answers550. When this empties aPOST /emailssend, BillionSend keeps a record with statussuppressedand no content, which does not count toward your volume, and sends theemail.suppressedwebhook. - Mail that waits is checked again when it goes out, so a scheduled email skips addresses suppressed in the meantime.
- Broadcasts skip suppressed contacts.
Every change to the list sends a suppression.added or suppression.removed webhook.
Review and remove
The dashboard lists each address with its reason and date. Recipients’ unsubscribes are in a separate tab, each with its domain.
You can remove an address to allow sending again. Do it only when you know the cause is fixed, for example a mailbox that always existed but was refused by a misconfigured server. The address is suppressed again at its next bounce or complaint.
API
The SDKs call the /suppressions endpoints as suppressions.*. Each entry is { id, email, origin, source_id, created_at }. origin is bounce, complaint or manual, and source_id is the email whose bounce or complaint created the entry.
curl -X POST https://api.billionsend.com/suppressions \
-H "Authorization: Bearer $BILLIONSEND_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "email": "user@example.org" }'
GET /suppressions?origin=bouncelists entries, newest first, optionally by origin.GET /suppressions/{id}andDELETE /suppressions/{id}take the entry id or the email address.POST /suppressionsadds an address. The optionalorigin(bounce,complaintormanual, defaultmanual) lets you bring over bounce and complaint history from another provider. Adding an address already on the list returns its existing entry.POST /suppressions/batch/addwith{ "emails": [...] }andPOST /suppressions/batch/removewith{ "emails": [...] }or{ "ids": [...] }take up to 1,000 addresses per call.
Removing an entry needs a key created by an owner or admin. See Team roles.
An address whose personal data you erased keeps blocking sends, but is hidden from the list and from lookups by email. It stays reachable by its id, which shows "[erased]" as the email.
Amazon SES and your team
Amazon SES keeps its own suppression list for your team, separate from every other team’s: a bounce on your mail never blocks another team’s mail to the same address. SES adds bounces and complaints to it by itself. When you remove an address here, it is removed there a few seconds later. A send that SES refuses because of its list shows as a permanent bounce with the subtype OnTenantSuppressionList.
If your bounce or complaint rate climbs too far, SES can pause your team. Owners get an email with SES’s reason, your mail is held rather than failed, and it goes out when SES enables sending again. See Sending limits.