Home / Blog / Why ESPs suspend accounts

Why ESPs suspend accounts

By Andrej Uzusienis · November 16, 2026 · 8 min read

An email service provider suspending your account is not a punishment for being a bad customer. It is self-defence. Your provider sends mail from shared infrastructure, and the reputation of that infrastructure is their core asset. If your campaign generates a complaint spike or hits a spam trap, the damage lands on every other customer in the pool.

That framing explains almost everything about how suspensions work: why they happen so fast, why they often happen mid-send, and why the appeal that works is the one that convinces the provider your sending is now safe for the pool.

The triggers, roughly in order of how fast they act

A bounce spike on the first send of an imported list

This is the most common cause by some distance. You import a list, launch, and in the first few thousand messages a large share come back as invalid recipients. Automated systems halt the send and flag the account, often within minutes.

Providers do not publish exact thresholds, and they vary. What is consistent is that a hard-bounce rate in the high single digits on a fresh import will draw attention, and anything above that will usually stop the send outright. It is a strong signal, because no carefully collected list bounces like that.

This one is almost entirely preventable: verify before import and the spike never occurs. The bounces you would have generated are removed before they reach the provider's infrastructure.

Complaint rate above threshold

Complaints arrive through feedback loops from mailbox providers and are monitored continuously. Thresholds are low: Google asks bulk senders to stay below 0.30% spam rate and recommends under 0.10%, and ESPs typically enforce something in that neighbourhood, because above it their own delivery to that mailbox provider degrades.

Complaint spikes usually come from a change rather than a constant: a list segment that has not been mailed in a long time, a sudden frequency increase, a rebrand that makes the sender unrecognisable, or a lead-magnet list being mailed as if it were a newsletter list. See reducing spam complaints.

Spam trap hits

Traps are the trigger with the worst ratio of visibility to consequence. You get no feedback that you hit one — the mail is simply accepted — and the first thing you learn is that a blocklist has listed the sending IP, at which point your provider acts immediately to protect the pool. A pristine trap hit indicates scraped or purchased data; a recycled trap hit indicates a stale list nobody has cleaned. See what a spam trap is.

A volume jump with no history

An account that has sent 3,000 messages a month for a year and suddenly queues 300,000 looks identical, from the outside, to an account that has been compromised. Most providers throttle or hold sends that break sharply with an account's established pattern, and will ask what changed before releasing the rest.

The fix is to tell them first. Providers are generally willing to raise limits for a planned campaign if you give them notice and can explain where the recipients came from. Ramping gradually also helps; see domain warm-up.

Authentication failures

Mail failing SPF or DKIM, or failing DMARC alignment, gets filtered harder by receivers and reflects badly on the sending infrastructure. Most providers now require authentication to be in place before they will let you send from your own domain at all. See the authentication guide.

Prohibited or high-risk content

Nearly every provider's acceptable use policy restricts certain categories outright — typically gambling, adult content, cryptocurrency offers, pharmaceuticals, debt relief, multi-level marketing — or confines them to approved accounts. Link reputation matters too: a URL shortener whose domain already appears in blocklists, or a landing page on a shared domain used by spammers, can get your mail flagged independently of your own behaviour.

Signals that look like fraud

A new account, a mismatch between billing country and login location, a payment method that fails, and a large list imported in the first hour is a combination that will trigger review on almost any platform. It is also exactly what a disposable spam account looks like. New accounts get less benefit of the doubt than established ones, for good reason.

Check an address before you send to it

Mailcheq runs syntax, MX, disposable, role-account and live SMTP checks in the browser, free.

Verify an address →

How suspension usually unfolds

  1. Automated hold. A send is paused mid-flight, or sending limits drop to zero. Often the first you know is that the campaign stopped.
  2. Review request. The provider asks where the list came from, how consent was collected, and what you are sending. This is a real question, not a formality.
  3. Outcome. Reinstated, possibly with reduced limits and a monitoring period; restricted to a subset of your list; or terminated, which on most platforms is final.

What a credible appeal contains

Providers see a great many appeals and have a good sense of which ones precede a repeat incident. What moves the decision is evidence, not assurance:

What does not work: arguing about thresholds, claiming the bounces were the provider's fault, or asking to be moved to a different IP. The last one in particular reads as an attempt to escape the reputation rather than fix the cause.

Preventing it

The underlying logic

Almost every suspension trigger is a proxy for one question: does this sender know who is on their list? A clean bounce rate, a low complaint rate, no trap hits and a steady volume curve are all evidence of a list collected deliberately and maintained since. A bounce spike is evidence of the opposite, which is why it gets acted on so quickly.

Verification and list hygiene are not just deliverability tools. They are the evidence that keeps your account open.

Spotted an error on this page? Email hello@mailcheq.com and we will fix it.