There’s something about bounces

I’ve shared a version of this image repeatedly. I think it was only my Facebook friends that got the stick figure screaming in frustration, though.

An overlapping circles diagram showing bounce classifications from 3 different ESPs and how they overlap (and don't) with each other and with my classifications of the underlying error.

The reality is bounce handling is one of the most frustrating pieces of email delivery. Not only that, many people in the email space treat it as a simple process. It’s really not as simple as we’d like it to be.

The above image was created based on docs from 3 different ESPs a client was using. They wanted to normalise their bounce handling across ESPs, and asked me for policy recommendations. I ended up digging through a bunch of docs from their 3 ESPs. I recorded the reasons as reported in the docs in a colored block corresponding to the ESP, then dropped them in the appropriate circle: soft, block or hard.

The shaded circles are based on my interpretations of why these bounces happen.

  • The big grey circle surrounds bounces due to reputation issues.
  • The green circle is primarily networking and technical issues.
  • The top purple circle is non existent or bad addresses

Note, nothing here indicates how we should react to the bounces, this is just a categorisation activity. This classification also has nothing to do with what the actual SMTP response is.

Just remember, next time someone says bounce handling is simple: they’re wrong.

Phishing evolves beyond DMARC
It’s the email time of year…

Related Posts

Relaying Denied

I’ve got multiple clients right now looking for insights about bounce handling. This means I’m doing a lot of thought work about bounces and what they mean and how they match up and how different ISPs manage delivery and how different ESPs manage delivery and how it all fits together. One thing I’ve been trying to do is contextualize bounces based on what the reason is.
Despite what people may thing, spam filtering isn’t the only reason an email fails to deliver. There are lots of other reasons, too. There is a whole category of network problems like routing issues, TCP failures, DNS failures and such. There are address issues where a recipient simply doesn’t exist, or is blocking a particular sender. There are spam and authentication issues. The discussion of all these issues is way longer than a blog post, and I’m working on that.
One of the interesting bounces that is so rare most people, including me, never talk about is “Relaying Denied.” This is, however, one of the easier bounces to explain.
Relaying Denied means the mail server you’re talking to does not handle mail for the domain you’re sending to. 
Well, OK, but how does that happen?
There are a couple reasons you might get a “Relaying Denied” message, most of them having to do with a misconfiguration somewhere. For whatever reasons, the receiving server doesn’t handle mail for a domain.
DNS records are incorrect. These can be due to a number of things

Read More

Don't think bounce handling is important?

James from Cloudmark has his own insight on spamtraps.

Read More

Thoughts on bounce handling

This week’s Wednesday question comes from D.

What are your thoughts on bounce handling

Read More