This article covers the SPF and DKIM authentication processes for eSputnik and how they are managed in Valimail. While only one of the two authentication methods is required for an email to pass DMARC, our recommendation is to configure both whenever possible.

This option may be required if you want to make your messages as beautiful as possible and do not want to have eSputnik reference in the header of the email. So that Google and other email systems believe that mailed-by: domain.com.

As for the "Simple" version, you need to enter 2 lines in the DNS - SPF and DKIM:

This option may be required if you want to make your messages as beautiful as possible and do not want to have eSputnik reference in the header of the email but you want to separate campaigns from your main domain.

As a solution eSputnik recommends to organize emailing from the subdomain of your domain.

eSputnik service will process all the emails arriving at this subdomain.

Such messages will look “almost like” yours. But they are not from your domain domain.com, they are from the subdomain, for example, promo.domain.com.

In this case you add three entries to your DNS domain settings: DKIM, SPF and MX.

NOTE: If you manage you domain in Valimail, you will need to add the CNAME DKIM key on your domain's configuration page in the Valimail platform and any other record will go in your DNS.

Also, you will need to add eSputnik in your Enabled Senders list in Valimail.

You can also find the instructions on how to set up DKIM and SPF for eSputnik, here.

You can find more detailed information on how to add a DKIM key in Valimail, here:

Once you establish that eSputnik is an authorized sender for your domain, you will need to add the service in your Enabled Senders.

You will find more detailed information on how to add a service for your domain in Valimail, here:

Note: We encourage you to use the comment section for any useful information about your sending service, such as the name of the service owner, change request ticket numbers, etc.