Sender Authentication – How To Get Emails Delivered

How to get the emails delivered, opened and read has always been, is and I’m sure will be the question of vital importance for email marketers. We are always looking for new email delivery tactics to improve our email campaign performance.

In one of my previous articles I’ve already touched upon the email filtering and blocking issue and talked about the reasons why the email may be blocked or filtered by ISPs. That was mostly all about the message content and list building. There is no doubt that the content of the email message and quality of the list affect email deliverability. Those are two primary factors email marketers should be concerned of.

But there are also some technical issues that may be overlooked by email marketers but play a significant role in the email delivery process. By addressing those issues you can increase your email deliverability rate and ensure your newsletter is delivered directly into the recipient’s Inbox.

You know authentication between the sender (email marketer) and receiver (recipient’s ISP) is quickly being adopted and put into practice. Email authentication is the effort to include identifiable information into the messages so that the receiver can recognize incoming email message automatically. Email authentication helps prevent forged emails from being sent from your mail server and thus, helps reduce the amount of spam in the recipient’s Inbox.

The sender’s authentication can be done in several ways: SPF, Reverse DNS Lookup, DomainKeys, or Sender ID.  So, if your opt-in email messages are constantly being blocked by an ISP, you will most likely need to adjust your authentication records before you start thinking about your entire email sending program restructure:  

  • Set up SPF (Sender Policy Framework) records on your server. SPF is an open standard created to stop forgery of From addresses. Because the majority of spam emails are sent from forged email addresses, SPF records allow the receiver’s host to verify that the email is being sent from the server it asserts it’s sent from. It’s like the email sender is telling to the receiver “I send emails from this computer only”. So, if any other machine tries to send an email from the same domain, the receiver’s mail server knows the From email address is forged. SPF standard is being used by a number of ISPs (including several large providers such as Hotmail, Yahoo, AOL, etc.) and mail hosts. Email senders will need to correctly setup SPF records for their domains if they want their messages to be accepted by those providers. You can ask your hosting company to setup SPF records for you. Or, if you have access to your cPanel, you can do this yourself without your hosting company’s help. Just go to your cPanel and click on Email Authentication. Then enable the authentication parameter you would want to apply to your emails.
  • Enable Reverse DNS on your mailhost. This is another way to authenticate the email sender to the receiver host. Reverse DNS lookup implies determining what host and domain name belong to a given IP address. If a Reverse DNS Lookup returns a “no domain associated”, then the email will likely bounce to the sender, or will be deleted or filtered. To avoid Reverse DNS Lookup problems, follow these simple rules: 1) don’t send emails directly from your home computer (always use an SMTP server when possible) and 2) don’t send emails from a crappy shared hosting server for a small fee monthly fee. Get a solid host, better yet a VPS (virtual private server) or a dedicated server and ask your hosting company to enable Reverse DNS for you.
  • Set up DomainKeys. This is the next step to do after you setup your Reverse DNS records. According to Wikipedia “DomainKeys is an e-mail authentication system designed to verify the DNS domain of an e-mail sender and the message integrity”. In other words, DomainKeys authentication system checks if the email is really sent from the domain it claims to be sent from. By installing DomainKeys you can help your server deliver your emails directly to the recipient’s inbox. DomainKeys authentication was first implemented by Yahoo and it’s now used by Gmail as well. If you don’t have DomainKeys installed, your emails sent to Yahoo and Gmail addresses will be the subject of a more thorough filtering.

In fact, if you have SPF records, Reverse DNS and DomainKeys setup, this is enough to get your email delivered to the recipient. However, you may also want to setup your Sender ID.

The Sender ID is an email authentication technology that validates the origin of email messages by verifying the sender’s IP address against the supposed owner of the domain the email is sent from. The Sender ID authentication algorithm addresses the problem of forging email messages headers by verifying the domain name from which the emails are sent.

Quick Tip: In addition to your test email addresses on AOL, Hotmail, Yahoo, and Gmail, include this email address into your test group – check-auth2@verifier.port25.com. This is a free authentication verifier service that allows email senders perform a simple check of various email authentication mechanisms. A detailed report will be sent you via email so you will have a clear understanding which email authentication parameter succeeded and which failed. Return Path also provides a test similar to the above email verification service. But it provides you with a one time random email address that you suppose to send an email to. A random email address is auto-generated when you visit the website http://senderid.returnpath.net/how.php. Unlike the verifier.port25.com service, you won’t get the test results automatically. After your email is sent, you will need to click on “View Sample” button on the same web page to get the results.

By implementing the above steps you will ensure your email will pass the ISP’s authentication system and increase your email deliverability rate. On the screenshot below you can see a report from Return Path after verifying email sender authentication records.

sender authentication result for bulk email campaign

