Thoughts on SenderScore

Kevin Senne posted over on the Oracle blog about how we need to stop caring about SenderScore and why it’s not as useful a metric as it used to be.
I can’t argue with anything he’s said. I think there is way too much focus on IP reputation and SenderScore. There’s so much more to deliverability than just one or two factors.
In fact, if you’ve been to any of my recent webinars or talks you will probably have seen some version of this image in my slides:
SenderScore99_cropped
Basically, just because you have a great SenderScore doesn’t mean you’re going to have good delivery.  Likewise, having a poor SenderScore doesn’t mean your mail is destined to be undelivered.
I tell clients, and people who ask about SenderScore that it reflects the data that Return Path gets, run through their proprietary algorithms to come up with a score. And that score is relevant for those ISPs that pay attention to it. But most ISPs make the deliver or not deliver decision based on their own internal data, not on the IPs SenderScore.

What’s more important for deliverability is the email reputation. Email reputation combines content reputation, link reputation, IP reputation and sender reputation into one score. Emails with poor reputation are often blocked during the SMTP transaction. After mail is accepted it goes through the personalized filters and then it’s delivered to the inbox or the bulk folder.
NewDeliverabilityModel
Filters are complex. I’m not ready to give up any available data, including the SenderScore, when troubleshooting delivery problems for my clients. But I also don’t work to fix a client’s SenderScore. I work to fix a client’s deliverability. Sometimes that improvement is shown in SenderScore improvements. Sometimes it’s not.

When did the reject happen?
Dealing with blocklists, deliverability and abuse people

Related Posts

Images at Yahoo

For a while, Yahoo was giving preferential “images always on” treatment to Return Path Certified senders. The tricky part of this was the senders had to register a DKIM selector key with Yahoo. I had a lot of (somewhat rude) things to say about this particular design decision.
Over the last few months, a number of senders have complained about being unable to update their selector keys with Yahoo. (Insert more rude comments about how broken it is to use the selector as a part of reputation.) Around the same time, a few of us have noticed that Yahoo seems to be turning on a lot of images by default. A few of the ESP delivery folks collaborated with me on checking into this. They could confirm that images were on by default for some of their customers without certification and without selector key registration.
Earlier this week, Return Path sent out an email to users that said that Yahoo would no longer be turning images on by default for Return Path Certified IPs.

Read More

Return Path announces new abuse prevention service

Return Path announced a new product this morning, designed to help mailbox providers stop outbound abuse.

Read More

Return Path releases inbox benchmark study

Earlier this week Return Path released their quarterly inbox placement benchmark study, and the results aren’t good.
According to this data, 22% of opt-in emails are not making it to the inbox. An interesting note is that 25% of email from social networks never makes it to the inbox. This is a challenge for social networks, but I’m not sure many individuals care. For a lot of people, if they don’t get mail from a social network it doesn’t really matter. They’ll either log into the network and get it, or they’re not really engaged with the network. And, when networks try to increase the amount of mail they send, that can turn into a problem as well.
Overall, the failure of mail to get into the inbox is a problem for senders. The underlying issue is that ISPs want to deliver mail the recipient wants. But much of the email out there, including marketing and social network updates, is mail the recipient is fine with getting, and equally fine with not getting.

Read More