Your ESP Can Block Your Account.

Hey, it's Pavel. Today we're talking about ESP compliance. What actually gets accounts blocked, why ESPs won't tell you the reason, and how to make sure it never happens to you.

This post was triggered by something I saw on LinkedIn recently. A team went public after all of their newsletters on Beehiiv went down simultaneously. No warning, all publications disabled at once.

Their support response said they violated the Acceptable Use Policy and Terms of Use. No specific violation identified. No further details, for security reasons.

The comments split predictably. Some people said this isn't fair. Some asked for more transparency. A few people got it.

I'm in the "few people got it" camp. Let me explain why.

Silent churn is costing you money. Merlin rewards your best readers with points, perks, and tiers. Apply for the beta at getmerlin.app

This came up in the thread and I pushed back on it there too.

People argued that Beehiiv should disclose what the violation was so legitimate publishers could fix it. That sounds reasonable. It isn't.

If an ESP tells you exactly which signal triggered the block, you know exactly what to change to avoid triggering it next time. Bad actors reverse-engineer enforcement. The moment a platform publishes its detection logic, people start optimizing around it. ESPs know this. The vague response isn't laziness. It's intentional.

That said, closing an account is not an easy decision. Before it happens, the compliance team runs an internal investigation. Some platforms schedule a call with the customer before pulling the trigger. Some don't. Beehiiv carries more risk than a standard ESP because of their ad network and Boost. They're not just infrastructure. They're part of the monetization chain. That raises the stakes on both sides.

Not unsubscribes. Spam reports.

When someone hits "report spam," that signal goes back to the ESP. One complaint doesn't move anything. But when they accumulate, the compliance team opens an investigation. If it confirms a pattern, you either get a compliance call or a suspension. Sometimes both, in that order. Sometimes just the suspension.

Most ESPs run on shared IP pools. Your reputation connects to everyone else sending from the same infrastructure.

If you go from a few thousand emails a week to hundreds of thousands overnight, you generate complaints and abnormal unsubscribe rates. You can get the shared IP flagged by Gmail or Yahoo. At that point it stops being your problem alone. The platform now has an infrastructure issue affecting every sender around you, and they move fast to contain it.

This is the one that gets entire account networks wiped at once, which is exactly what that LinkedIn post looked like from the outside.

The pattern: multiple newsletters on the same platform, routed through the same operation, with fraudulent traffic pushed through them to inflate ad clicks, or purchased lists to manufacture engagement. The goal is to look like a real audience when you're not.

ESPs are not naive about this. Click behaviour, open timing, geographic signals. Fake traffic doesn't look like real traffic. When they find it, they don't close one newsletter. They close everything. Same billing details, same IP, same pattern. All of it, at once.

This one catches people off guard.

If you promote affiliate offers and those offers pull your subscribers into aggressive follow-up sequences they never signed up for, you become part of the problem even if you didn't build the funnel. ESPs track where their senders direct traffic. If your links consistently generate downstream spam complaints, it traces back to your account.

Even if someone at an ESP personally finds your content suspicious or doesn't like the look of your account, that alone doesn't get you blocked. The compliance team needs hard evidence, a written internal procedure, and a mutual decision. One person's gut feeling doesn't close accounts.

Legitimate publishers can relax on that point.

But the flip side is also true. If you've been doing something you shouldn't and haven't been caught yet, that's not safety, that's timing. You passed below the radar. You didn't trigger the right threshold at the right moment. That changes. ESPs update their detection, investigations open for other reasons, and patterns surface over time. The absence of consequences is not the same as the absence of risk.

Read the notice carefully. Then, before you write anything to support, gather your evidence. Your signup flow, where your list came from, what the opt-in looked like, your sending history.

Appeal once. Be specific, be brief, be honest. If you made a mistake, say what it was and what you fixed. The compliance team wants to see one thing: that you understand what happened and won't repeat it. That's what gets accounts reinstated.

If you ran fake traffic or bought lists, there's no real path back. They have the data.

Build your list with people who actually opted in. Send consistently enough that they remember who you are. Clean out disengaged subscribers before they start marking you as spam.

Keep your volume consistent and grow it gradually. Watch your complaint rates before the ESP does.

Vet your affiliate relationships. If the offer you promote funnels your subscribers into something aggressive, you own the consequences.

ESPs want you to stay. They make money when you do. The accounts that get blocked are the ones that treated the platform as something to exploit.

That's the whole story.

Pavel

Before You Go: Here's How I Can Help

— Pavel