Configure the SPF protocol with SALESmanago

The SPF (Sender Policy Framework) protocol is an email authentication method used to prevent impersonation by verifying that incoming mail from a domain comes from an authorized IP address. It protects email recipients from phishing, spam, and malware by ensuring that only verified senders can reach their inboxes. 

The SPF protocol is now required by Gmail and Yahoo and so, it became obligatory for SALESmanago customers. Read the article below and configure the SPF protocol for your domain to maintain your ability to send emails to @gmail.com and @yahoo.com addresses.


Contents

  1. Getting started
  2. Quick summary: SPF configuration
  3. Implementing the SPF protocol for your domain
    1. Step 1. Determine where you can edit your DNS settings
    2. Step 2. Find the right place in the DNS settings
    3. Step 3. Add the record for the SPF protocol

1. Getting started

New security challenges and the volume of spam and malicious communications sent worldwide have led two large email clients, Gmail and Yahoo, to impose new requirements on bulk (mass) email senders. The requirements are likely to apply to SALESmanago customers who:

  • use a SALESmanago Email Marketing sender account, or
  • use an External (SMTP) sender account and send (regularly or occasionally) more than 5,000 emails a day.

If you want to learn more about the new authentication requirements, read this article >>

To ensure that the deliverability of its customers is not affected by the new requirements, SALESmanago has made the implementation of SPF, DKIM, and DMARC protocols obligatory. Read the instructions below to learn how to do it.


2. Quick summary: SPF configuration

NOTE: Before implementing the SPF protocol, make sure that you don’t have it in place already. You can use an online tool, such as https://mxtoolbox.com/spf.aspx.

The table below sums up the DNS entry required to implement the SPF protocol. Note that the all flag should be added at the end of the record; the option recommended by SALESmanago is ~all.

Remember that the detail marked in green is just a placeholder and must be replaced with your own data.

ProtocolNameTypeValueTTL
SPFexample.comTXTv=spf1
include:_spf.jupiter.salesmanago.pl ~all
3600

NOTE: If you already have an existing v=spf1 record, simply extend it by adding:

 include:_spf.jupiter.salesmanago.pl

If you have no all flag yet, also add ~all at the end.

Note that flags, including all, should be placed after this part:
include:_spf.jupiter.salesmanago.pl.

You can read more in Section 3, Step 3 below.


3. Implementing the SPF protocol for your domain

The SPF protocol is usually implemented in the DNS (Domain Name System) settings for your domain.

NOTE:

  • The instruction below is of a generic nature. The actual process may look different depending on the eCommerce platform, domain registrar, hosting provider, or CDN provider whose services you use.
  • Before implementing the SPF protocol, make sure that you don’t have it in place already. You will probably be able to check this in the same control/user/configuration panel where you can add a new record – simply review the list of existing records. Note, however, that the SPF record may need updating – see the instructions below.

Step 1. Determine where you can edit your DNS settings

Depending on the way in which your website is set up, consider these four possibilities:

  • E-store set up on a SaaS eCommerce platform (such as Shopify or BigCommerce): Log in to your e-store account and search for DNS settings. For instance, on Shopify, you need to go to Settings → Domains → Domain settings → Edit DNS settings.
  • Domain purchased via a hosting provider (such as OVH or A2 Hosting): Log in to your hosting account and go to the control panel (which can be called “user panel”, “domain configuration panel”, etc).
  • Domain purchased via a domain registrar (such as GoDaddy or OVH): Log in to your domain account and go to the control panel (which can be called “user panel”, “domain configuration panel”, etc).
  • Website served via a Content Delivery Network—CDN (such as Cloudflare): Log in to your CDN account and go to the control panel (which can be called “user panel”, “domain configuration panel”, etc).
    In Cloudflare, go to DNS → Records:

Read more about managing DNS records in Cloudflare >>

NOTE: If you have more than one domain, make sure to select the one you want to configure.


Step 2. Find the right place in the DNS settings

After logging in to the account that allows you to edit your DNS settings, look for the place where you can add records for your domain. This place (section, tab, etc.) can be called, for instance, DNS Settings, Zone Editor, DNS Management, Name Server Configuration, or DNS Record Management.

It is possible that you will see a button like Add TXT record; or you may need to click a button for adding a record and then select the record type from a list. If you can’t find the option to add a record for your domain, consult the help materials of your service provider (eCommerce platform, domain registrar, hosting provider, or CDN provider) or contact their customer support.


Step 3. Add the record for the SPF protocol

To implement the SPF protocol required, you will need to add a TXT record for your domain. When you do so, you will probably see a number of input fields that allow you to define the new record. Pay attention to the three fields described below:

  • Host (Host record, Host name, Name, Domain, etc.)—In this field, enter the name of your domain accompanied by the top-level domain, for example:
    yourcompany.com, yourstore.de, yourecommerce.es
    TIPS:
    • After completing the Host field, you may see that a dot (full stop) was added at its end. Don’t try to delete it—this is a required formatting element.
    • If you are in doubt which field is the Host field, look at your existing records and check which field contains domain addresses.
  • Text value (Main value, Record, Value, Content, etc.)—In this field, enter the following value:
    v=spf1 include:_spf.jupiter.salesmanago.pl ~all
    NOTE: If you already have an existing v=spf1 record, simply extend it by adding:
    include:_spf.jupiter.salesmanago.pl
    and, potentially, also the all flag. The option recommended by SALESmanago is ~all, however, you can also use the other options (-all/?all), depending on your preferences or company guidelines.
    EXAMPLE: Your current SPF entry looks as follows:
    v=spf1 mx include: _spf.google.com -all
    Change it to:
    v=spf1 mx include: _spf.google.com
    include:_spf.jupiter.salesmanago.pl -all
    Note that flags, including all, should be placed after this part:
    include:_spf.jupiter.salesmanago.pl.
  • TTL (Time to Live)—We recommend setting the TTL (Time to Live) to 1 hour (3600 seconds).

At this stage, add the ready record by clicking Save, OK, Done, etc. You don’t need to take any additional steps on the SALESmanago platform. 

IMPORTANT: The SPF protocol will be implemented for your domain within several hours, but it can take up to 24 hours for the changes to become visible in your domain settings (due to a DNS propagation delay).

If you have any questions or doubts concerning the configuration of your email authentication protocols, or if you would like to have your setup verified by our Support specialist, please contact us at: support@salesmanago.com.

If you need more information about the topic mentioned above, please contact us: support@salesmanago.com +1 800 960 0640