DKIM has been a hot topic of discussion on some of my mailing lists today. One of the open questions is what is holding up adoption of DKIM. I have my own theories, but thought I’d throw out some questions to see how ESPs and ISPs are currently using domain based reputation.
I have set up two surveys one for ESPs and one for ISPs. Responses are anonymous.
I’ll collect responses for a week and share the results.
I did not have a lot of predictions for what will happen with email at the beginning of the year so I did not do a traditional beginning of the year post. Over the last 3 – 4 weeks, though, I have noticed some things that I think show where the industry is going.
Authentication. In January two announcements happened that lead me to believe most legitimate mail will be DK/DKIM signed by the end of the year. AOTA announced that approximately 50% of all email was currently authenticated. They did not separate out SPF/SenderID authentication from DK/DKIM authentication, but this still suggests email authentication is being widely adopted. AOL announced they will be checking DKIM on their inbound mail. I expect more and more email will be DKIM signed in response to this announcement.
Filtering. The end of 2007 marked a steady uptick in mail being filtered or blocked by recipient domains. I expect this trend to continue throughout 2008. Recipient domains are rolling out new technology to measure complaints, evaluate reputation and monitor unwanted email in ways that tease out the bad actors from the good. This means more bad and borderline email will be blocked. Over the short term, I expect to see more good email blocked, too, but expect this will resolve itself by Q2/Q3.
Sender Improvements. As the ISPs get better at filtering, I expect that many borderline senders will discover they cannot continue to have sloppy subscription practices and still get their mail delivered. Improved authentication and better filtering let ISPs pin-point blocks. Instead of having to block by IP or by domain, they can block only some mail from a domain, or only some mail from an IP. There are a number of senders who are sending mail that users do not want mixed with mail that recipients do want. Right now, if there is more mail that recipients want in that mix, then ISPs let the mail through. This will not continue to happen through 2008. Senders will need to send mail users actively want in order to see good delivery.
Less is more. A lot of other email bloggers have talked about this, and I will echo their predictions. Less email is more. Send relevant mail that your customers want. Target, target, target. Good mailers will not send offers to their entire database, instead they will send mail to a select portion of their database.
Feedback loops. Use of feedback loops by recipient domains will continue to grow.
Mobile email. More recipients will be receiving email on mobile devices.
Suggestions for 2008
With all the traveling I did last month, I’m still not back to full blogging speed. I have been slowly reading through the backlog of unread posts from my RSS feeds and there was lots of good stuff published.
Three myths about DKIM by John Levine. A very good explanation taking down some of the myths of DKIM. Also on the DKIM front, RFC 5585 DKIM Service Overview was published last month. According to Cisco, DKIM adoption is climbing. More information about DKIM is available at dkim.org and our own dkimcore.org.
The always awesome guys at Mailchimp have embraced twitter as part of their platform. Not only have they set up their own service for link shortening so that links can be tweeted, but have also incorporated twitter stats into their mail dashboard.
Al has an insightful post on delivery, spam filtering vendors and the differences (or lack thereof) between B2C and B2B marketing. As I tell my customers, there is no switch inside the filtering scheme for “I know this person, they’re OK, let the mail in.”
Terry Zink has started a series about blacklists triggered by the recent SORBS announcement. His first post, My take on blacklists, part 2, discusses how some people go about building a blocklist from scratch.
Happy 7-8-9 everyone.
I have seen a lot of companies attempt to send out customer support surveys by email, only to fail dismally. Generally, the intentions of the companies who do this are good, but the executions are appalling. Companies have found any number of ways to invite epic fail to call, including mailing to non-customers, mailing to the wrong person at a customer company and mailing to former customers.
Mailing to non-customers generally happens when companies sort abuse and support mail through the same ticketing system. Good customer support (tell us how we did) turns out to be rotten complaint support. The failure here is multifactorial, but revolves around not understanding the difference between customer support mail and abuse complaints. Abuse is not, usually, mail from your customers. More often mail to abuse is from non-customers. While it may seem like a good thing to follow up with abuse complaints to find out if the person is satisfied, generally someone who complains about spam does not want more mail from a company. The fix it to change the selection process for surveys. Survey customers not complainers.
The second failure is more common with enterprise vendors. Generally the vendor will have multiple contacts at company but send a single survey out to all contacts at the customer. Take an average website that provides statistics about web or email performance. A company establishes an account there, and then provides a logins for customer support people, a manager or two and maybe an outside consultant. These people are all using the same site, but are possibly using different parts of it. The consultant can give some feedback on the API and data access, but is not the right person to ask about pricing, packages or overall usefulness and value for money. Management can provide feedback on pricing and value for money but probably has never logged into the website, despite having a working account. Customer support can provide feedback on the user interface and overall usefulness of the site. Knowing who is who at the customer and who is the right contact for different surveys can be tricky, but it is always better a company to appear to be acting purposely.
Finally, some companies send out surveys to anyone who has ever registered for a website, or game or product no matter how long ago that registration was. They send mail to the person who registered for a website but has not logged in for 6 months, or 12 months or even longer. The recipient may have even taken positive action to close an account, such as discontinuing payments. And, yet, the company still mails them a customer satisfaction survey. If the recipient is not paying for the product, if the recipient is not logging into the website then they are no longer a customer. Sure, there are times to reconnect with old customers, and it can be done well. However, what I am talking about is the survey that is clearly designed to be answered by current users and customers.
The sad thing is, I have received customer satisfaction surveys in all of the above categories in the last 6 months.
If you as a sender, are going to use customer satisfaction surveys, do it in a thoughtful and purposeful manner. Do it in a way that brings value to your company and to the people you are surveying. If you do not, you risk higher complaint rates. Remember, people who are not your customer or who are a former customer are probably more likely to hit “this is spam” then to answer your survey. Like any mail you send, make sure you know who your audience is and have a mental model for how they will treat your mail. Do not just grab all available addresses and mail them. Do some analysis of your customer base before you mail and mail them surveys that apply to them. You will get fewer spam complaints and probably more and more accurate survey responses.