The steps listed above will absolutely help but they still may not be enough. There are a few more things you can do to build your email sender reputation and improve your email campaign performance:

  • Check your mail server’s IP address against DNS based blacklists every few email campaigns. You can use the MX Lookup tool to see if your server’s IP address is blacklisted. If it is, there is nothing wrong with emailing to the admins of those sites and ask them how you can be removed from the blacklist. 
  • Sign up at email deliverability services. These services work as whitelists and ensure the email delivery to the recipient. When you sign up, your server’s IP address is included into their database. The ISPs check those databases, and if your IP is found there, your email is delivered. Only note that the email deliverability services are not free. They charge a monthly fee or the fee is based on the quantity of sent emails.
  • Whitelist your server with ISPs. Large ISPs have a procedure you can follow to facilitate the delivery of your email messages directly to the subscriber’s Inbox and not to the bulk email folder. The bad thing is that the ISP may not whitelist you if you are using a shared mail server. Even the host owning the mail server may come into troubles with getting the server whitelisted if shared accounts are in use. The experience shows that in order to send the emails as reliably as possible, email marketers should use a dedicated mail server and implement all the steps I described above. And the final thing to do is to follow the ISP whitelisting procedure. There is also a concern about the quantity of emails sent at a time. ISPs tend to meter incoming emails and accept only a certain number of messages per hour. Gone are the days when it was possible to continuously blast thousands of messages. Now the emails should be metered to leak over time.
  • Signup for Feedback Loop programs with ISPs. Those are free programs provided by major ISPs to help email senders improve the delivery of email messages to their recipients. When a user receives a message from a sender enrolled in the Feedback Loop program and clicks on the Report Spam button on the message instead of clicking on your unsubscribe link, a feedback report for each spam complaint is sent to the email sender. Why is it useful?

    It lets you know there is something wrong with your email (off topic, unreadable, etc.) so that one of your subscribers clicked the spam button on it. A spam complaint is a valid reason for you to immediately remove that person from your list. Remember, by clicking on the "Report Spam" button the recipient does not unsubscribe. They will still receive your emails until you manually unsubscribe them. So, to avoid more spam complaints in the future, you’ll want to remove them immediately.

    You can read more about Feedback Loop programs here
    http://website.email-ethics.com/feedback-loops

  • Do not change your mail server’s IP address without any evident reason for it. Some ISPs are more cautious to new IP addresses and restrict the amount of emails that can be sent from a new IP address.
  • Do not change your “From” email address without need. The recipients have already used to your From field and probably added your From email address to their whitelists. Sending from a new email address may make them think it is spam and hit “Report Spam” button or just delete your email message. If you are forced to change your From email address, consider sending a short notification to your subscribers before the change takes place. This way, they can update your records in their address books or whitelists and your future emails will more likely to be received in the Inbox.
  • Do not send the first welcome email in HTML. It’s better if you send your welcome message in plain text format and after your subscribers whitelist you, you can email your regular newsletters in the HTML format. Plus, some email services (AOL, Yahoo, Hotmail and Gmail) do not display images in a HTML email until the recipient loads them. So, consider compiling your welcome email in the text format and include the instructions how to whitelist you in order the recipient could receive your regular HTML email newsletters into the Inbox. If you’re looking for an easy way to build your own mailing list, our Double Opt-In Manager widget is exactly what you need. Using this plugin you can place the signup form at the side bar on your WordPress blog and let people subscribe to your newsletter using a double opt-in method. The plugin will automatically send a welcome email in the plain text format to every new subscriber proving them with the instructions how to whitelist your email address. The subscribers will be saved to your internal WordPress database and you will be able to export them for using in your email marketing software.  

To conclude, keep in mind that nowadays the sender’s reputation question is timely as never before. It’s easy to fool anti-spam filters using some tricks but it’s not easy to restore your good name. Your email sender’s reputation determines the success of your mailings so put your efforts to create a good picture of yourself.

 

Your copy of the "Coding HTML Email: Tips, Tricks and Best Practices" is waiting

Just fill out the form below and we’ll deliver it INSTANTLY! You will also be notified when new articles are posted here.


You can leave the list at any time. Removal instructions are included in each message.

 

Please, share your thoughts in comments below.

  • Digg
  • del.icio.us
  • Reddit
  • Sphinn
  • StumbleUpon
  • Slashdot
  • Technorati
  • Propeller
  • Google Bookmarks
  • Facebook
  • MySpace
  • LinkedIn
  • email
  • PDF


Related posts

5 Responses to “Sender Authentication – How To Get Emails Delivered”

  1. Ant says:

    As I understand it , sending DomainKeys compliant email requires the email server itself to digitally sign each sent message – is it possible that future releases of G-Lock Easymail will contain this functionality for direct senders?

    • Julia says:

      @ Ant,

      G-Lock EasyMail v6 already provides you with the ability to sign the emails with DomainKeys signature. See DomainKeys Signature tab in the Account settings. But since this is a DNS based authentication, you need to have access to your DNS in order to write Public Key there.

  2. [...] Some technical issues such as incorrectly formatted message headers, no reverse DNS, PTR records setup, or authentication errors can lead to email delivery challenges and can cause the emails being filtered or blocked by ISPs. They seem to be serious problems but in fact they are easy to correct. You just need to contact your IT staff, or your server administrator, or your hosting service, or your ISP and notify them about the problem you encountered. Generally, it doesn’t take much time to correct the issue. Here you can read more about how to deal with technical sending issues and get your emails delivered. [...]

  3. kevin says:

    Is MTA a good tool to deliver emails? Especially when we are trying to send over 25,000 contacts per day?

  4. Lucinda from franking machine says:

    Great info here, thanks… 1 question though,

    If I simply don’t have the time to check through all this due to other work commitments, is using constant contact, or aweber a good move, or not?

    If so, any ideas who is best? I think both offer a free trial but I would love an experts opinion on this!!!

Leave a Reply

Rules: Enter Your Name@Your Keywords (example: Julia@Fast Blog Finder) into the Name field and KeywordLuv will use Your Keywords as the anchor text. No inappropriate or offensive comments. No links to inappropriate or offensive sites. Comments must contribute to the discussion.


This site uses KeywordLuv. Enter YourName@YourKeywords in the Name field to take advantage.