Tech Talk Podcast
Last week I had the pleasure of sitting down and talking delivery and email with W. Jeffery Rice of Brickstreet software. He’s posted a review and the recordings at Brickstreet and the UR Business Network.
Last week I had the pleasure of sitting down and talking delivery and email with W. Jeffery Rice of Brickstreet software. He’s posted a review and the recordings at Brickstreet and the UR Business Network.
A client asked me earlier this week what SLAs ISPs provided for email delivery. The short answer is that there isn’t a SLA and that the only guarantee is that the email will get there when it gets there.
But as I was mentioning this to Steve, he pointed out that there was a recent change in the RFCs for email. In both RFC 821/2 and RFC 2821/2 (the original email related RFCs and the update in the early 2000’s) the RFCs stated that once a receiving MTA accepted an email that that MTA was required to either delivery the mail or generate an asynchronous bounce. While this isn’t a standard SLA, it does mean that a 2xy response after DATA meant the email would either be delivered to the user or be sent back to the sender. Despite the RFC requirements some receivers would still drop mail on the floor for various reasons, sometimes intentionally and sometimes not.
RFC 5321/2, the current SMTP standard, still says that once a server accepts the mail it must not lose that mail ‘for frivolous reasons.’ The RFC goes on to admit, though, that in recent years, SMTP servers are under a range of attacks and dropping mail on the floor is not frivolous in those cases.
I had the privilege to talk with a bunch of experts on the Only Influencers Blog Talk Radio show this morning. The discussion centered around the perceived conflict between Marketing and Delivery.
The conversation was a good one, with a lot of different perspectives aired. I strongly recommend people who are interested in hearing multiple industry experts talking about email marketing and delivery listen to the podcast.
Once I get back from MAAWG I plan to talk a little more about delivery managers as fire fighters and why that is such a good metaphor for delivery.
There is a lot of contention between ISPs and senders at the best of times. As we move into the holiday season, retailers are increasing their email marketing, sometimes quite significantly. This causes more delivery issues as recipients and MTAs react to the increased volume.
At many non retail companies, however, the pace of work slows down. There are distractions and office parties and people taking long lunches to finish their holiday shopping. Non-critical departments are not staffed for official holidays like Thanksgiving and Christmas Day.
This means that delivery issues may not be responded to as quickly as senders might like. Just this morning I got a call from someone who wants his delivery issues to be fixed by tomorrow. I’m sorry, even if I were to treat this as an emergency, there is work and investigation that needs to be done at the ISP end, and they’re not necessarily going to have a staffed delivery desk on Thanksgiving day. And even if they do have a staffed desk, it’s possible the staff won’t be focused and issues won’t be handled as fast as they might otherwise be.
I’d love to help, but there’s a limit to what I can do. Filtering decisions are made by the ISP, or their filter vendor, and sometimes they don’t happen as fast as we’d like. It’s frustrating for senders to have to deal with, but these are the realities of email delivery.