Raising the standard

Last week news broke that Mailchimp had disconnected a number of anti-vaccination activists from their platform and banned anti-vax content. I applaud their decision and hope other companies will follow their lead in banning harmful content from their network.


Measuring stick with an arrow and the words "you must be this tall to ride the ride."

These kinds of decisions, where providers say you can’t do that on our network, are because these are private platforms. As I talked about recently, they own the platform, they make the rules.

The same ownership that gives ESPs the right to ban content, also gives them the ability to enforce deliverability standards. These are the rules they enforce on customers to ensure a reasonable reputation. What kind of rules will a good ESP implement and enforce?

  1. Identify yourself and your company with accurate information. Be upfront and transparent about who you are and what you mail at the point of address collection.
  2. Collect permission directly. Do not outsource your permission to a third party. This means no co-reg, no renting lists, no purchasing lists.
  3. Respect your recipients. Do send email at the right cadence for your particular audience. Remove unengaged users who do not interact with your mail for an extended period of time.
  4. Respect the recipient domain rules. Set appropriate limits on the number of connections and sending speed. Handle bounces correctly. Don’t keep connections open for longer than necessary. Don’t allow customers to send spam.

How ESPs enforce these rules depends on the ESP. Some are more proactive than others. Any decent ESP is going to have a deliverability and/or compliance team that monitors for complaints and blocks and other obvious signs of deliverability problems. But the monitoring doesn’t stop there. There are a number of tools that have recently entered the market that allow ESPs to measure the quality of their customers’ data.

ESPs also monitor things like opens and clicks and engagement statistics. Customers who fall below standard thresholds are asked to improve their lists. For some senders this seems invasive and problematic. But responsible and legitimate senders know that removing unresponsive addresses benefits them. Even if they lose a few might-eventually-respond-someday addresses, there is significant long term benefit to maintaining an engaged list.

Enforcing good practices and data hygiene is expensive and can cause some hard feelings among customers. Companies who don’t enforce minimum standards can often find themselves in a downward spiral headed towards failure. I’ve worked with some of the ESPs in the past, and it’s never a good position.

ESPs that do enforce standards and good deliverability practices have customers that reach the inbox more effectively. Their raising of the standards bar often means smaller lists. But those smaller lists have a bigger reach and are more profitable for their owners.

Related Posts

ESPs and deliverability

There’s an ongoing discussion, one I normally avoid, regarding how much impact an ESP has on deliverability. Overall, my opinion is that as long as you have a half way decent ESP they have no impact on deliverability. Then I started writing an email and realised that my thoughts are more complex than that.

Read More

Who pays for spam?

A couple weeks ago, I published a blog post about monetizing the complaint stream. The premise was that ESPs could offer lower base rates for sending if the customer agreed to pay per complaint. The idea came to me while talking with a deliverability expert at a major ESP. One of their potential customer wanted the ESP to allow them to mail purchased lists. The customer even offered to indemnify the ESP and assume all legal risk for mailing purchased lists.
While on the surface this may seem like a generous offer, there aren’t many legal liabilities associated with sending email. Follow a few basic rules that most of us learn in Kindergarten (say your name, stop poking when asked, don’t lie) and there’s no chance you’ll be legally liable for your actions.
Legal liability is not really the concern for most ESPs. The bigger issues for ESPs including overall sending reputation and cost associated with resolving a block. The idea behind monetizing the complaint stream was making the customer bear some of the risk for bad sends. ESP customers do a lot of bad things, up to and including spamming, without having any financial consequences for the behavior. By sharing  in the non-legal consequences of spamming, the customer may feel some of the effect of their bad decisions.
Right now, ESPs really protect customers from consequences. The ESP pays for the compliance team. The ESP handles negotiations with ISPs and filtering companies. The cost of this is partially built into the sending pricing, but if there is a big problem, the ESP ends up shouldering the bulk of the resolution costs. In some cases, the ESP even loses revenue as they disconnect the sender.
ESPs hide the cost of bad decisions from customers and do not incentivize customers to make good decisions. Maybe if they started making customers shoulder some of the financial liability for spamming there’d be less spamming.

Read More

Share your average bounce rates

The question came up on slack this morning about bounce rate benchmarks. What are the normal / average bounces that different ESPs see? Does region matter? What’s acceptable for bounce rates?

Read More