SPF(supported)
DKIM(recommended)
This article covers the SPF and DKIM authentication processes for XCAMPAIGN 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.
Configuring DKIM authentication for your XCAMPAIGN emails
To setup DKIM for your XCAMPAIGN emails, please follow the guidelines below:
In the part of the Help How to set your address for sending - Phishing and Spam Protection
In the Help or using the button to call it up (in case you closed it) there is the section Phishing and Spam Protection.
This section is further divided into three subsections for the TXT records setting for SPF, DKIM and DMARC.
If the setup is not completed without errors, this section is always open. Otherwise, its content can be displayed using the More info. The same applies to individual subsections.
Should it happen that a MX record found in your server’s DNS records does not match the required settings, we will also show you the record found in the DNS records here.
What is necessary to do?
Enter all the listed TXT records into your DNS (Domain Name System) server.
NOTE: If you manage you domain in Valimail, you will need to add the DKIM key/s on your domain's configuration page in the Valimail platform.
How to verify, that you have set up this step correctly, you will learn here.
You can also find the instructions on how to set up DKIM and SPF for XCAMPAIGN, here.
Add an XCAMPAIGN DKIM key in Valimail
You can find more detailed information on how to add a DKIM key in Valimail, here:
Configuring SPF authentication for your XCAMPAIGN emails
Once you establish that XCAMPAIGN 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.