They Must Have Changed Something…

One of the most common refrains I hear from folks with delivery problems is that the filters must have changed because their mail suddenly started to go to the bulk folder. A few years ago, I posted about how even when there is no change in the sender’s behavior, reputation can slowly erode until mail suddenly goes to the Gmail bulk folder. Much of that still applies – although the comments on pixel loads (what other folks call ‘open rates’) are a bit outdated due to changes in Gmail behavior.

While it is often true that reputation drives sudden delivery problems there are other reasons, too. Filters are always adjusting and changing to meet new challenges and threats. We’re seeing these changes rolling out at some of the consumer mailbox providers. Steve recently wrote about changes that Yahoo! was making related to domain existence. He also posted about Microsoft getting picker about email address format. Talking with various folks on the receiving side these changes are in direct response to active an ongoing spam techniques.

As with everything in email and filtering, though, there are other reasons that mail can suddenly start going to bulk: the filters change and mail that wasn’t being caught by the filters previously is now caught in them. There are two reasons this could happen to specific mail streams:

  1. The filter is not specific enough and catches mail that isn’t its target.
  2. The filter is specific enough and the mail is the intended target for the updated filter

A lot of senders like to assume they’re in category 1. Sometimes they’re even right. The good news is that most of the consumer mailbox providers and many of the filter companies have channels to report this kind of false positive so they can tweak their filters to stop catching unintended mail.

What about category 2 mail? Where senders think they’re doing everything right because the mail is getting into the inbox. They’re shocked to discover they’re following “all the rules” and their mail was fine and now the filters changed and suddenly their mail isn’t fine.

There are a couple things going on here, all of which contribute to the underlying shock.

First, following all the rules doesn’t mean a sender is actually doing the right things. To be honest, I don’t even know what “all the rules” are for delivery. In my experience there’s no magic checklist of rules that mean mail will be delivered. To my mind, the only real rules are: send technically correct, authenticated email to people who have asked to receive it. That’s it, that’s the rule. Things like bounce rates and complaint rates and open rates and all the metrics we user are, in essence, 2nd order metrics. They are ways we can measure whether or not we’re sending technically correct email to people who asked for it. But all of these numbers are approximations and guesses at the very best. I’ve seen senders with awesome metrics, and who have worked very hard to meet those metrics, while still sending mail that no one wants and no one cares if they don’t get it.

Second, some senders focus on whether or not their mail is getting accepted for delivery. As long as the mail is not outright blocked or they’re not listed on any of the public blocklists then they must be doing things right. This is a bad metric and the one most likely to fall afoul of updated filters. Just because your mail is accepted doesn’t mean it’s wanted by either your individual users or the ISPs. What I’ve seen is that senders’ who use “not blocked” as a metric often have poor practices. Sure, the practices are good enough to get mail through, but they aren’t actually good practices. They’re just good enough to get through the filters.

When mail is just good enough, it’s at risk when the filters get better. When talking about filters with folks I categorize it in three ways. On one side we have mail that is Good and should be delivered, on the other side we have mail that is Bad and should not be delivered. Good mail is things like messages from friends and family, the tickets that you bought or whatever. Bad mail is malware and obvious spam. Between those two extremes is a vast grey area of mail that is hard to filter.

For example, it’s hard to filter mail that some some users want and other users don’t. Using global filters on this type of mail ensures some of the recipients are going to be unhappy about filter decisions. This is impossible for global filters to solve and requires user specific filters.

In other cases, the users clearly don’t want the mail, but it’s hard to reliably identify that mailstream using software. Often in these cases the filter developers and maintainers can manually identify the mail but for various reasons, including that the senders are actively trying to avoid filters, can’t programatically identify the mail… yet. This is a type mail that the filter updates are really trying to catch. This is also the type of mail that when it does get caught and the sender asks for help they don’t usually get it. They’ll get either no response or a vague “we see no issues on our end.” That’s the sign the sender needs to step up their game and stop doing the bare minimum.

Email is a communications channel and there are real people on the other end of that email address. Mailbox providers and filtering companies center the user experience. Senders who don’t center the user in their strategy may discover that their grey mail is blocked or filtered as filters continue to become more and more discriminating.

Related Posts

Mentally modelling filters

When we talk about filters, we often think there is one filter. But, in many cases there are multiple stages of filters, each examining mail in a different way.

Read More

Do system administrators have too much power?

Yesterday, Laura brought a thread from last week to my attention, and the old-school ISP admin and mail geek in me felt the need to jump up and say something in response to Paul’s comment. My text here is all my own, and is based upon personal experience as well as those of my friends. That said, I’m not speaking on their behalf, either. 🙂
I found Paul’s use of the word ‘SysAdmin’ to be a mighty wide (and — in my experience — probably incorrect) brush to be painting with, particularly when referring to operations at ISPs with any significant number of mailboxes. My fundamental opposition to use of the term comes down to this: It’s no longer 1998.
The sort of rogue (or perhaps ‘maverick’) behavior to which you refer absolutely used to be a thing, back when a clean 56k dial-up connection was the stuff of dreams and any ISP that had gone through the trouble to figure out how to get past the 64k user limit in the UNIX password file was considered both large and technically competent. Outside of a few edge cases, I don’t know many system administrators these days who are able to (whether by policy or by access controls) — much less want to — make such unilateral deliverability decisions.
While specialization may be for insects, it’s also inevitable whenever a system grows past a certain point. When I started in the field, there were entire ISPs that were one-man shows (at least on the technical side). This simply doesn’t scale. Eventually, you start breaking things up into departments, then into services, then teams assigned to services, then parts of services assigned to teams, and back up the other side of the mountain, until you end up with a whole department whose job it is to run one component of one service.
For instance, let’s take inbound (just inbound) email. It’s not uncommon for a large ISP to have several technical teams responsible for the processing of mail being sent to their users:

Read More

Politics and Delivery

Last week I posted some deliverability advice for the DNC based on their acquisition of President Obama’s 2012 campaign database. Paul asked a question on that post that I think is worth some attention.

Read More