Matt posted a discussion of the portability of IP reputation over at his EmailKarma blog.
I have heard about Hotmail/MSN’s claim that if you add your new IPs to your SPF/SenderID record and send from your old IPs that your old IP reputation will transfer to your new IPs. I’ve not heard it working in practice, but it really can’t hurt to add your new IPs to your records as soon as you know what they are.
Goodmail made a splash on the email marketing and ISP industries a few years ago by announcing their CertifiedEmail program. They guaranteed that using their certification would result in email going directly to the inbox, and all images in the email would be displayed by default. Senders using Goodmail would pay money, per message, and Goodmail would split that money with the receiving ISP.
This sounds very much like a situation where everyone wins. The senders get their mail to the inbox with images turned on. The receiving ISPs get a little money to deliver email and offloads some of their sender screening onto a third party. Individual recipients know that this email is certified and that it’s safe to click on links in the email.
In the time since CertifiedEmail has been announced, however, there seems to be very little adoption. Sure, receivers do seem to be signing up, a little. AOL and Yahoo have been using CertifiedEmail for a while. In summer 2007, a number of cable providers announced they would be using CertifiedEmail as well.
Senders, on the other hand, don’t seem to be adopting this as fast as Goodmail might like. The Federal Government recently announced they would be sending email signed by Goodmail and some large online companies, Overstock.com among them, are also sending with certified email. In order to get more companies to sign up for CertifiedEmail, Goodmail announced in August 2007 that they had partnered with CheetahMail, Episilon and Axciom Digital to provide free CertifiedEmail to qualifying customers of those ESPs.
Why might companies not be adopting CertifiedEmail? I have a couple of thoughts.
“The only solution to our delivery problems isn’t double opt-in, is it?” A question I get quite frequently from clients and potential clients. In the vast majority of cases the answer is no, confirmed (double) opt-in [1] is not the only solution to delivery problems. In fact, there are delivery issues that confirmed opt-in will do nothing to solve.
Many other delivery sites and deliverability experts will tell clients that the solution to their deliverability problems is to switch to confirmed opt-in as a method to collect email addresses. This overly simplistic solution only treats one possible source of delivery problems, the collection of addresses. It does not address data hygiene issues, technical delivery issues or complaints.
While address collection is important, the best address collection processes on the planet cannot fix sloppy data handling, failure to unsubscribe recipients, or non-existent bounce handling. All of these factors play a role in delivery. It is critical to identify the underlying source of delivery problems before advising anyone on how to fix it.
Over the course of the next few blog posts, I am going to take a look at the various issues that affect delivery: permission, data hygiene, bounce handling, complaints and authentication. I’ll talk about what is important and what senders need to look for and be aware of when they’re trying to troubleshoot delivery issues.
[1] There is some disagreement between senders and anti-spammers about the correct terminology to use. Senders use double opt-in to describe the process, anti-spammers use confirmed opt-in. I am using both terms here to mean the same process.
Yesterday I wrote about activist groups getting blocked at major ISPs and how the ISPs don’t block mail because they don’t like the political viewpoints in email. This morning Mark Brownlow has a post up about delivery in general and the cause of many delivery problems.
Read More