Help Center

Why We Charge for Rejected Emails

Why we charge for spam banner.png

ℹ️ Note: This article refers to how we count Email Messages sent from "Outbound Filtering" accounts. If you have an Email API account, please refer to our general article on how we count messages: How MailChannels Billing Works - and Why.

If you've looked at your MailChannels invoice and noticed that you're being billed for messages that were blocked, rate-limited, or otherwise rejected, you might be wondering whether that's a mistake. It isn't. Charging for every message you attempt to deliver through our service — regardless of whether it reaches the recipient's inbox — is a deliberate policy, and one we've maintained for many years. I want to explain why.

The short answer

We charge for rejected messages because doing so gives you a powerful economic incentive to clean up abuse on your platform before it spirals out of control. That might sound counterintuitive at first, so let me walk through the reasoning.

The problem we're solving together

If you're a MailChannels customer, you're most likely a web hosting provider or a multi-tenant SaaS platform. That means you have hundreds or thousands of users sending email through your infrastructure, and you can't personally review every message. Some percentage of those users — often without your knowledge — will at some point start sending spam, phishing emails, or other forms of abuse.

When that happens, MailChannels steps in. Our filtering engine identifies the problematic traffic and blocks it before it can damage your IP reputation or the reputation of the broader sending pool. This is the core of what we do, and it works.

But blocking abuse is only half the battle. The other half — the half that actually matters for long-term deliverability — is making sure you take action against the abusive sender on your end.

Why free rejections create the wrong incentive

Imagine a world where we didn't charge for rejected messages. In that world, when one of your users starts blasting spam and we block it, there's no cost to you. The spam doesn't go out, your reputation is protected, and your bill stays the same. Problem solved, right?

Not really. Here's what actually happens: because there's no cost, there's no urgency. The abusive account stays active on your platform. It keeps trying to send. We keep blocking. And over time, the volume of attempted abuse grows — not just from that one account, but from others like it, because your platform has become known as one that tolerates abusive signups without consequence.

This is the classic problem in any shared-responsibility system: if one party bears all the cost of enforcement while the other party bears none, enforcement gradually breaks down. We've seen it happen. Platforms that don't feel the cost of abuse tend not to invest in preventing it.

Charging for spam creates an incentive for change.png

How charging changes the equation

When you're billed for every attempted message — including the ones we block — something different happens. You start paying attention. You set up a webhook to receive real-time alerts from the Monitors service. You notice that a particular user or domain on your platform is generating a spike in blocked traffic. And because that spike is hitting your bottom line, you take action: you suspend the account, you tighten your signup process, you implement better verification, or you reach out to the user to understand what's going on.

In other words, billing for rejected messages closes the feedback loop. It transforms our blocking signals from something you might glance at into something you act on.

The counterintuitive outcome: you send less and pay less

Here's the part that surprises most of our customers. When you start actively responding to the signals MailChannels provides — shutting down abusive senders, tightening onboarding, monitoring your sending patterns — the total volume of email flowing through our service tends to go down. Not because your legitimate email decreases, but because the illegitimate email that was inflating your numbers gets eliminated at the source.

We've watched this pattern play out across hundreds of customers over many years. The ones who lean into the feedback loop end up with cleaner platforms, better deliverability, and lower bills. The ones who ignore the signals and treat our blocking as a "free" service tend to see their costs and their abuse volumes grow in lockstep.

We know it can feel unfair

We understand the initial reaction. When you see charges for messages that never reached anyone's inbox — messages sent by an abusive user you didn't authorize — it can feel like you're paying for someone else's bad behavior. And in a narrow sense, you are.

But consider the alternative. In email, reputation is everything. If we simply absorbed the cost of blocking abuse and asked nothing of you, we'd be enabling a dynamic where abuse on your platform has no consequences until it's too late — until your IPs are blacklisted, your legitimate customers can't send email, and the damage is already done. By then, the cost of remediation is far greater than the cost of a few blocked messages on an invoice.

Our pricing model is designed to keep you engaged in the process of maintaining a clean sending environment. It's an early-warning system with financial teeth, and it works precisely because it asks something of you.

What you should do

If you're seeing charges for rejected messages and want to bring those costs down, here's what we recommend:

  1. Use Monitors actively. Our Monitors & Alerts feature surfaces the users and domains on your platform that are generating abuse. Check your alerts regularly — or better yet, integrate it into your operations workflow by receiving Monitors webhooks so you can automate responses to abuse signals.
  2. Act on the signals quickly. When Monitors flags a sender, investigate and take action. Suspend accounts that are clearly abusive. Reach out to users who might not realize they have a compromised account.
  3. Tighten your onboarding. Many abuse problems start at signup. If you're seeing repeated patterns of abusive accounts, consider adding email verification, CAPTCHA, phone verification, or manual review for new signups.
  4. Set sending limits. Reasonable per-user sending limits can contain the blast radius of a compromised or abusive account before it generates significant blocked traffic.

A shared commitment to a cleaner email ecosystem

At MailChannels, we see ourselves as your partner in maintaining email deliverability. Our filtering catches the bad traffic. Our Monitors tell you where it's coming from. And our pricing model ensures that you have every reason to act on that information.

We charge for rejected messages not because we want to penalize you, but because we've learned — through years of operating in the email deliverability space — that this model produces the best outcomes for everyone: for you, for your users, for the recipients of your email, and for the health of the email ecosystem as a whole.

If you have questions about your bill, or if you'd like help setting up automated abuse response workflows using Monitors, our support team is always happy to help.

— Ken Simpson, CEO, MailChannels

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.