Reading one of my favorite email deliverability sites, I came across this article announcing what is believed to be the first attempt to aggregate email bounce codes into a single list. Warning: the rest of this post may get pretty geeked out, so proceed with caution.
Why Is This Good?
I will try to explain this in a way that keeps most people interested, but it will challenge my writing ability, I am sure. Anyway, the reason that this is good is because this is the first step in standardizing bounce codes across different email providers and ISP’s, which will lead to better spam-filtering and better delivery.
What Happens Now
From the perspective of someone who is responsible for ensuring that emails get delivered, the process of interpreting bounce codes can be somewhat frustrating. Each email provider and ISP has their own collection of various bounce codes. Usually, each company has dozens, if not hundreds, of different bounce codes that get communicated from their receiving mail servers back to the sending mail servers to indicate the delivery status of each email. Email service providers (those who send marketing emails on behalf of their customers) then interpret the bounce codes in order to convey the delivery status back to their customers. This is how senders know delivery rates, bounce rates, etc, then adjust their lists and sending practices to improve delivery. Its a key part of the whole system.
Improving Delivery
While is it important that email service providers convey the delivery status to their customers, its actually more important that the email service provider understand and utilize the information being sent back by the ISP’s and email providers, so that they can continuously improve delivery and reduce spam. Currently, when I get notice that we have an unusually large bounce rate at one or more domains, I have do what amounts to a manual investigation as to why the bounces are occurring because the industry has not settled on any sort of standardized set of bounce codes (there actually is a specification for general bounce codes, but its not specific enough for today’s modern delivery and spam-fighting practices). Each ISP has their own set of codes and format for reporting the codes, so manual intervention is necessary to ensure proper interpretation of the delivery status.
Standardizing the bounce codes will allow email service providers and senders to automate tasks that will ensure even greater deliverability and better spam protection. Once their is a standard set of codes to be interpreted, all of the delivery verification and proper responses can be fully automated. Email service providers will be able to shut down spammers at the earliest signs of trouble, and other delivery problems that might incorrectly send up a spam-flag currently will be reduced, if not eliminated. Standardization, like with most everything else, will make email delivery and spam detection much more efficient.
Conclusion
Although this is not actually “standardization” yet, its a good first-step toward that process. Having all of the bounce codes aggregated in one place will make it easier for email delivery experts and others to treat bounced emails (and those who send them) properly. Its an exciting step in the process. Eventually, email delivery will be almost totally ubiquitous, like turning on your faucet and expecting water. Users will send emails and the ones that should be delivered will be, and the ones that should be blocked will be blocked and reported back to the sender with the appropriate punitive measure happening automatically. It might seem like we are almost there to many users, but there is still a lot of labor going on behind the scenes that will ultimately be automated.