Help for owners
My email sending account was suspended or paused
Short answer
Providers pause sending when bounces, complaints or content signal poor practice. Amazon SES, for example, places accounts under review at a 5% bounce rate or 0.1% complaint rate, and wants the cause and the fixes you already made in writing. Find the cause first and do not open a second account.
Does this sound like your situation?
- I got an email saying my sending is paused, under review or blocked.
- Password resets and receipts stopped at once.
- The dashboard shows a status other than healthy.
- A marketing campaign went out just before it happened.
- My developer says the service is rejecting everything.
Why does this happen?
Bounce rate rose
Amazon SES says to keep the bounce rate below 2%, places the account under review at 5% or more, and might pause sending at 10% or more. Old, bought or mistyped addresses are the usual cause.
Confirmed by docs.aws.amazon.com
Complaints rose
Amazon SES says to keep the complaint rate below 0.1%, with a review at 0.1% and a possible pause at 0.5%. Mail to people who did not ask for it or content that differs from what they signed up for drives it.
Confirmed by docs.aws.amazon.com
Spam traps or unsolicited content
SES also acts on hits against spam trap addresses, and on mail that appears unsolicited, phishing related, or in a use case it does not support.
Confirmed by docs.aws.amazon.com
A review period passed without a fix
SES says an account under review can keep sending, but if the issue is not fixed before the review period ends, sending can be paused. Notices go to the email address on the AWS account, which may not be the one the app uses.
Confirmed by docs.aws.amazon.com
Domain not verified
Mailgun says an unverified domain looks more suspicious to it and raises the risk of the account being disabled, and that verified domains need SPF and DKIM records.
Confirmed by documentation.mailgun.com
What can I do about it today?
- Find the notice and read itSearch the inbox of the account owner, including spam, for the provider's message. It states the reason and what to do next.
- Stop whatever was sendingPause the campaign or automation that may have caused it. SES advises stopping mail while the problem is fixed, if you can.
- Do not open a new account to carry onMoving the same list to another account tends to repeat the problem and can break the provider's terms.
- Gather the facts for the replyHow you got the addresses, how people sign up and unsubscribe, and which mail types you send.
- Reply only with fixes already madeSES asks for the cause, the changes you have already made and how they prevent a repeat, not plans.
When should I bring someone in?
- Your transactional mail is down and the business depends on it.
- You do not know the cause and the provider can only give a high-level summary.
- The review request was refused.
How do I handle it?
- Establish the cause from the dataBounce and complaint logs, list sources and campaign history decide the cause, not guesses.
- Clean up the root problemList hygiene, double opt-in, suppression, working unsubscribe and sender authentication, whichever applies.
- Write the review responseA factual reply in the provider's format: cause, completed changes, prevention. You send it, as it is your account.
- Protect the essential mail meanwhileI look at whether password resets and receipts can safely run through a separate route while the review runs, within the provider's terms.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I keep sending while under review?
Amazon SES says you can continue to send during a review, but should correct the issue, or sending may be paused when the review period ends.
Will the provider tell me which addresses caused it?
Amazon SES says it typically gives only a high-level overview and that you must investigate the root cause.
Is a pause permanent?
Not necessarily. The decision is the provider's, and I cannot promise it will be lifted.
Is this the same for Mailgun and SendGrid?
Each has its own rules and limits. Read your provider's notice and policy; the method is the same: cause, fix, written reply.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.