Never get your sending paused by an SES review again.
Amazon SES enforces bounce and complaint limits strictly. One stale import can trigger an account review, and a review can stop your password resets. MailEnv blocks the addresses that cause it and steps in long before AWS does.
The Amazon SES limits that put accounts under review.
AWS watches every SES account's bounce and complaint rates. Cross the first line and the account goes under review. Cross the second and AWS can pause sending entirely, including the transactional mail your customers are waiting for.
Mailbox providers are stricter still. Gmail and Yahoo expect complaint rates under 0.3%, and they act at the domain level whatever your SES account status.
| Under review | Sending may pause | |
|---|---|---|
| Bounce rate | 5% | 10% |
| Complaint rate | 0.1% | 0.5% |
| MailEnv steps in | Well before either line, with throttling, pauses, and an explanation. | |
Bad addresses are blocked before they reach AWS.
The fastest way to blow through SES limits is to keep sending to addresses that already failed. MailEnv's suppression list engine checks every recipient on every request.
- Hard bounces suppressed instantly. An address that doesn't exist gets one bounce, not a second.
- Complaints suppressed for good. Anyone who marks you as spam is never mailed again.
- Unsubscribes honored everywhere. Across every stream and every future send.
- Blocked at the API. Suppressed sends never reach SES, so they can't raise your rates.
Everything that keeps your rates low, running on every send.
Suppression list engine
Bounces, complaints, and unsubscribes are captured from SES events and enforced at the API.
Pre-send verification
Invalid, disposable, and risky addresses are caught before their first send.
Quarantined imports
Imported lists are verified before you can send to them, so an old CSV can't sink your rates.
Throttling & pauses
When rates trend up, sending slows or stops before AWS or mailbox providers step in.
Stream isolation
Tag mail by type so a problem campaign is slowed while sign-in codes keep flowing.
Monitoring & alerts
Bounce and complaint trends tracked continuously, with alerts and a reason for every action we take.
What bounce rate gets an Amazon SES account suspended?
AWS places an SES account under review when its bounce rate reaches 5%, and may pause sending at 10%. For complaints, review starts at 0.1% and sending may be paused at 0.5%. AWS calculates these rates over a representative volume of recent mail.
What does an AWS SES reputation manager do?
It watches bounce and complaint signals, blocks addresses that have already bounced or complained, and slows or stops sending before rates reach the levels where AWS or mailbox providers take action. MailEnv does all of this on every request.
How does automatic suppression work?
When an address hard-bounces, files a spam complaint, or unsubscribes, MailEnv adds it to your suppression list. Later sends to that address are blocked at the API and never reach Amazon SES, so they can't raise your rates again.
Do I need my own SES account for this?
No. You send on MailEnv's SES infrastructure. The guardrails protect your domain's reputation and the shared sending network every customer relies on.
What happens when my rates start rising?
MailEnv throttles or pauses the affected sending and tells you why, well before the AWS thresholds. Tagged streams let critical mail like sign-in codes keep flowing while a problem campaign is slowed down.
Protect the account your password resets depend on.
Get an API key, verify your domain, and send with suppression and reputation guardrails on by default.