Authentication

Email Authentication

Email authentication can help your email marketing campaigns look more reputable, which helps your deliverability to the inbox. So at MailChimp, we support multiple authentication methods to cover all bases.

Ever get an email that claims it's from your bank, or eBay, or PayPal? It actually looked pretty real, but it turned out to be a forgery? That's the problem with email: it was originally created to be an extremely easy way to communicate, but it also happens to be extremely easy to forge. Authentication is a way to prove an email is not forged.

Authentication Should Be One-Click Simple

Email authentication is useless if it's too hard to implement. Many email service providers require server setup in order to authenticate your email campaigns. Accessing your server to modify DNS and TXT records and modifying your MTA is just not practical (especially for small businesses). So at MailChimp, we've made authentication a free, one-click process.

Authentication & Deliverability Resources:

authentication
Types of Email Authentication

There is no one "favorite" or "best" authentication method. They all have their advantages and disadvantages. In short, some simply require a file on your server that can be cross-referenced by a receiver (SPF, SenderID). These methods are easy to implement, but some say not as secure. Other types of authentication (Domain Keys & DKIM) actually embed code in the email itself. These methods make it tougher to forge emails, but can also be tougher to implement for the sender, and the receiver. Because of the various pros and cons, different receivers choose to check for different types of authentication. Until there's some standard, senders may want to just employ all authentication types (MailChimp's authentication covers all bases).

http://www.mailchimp.com/nonrestrictiveocean.php