Changes happen, even if you don't keep up

I cannot count the number of times I hear someone complain that they didn’t change anything and now their email isn’t delivering and why did this happen all of a sudden and how can they be blocked now when they weren’t blocked 3 months ago. Nothing changed, so why all of a sudden is mail failing?

an image of colored lights with the words 'Change The Only Constant' superimposed on them

The problem is that the person asking the question is only looking at things from their own perspective. They didn’t change anything, so of course nothing changed. This point of view is inherently self-centered, thinking that the only thing that matters is the sender. It demonstrates a failure to understand one of the core concepts of SMTP. Each side of a SMTP transaction pays for email. The senders pay all their costs, but the receivers also experience costs to delivering mail. In fact, many of the costs a receiver experiences (spam filtering, for instance) are due to bad senders not through any choice of their own. Some could actually argue that the primary costs of email are borne by the people who receive the email, not the people who send it. It’s certainly more true that bulk senders profit more from email that the large receivers.

Back in the day, there was an old argument about who funds the US Postal Service (USPS). Does bulk mail subsidize the cost of non-bulk mail or does non-bulk mail subsidize the cost of bulk mail? This would usually come up when some spammer would wander into anti-spam discussions and start on about how we shouldn’t block spam because it was cheaper (and more environmentally friendly! savetrees.com) than bulk postal mail. And that they paid for that mail to be delivered, so it was on the receivers to deliver mail they paid for. What all of the folks arguing about postal mail forgot is that: The USPS controls all bits of postal delivery. They even own the mailboxes to the point where it’s against the law in the US to put anything in a postal box if you’re not the USPS. That’s why you can’t get commercial deliveries to a PO box.

This USPS model is not the model of email. In email, you own (or rent) the infrastructure to send and receive mail for your own domain or your own entity. It’s a cooperative model, one where the responsibility for delivery shifts from sender to receiver at the instance the SMTP session goes away (really, that is part of the SMTP RFCs)

In other words, message transfer can occur in a single connection between the original SMTP-sender and the final SMTP-recipient, or can occur in a series of hops through intermediary systems. In either case, once the server has issued a success response at the end of the mail data, a formal handoff of responsibility for the message occurs: the protocol requires that a server MUST accept responsibility for either delivering the message or properly reporting the failure to do so (see Sections 6.1, 6.2, and 7.8, below).RFC5321

It’s not just the responsibility that hands off, it’s also the cost of delivery. At the point the SMTP session closes, any futher costs of delivery are assumed by the receiving server. At no point are senders paying email receivers to deliver email (barring that one company that tried it but ended up failing in part because they failed to keep spammers off their service).

All of this is the long way of saying: The receiving server can and does block mail and it’s their right because they are paying for the delivery. They can also change the rules on what kind of mail they will deliver at their perogative. Don’t like their rules? OK. You can lobby for them to change them, I’ve done it many times over the years and even been successful in doing so. But the choice to deliver mail always comes down to the folks who are paying the bills to deliver that mail.

Why the rant today? I was offering advice to someone about how to handle a delivery issue. They came back to me with “But we haven’t changed anything! Why do we need to make changes now?!” OK, you didn’t change anything. That doesn’t mean what you’re doing or sending is acceptable. Sometimes senders get away with poor behavior because they’re just not the worst right now or because they can’t be blocked without substantial collateral damage (e.g. cold email). As a sender, the only thing you can really do is change your behavior.

The last few years we’ve seen receivers grow more and more aggressive about requiring bulk mail actually follow standards and best practices [e.g. this recent blog post about message-ids from Steve. Some of this is because they’re tired of paying to subsidize sender business models and marketing.

This isn’t something new. I even blogged about this very thing back in 2009. That’s more than 15 years ago where I was telling bulk senders it was time for them to take responsibility for their mail and their actions.

Looks like some folks still haven’t gotten the message.

Related Posts

Life of an Email

I’m repeating the presentation I gave at M3AAWG in London for the Certified Senders Alliance.

It’s all about how to send an email by hand, and how knowing the mechanics of how an email is sent can help us diagnose email delivery issues.

We’re starting in about five hours from when I post this.

Register at https://register.gotowebinar.com/register/2268789893122531343

Read More

When did the reject happen?

conversation_for_blogEarlier today I approved a comment from Mike on a post about problems at AOL from 2012. The part of the comment that caught my attention:

Read More

Send Actual SMTP

It’s rare I find mail that violates the SMTP spec (rfc5321 and rfc5322). I’ve even considered removing “send mail from a correctly configured mail server” from my standard Best Practices litany.

Read More