In This Article:

    Email Authentication - Make Sure Emails Can Get to Supporters

    In This Article:

      Email service providers (like Gmail) include security to enable email recipients to know who is sending a given email. The intent is to prevent spoofing, which occurs when one sends an email that appears to come from one source but actually comes from another. This is a common practice used by spammers to trick people into opening, reading, and clicking emails.

      This information is usually hidden in the headers of an email (code you don’t normally see but which tracks the journey of an email). Email service providers have begun to add “via” information to show who is actually sending the email. So even though your blasts is be coming from xyz@yourorg.com, the email service provider will show that the messages are being sent by Salsa Labs.

      Here's an example of what this looks like in a Supporter's inbox:

      example.png

      This will no longer appear to the email recipient once the email service provider concludes that the email recipient actually wants to receive messages from the sender.

      For example, if the supporter replies to a message or adds your address to their address book, Gmail (or any other email service provider) will conclude that the supporter actually wants to hear from you.

      This is another reason why you (as an email sender) need to make sure all emails have some sort of action to them. Engage your supporters so they can prove to email service providers that they're interested in what you have to say.

      If you don't have an SPF record set up when you add an email address to the "Sent From" field for a Salsa Engage Email Blast, Salsa Engage will prompt you with a warning.

      Never use the following domains for your "From" email address:

      • Gmail.com
      • Hotmail.com
      • AOL.com
      • Yahoo.com

      Many email clients automatically block emails from these domains or send them directly to spam. To ensure deliverability, these domains should not be used in the senders ("From") address.

      What You Can Do - Set Up a Sender Policy Framework (SPF) Record

      Email service providers check several ways to see if a message is authentic, but the easiest road to authentication is to set up an SPF record. SPF records verify that email senders (like Salsa) have permission to send email on your behalf.

      Salsa staff cannot set this up for your organization - you'll need to work with your IT staff. If you are using Bluehost or Godaddy, they host helpful articles on setting up an SPF record:

      • Click here for GoDaddy
      • Click here for BlueHost

      Note: Before you begin, make sure you have the ability to add a TXT entry to your DNS records.

      Once you've made your SPF updates, enter your domain at https://mxtoolbox.com/spf.aspx to confirm that the changes have worked. The following example illustrates what you'll see (in MxToolbox) when you've set up your SPF correctly.

      00000022.png

       

      A Few Tips About Adding Your SPF Record (for IT professionals)

      Implementation

      • To add a new SPF record...
        • The format varies between various DNS platforms - please consult your specific documentation for instructions to enter an SPF record as a TXT record. It should look similar to yourdomain.org TXT "v=spf1 mx include:salsalabs.org ~all"
      • To update an existing SPF record...
        • Insert include:salsalabs.org into your current configuration, just before the "all" mechanism. This tells the SPF record requestor to look up the record for salsalabs.org and include that information in the organization's SPF response.

      Syntax

      Below is a typical SPF record and a breakdown of what each component of the SPF string does.

      "v=spf1 mx include:salsalabs.org ~all"

      • v=spf1 means SPFv1 or SPF Engage, the current version of SPF. This identifies the TXT record as an SPF string.
      • mx is a mechanism indicating that the incoming mail servers for your domain are also permitted to send mail.
      • include:salsalabs.org is a mechanism indicating any server permitted to send mail from salsalabs.com may also send mail from your domain.
      • ~all means that all other mail not explicitly permitted by the rest of the SPF record can be accepted but will be marked for greater scrutiny.

      Whitelisting

      Hosted Providers

      If you are using hosted tools, such as Ms Office 365 or MS Outlook, white list IP range 204.28.10.0/23.

      Supporters

      On email signup forms, ask supporters to be sure to whitelist your emails with their email service provider and to check spam if they don't hear from you.

      Was this article helpful?
      0 out of 0 found this helpful
      Have more questions? Submit a request

      Comments

      0 comments

      Please sign in to leave a comment.