Implementing Email Authentication
Wednesday, May 24th, 2006Tom Bartel, Chief Privacy Officer at ReturnPath has a good article on their blog that you should read. It is a great guide to getting yourself set up with email authentication. I heard some staggering numbers about Forntue 500 and small businesses today that have yet to set this up for their IPs. If you can just follow this guide below, your campaigns will be a step ahead of those that have not in getting to the inbox.
One of the most basic elements of our work at Return Path is ensuring that clients use best practices in their email delivery processes. A common recommendation we give is to implement email authentication. Email authentication has two primary benefits: It stymies forgery of email messages and allows senders to build a positive reputation with receivers based upon their mailing behavior. Yet many companies, particularly small ones, have never heard of email authentication — and those who have heard of it have not yet initiated a project to implement it.
How does email authentication work? The most common schemes today — SPF, SenderID, and DomainKeys — use the Domain Name System (DNS) to publish “records.” Each record, which is available to the entire Internet community, details the specific machines that are authorized to send mail for a specific email domain.







