The SES suppression list, handled
Know which suppression list fires and when. Auto-suppression on your SES, enforced on every send path. One click from $99.
One-time license · one-click AWS install · yours forever
You are in the right place
- The SES account-level list quietly swallows sends without telling your app.
- Your own suppression logic lives in a script one engineer understands.
- One send path that forgets to check is all it takes to mail a complainer.
Side by side
| Capability | sendbunny | Them |
|---|---|---|
| What triggers it | sendbunny: hard bounce or complaint, automatically | SES account list: SES's own criteria · DIY: whatever you coded |
| Where it is enforced | sendbunny: every send path | SES account list: at SES, invisibly · DIY: paths you remembered |
| Who maintains it | sendbunny: the platform, visible in the UI | SES account list: AWS · DIY: you, forever |
Own it in one click
- 1
Deploy and send normally
One Create stack click. Suppression needs no setup; it is part of the send pipeline from the first email.
- 2
Let events do the bookkeeping
A hard bounce or complaint suppresses the address the moment SES reports it. No script, no cron, no forgotten path.
- 3
Review before big sends
Open the suppression view to see who is excluded and why before a large campaign. Confidence beats surprises.
What you get
- Hard bounces and complaints are suppressed automatically.
- Every send path checks the list: campaigns, API, test sends.
- The suppression view shows who is blocked and why.
- One click into your AWS from $99. Your list, your rules.
Best for
- Teams confused about which suppression list did what
- Senders protecting bounce and complaint rates ahead of a review
- Anyone replacing hand-rolled suppression checks
Not for
- Senders who want to keep mailing suppressed addresses
- Teams outside AWS entirely
FAQ
- What is the difference between the SES account-level list and sendbunny's?
- SES keeps an account-level list that silently drops sends to addresses that bounced or complained. sendbunny keeps its own visible list and stops those sends before they reach SES, so your app knows what happened and your rates stay clean.
- Does suppression cover the transactional API too?
- Yes. Every send path checks suppression: campaigns, the REST API, and test sends. There is no back door that mails a suppressed address.
- Will this satisfy an AWS production access reviewer?
- It is exactly the story AWS asks for: automatic handling of bounces and complaints, plus one-click unsubscribe. You can describe it truthfully because it is running in your account.
- What gets suppressed automatically?
- Hard bounces and spam complaints. Soft bounces like a full mailbox are not permanently suppressed, and list unsubscribes are honored separately per list.
Keep reading
Own your email platform today
One click into your AWS. From $99 once. Pay $0 when idle. Scales when you send.