End of an era

A few weeks ago, Return Path announced they were being purchased by Validity, who also own BrightVerify. Last week, they had a round of layoffs. According to sources inside the industry, Validity is closing the New York headquarters and Indianapolis offices and layoffs involved more than 170 staff members.


picture of a dictionary page with the word "trust" highlighted

Return Path has been a fixture in the deliverability space for years. While they didn’t invent email certification, they were the only VC backed company that survived. Their suite of tools was the only major player in the market for quite a while. All of this contributed to creating the deliverability industry as we know it today.

But as I’ve been writing about for a while, things are really changing in delivery. How mail is filtered is significantly different now than it was a few years ago. The changes at Return Path, including some of the positions eliminated during the layoffs, tell me that the new owners see those changes as well.

Over the years Return Path has effectively addressed current deliverability challenges. When deliverability was mostly about IP address reputation and global inbox decisions, they created probe accounts and developed their certification program. As filters changed, they introduced panel data and improved their certification requirements. I attribute much of their success to the company leadership and their focus on supporting the same goals as the ISPs – to get email to the people who want it and minimise the amount of unwanted email.

The purchase announcement from Validity makes me wonder how much of that will continue over the next few years. Part of the reason Return Path has been so successful over the years is their focus on permission and good email marketing practices. I don’t see much of that focus in the Validity announcement. In fact, looking at the products Validity are selling they seem to be building a suite of tools designed to minimise the bad effects of acquiring addresses through channels other than direct opt-ins from recipients.

Will Return Path continue on the path its been on for the last 2 decades or will this change under their new owners? Only time will tell.

Related Posts

The inbox is a moving target

The more I look at the industry, the more convinced I am that we’re in the middle of a fundamental shift in how email is filtered. This shift will change how we handle email deliverability and what tools we have and what information we can use as senders to address challenges to getting to the inbox.

Read More

Their network, their rules

Much of the equipment and wires that the internet runs on is privately owned, nor is it a public utility in the traditional sense. The owners of the property have a lot of leeway to do what they like with that property. Yes, there are standards, but the standards are about interoperability. They describe things you have to do in order to exchange traffic with other entities. They do not dictate internal policies or processes.

Read More

Troubleshooting delivery is hard, but doable

Even for those of us who’ve been around for a while, and who have a lot of experience troubleshooting delivery problems things are getting harder. It used to be we could identify some thing about an email and if that thing was removed then the email would get to the inbox. Often this was a domain or a URL in the message that was triggering bulk foldering.
Filters aren’t so simple now. And we can’t just randomly send a list of URLs to a test account and discover which URL is causing the problem. Sure, one of the URLs could be the issue, but that’s typically in context with other things. It’s rare that I can identify the bad URLs sending mail through my own server these days.
There are also a lot more “hey, help” questions on some of the deliverability mailing lists. Most of these questions are sticky problems that don’t map well onto IP or domain reputation.
One of my long term clients recently had a bad mail that caused some warnings at Gmail.
We tried a couple of different things to try and isolate the problem, but never could discover what was triggering the warnings. Even more importantly, we weren’t getting the same results for identical tests done hours apart. After about 3 days, all the warnings went away and all their mail was back in the inbox.
It seemed that one mailing was really bad and resulted in a bad reputation, temporarily. But as the client fixed the problem and kept mailing their reputation recovered.
Deliverability troubleshooting is complicated and this flowchart sums up what it’s like.

Here at Word to the Wise, we get a lot of clients who have gone through the troubleshooting available through their ESPs and sometimes even other deliverability consultants. We get the tough cases that aren’t easy to figure out.
What we do is start from the beginning. First thing is to confirm that there aren’t technical problems, and generally we’ll find some minor problems that should be fixed, but aren’t enough to cause delivery problems. Then we look at the client’s data. How do they collect it? How do they maintain it? What are they doing that allows false addresses on their list?
Once we have a feel for their data processes, we move on to how do we fix those processes. What can we do to collect better, cleaner data in the future? How can we improve their processes so all their recipients tell the ISP that this is wanted mail?
The challenging part is what to do with existing data, but we work with clients individually to make sure that bad addresses are expunged and good addresses are kept.
Our solutions aren’t simple. They’re not easy. But for clients who listen to us and implement our recommendations it’s worth it. Their mail gets into the inbox and deliverability becomes a solved problem.

Read More