Delivery
Automatic suppressions
Protect your sending reputation by blocking addresses that hard-bounce or complain.
What creates a suppression
Authenticated, correlated permanent bounces and complaints create permanent organization-scoped suppressions. Complaints take precedence over hard bounces. Transient bounces, delivery delays and not-spam feedback do not create suppressions.
Suppression applies across projects in the same organization. It does not affect independent organizations. BCC recipients are protected without appearing in public timelines.
How sends are blocked
The API checks every To, CC and BCC address. If any address is suppressed, the entire request is stored as suppressed without queuing or charging monthly quota. The worker checks again before contacting SES, protecting messages already in the queue.