SES Paused Your Sending After a Break? Here's Why It Happens

If you stopped sending from Amazon SES for a few weeks or months and now SES has paused your account, you're not dealing with a bug. You're dealing with stale addresses — and a black-box enforcement system that doesn't care why your bounce rate spiked.

The documented pattern: a ~5,000-subscriber newsletter on SES, a sending pause of a few weeks. When the publisher comes back and hits send on the full list, the bounce rate on that single campaign blows past SES's tripwire, sending privileges are suspended, and the appeal is rejected. One send, years of list-building gone.

Here's what's actually going on, and what your options are.

What SES sees

SES enforces bounce and complaint thresholds per account. The published guidance: keep bounce rate under 5% (AWS starts warning here) and under 10% hard cap — cross it and your account gets placed under review or suspended. Complaint rate needs to stay under 0.1%.

What SES doesn't tell you: AWS evaluates bounce rates over a representative volume of recent sends — a rolling window, not a lifetime average. A single bad resume send moves that window fast enough to trip enforcement. A list that bounced 0.5% when you sent weekly for a year can bounce 12% after a two-month pause. Same list. Same subscribers. Just older addresses.

Why a pause kills your bounce rate

Three things happen to an email list that sits idle:

1. People change jobs and addresses. Corporate addresses die when people leave. Consumer addresses get abandoned. Industry estimates put list decay at roughly 20–25% per year — so even two or three months of silence means several percent of your list is already dead.

2. Mailbox providers shut down accounts. Yahoo, Gmail, and corporate servers eventually stop accepting mail for inactive accounts, returning hard bounces instead of silently dropping.

3. Spam traps get recycled. Abandoned addresses get converted into spam traps by blacklist operators. Sending to them doesn't just bounce — it flags you.

Add it up: a few months of silence can easily add 3–8 points to your bounce rate. If you were running at 2–4% (healthy-looking), that first send back puts you over 10%. SES doesn't ask "were you on vacation?" It suspends.

The exact failure sequence

1. You pause sending for weeks/months.
2. You resume with a full-list send.
3. Stale addresses bounce en masse — hard bounces spike.
4. SES's automated enforcement pauses your sending privileges.
5. You file an appeal explaining the pause.
6. The appeal is rejected (it's a black-box review; most people get a form response).
7. Your list — the asset you spent years building — is stranded.

The cruelest part: SES gave you no warning that the pause was dangerous. There's no "your list has aged, consider re-warming" notice. The first signal is the suspension.

Can you recover the SES account?

Be honest with yourself here. Some people win appeals. Most don't. If your appeal was already rejected, further appeals on the same account rarely succeed — SES support treats a rejected appeal as final more often than not.

Your real options:

• New SES account (new AWS account, new sending domain, new identity). This works, but you're back under the same black-box tripwire, and you still have the stale-list problem. You'd need to clean the list first anyway — see below.
• A different ESP (Mailchimp, beehiiv, etc.). Same enforcement exists everywhere; you're just moving the dependency.
• Self-hosted sending you actually own (Sendy + your own SES account, MailWizz, Listmonk). You still answer to mailbox providers on bounces — but nobody can unilaterally delete your list, your segments, or your history. The list export is yours, day one. This is the only option where the pause can't strand the asset itself.

The real lesson: clean before you resume

Whatever rail you use, never resume full-list sending after a pause without cleaning first:

1. Export the full list first. This should be possible on day one with any platform you trust. (It's not always — that's the test.)
2. Run a bounce/verification pass. Cheap verification services (or the self-audit checklist below) flag hard bounces and known traps before you send a single real email.
3. Re-warm in segments. Send to your most engaged 10–20% first. Expand only as bounce rate stays under 2%.
4. Sunset the unengaged. Anyone who hasn't opened in 12+ months is a liability, not a subscriber. Archive them.

Running step 2 before that send is what would have saved the list.

Get the free ListProof self-audit checklist

A one-page checklist built from exactly this failure — the 9-step self-audit to run before that send. Free, no signup theater:

→ [Get the SES Resume Self-Audit Checklist] (lead magnet CTA — link TBD)

And if your account is already suspended and the appeal went nowhere: I do fixed-price SES rescue audits (CA$899) — I tell you in one pass whether the account is recoverable and what rail to land on. If the safe segment bounces above the prediction on your first send, we re-run the analysis free.