SPF(not supported)
DKIM(recommended)
This article covers the SPF and DKIM authentication processes for Smaily and how they are managed in Valimail Enforce. While only one of the two authentication methods is required for an email to pass DMARC, our recommendation is to configure both whenever possible.
TABLE OF CONTENTS
- Configuring DKIM authentication for your Smaily emails
- Add a Smaily DKIM key in Enforce
- Configuring SPF authentication for your Smaily emails
- Enable SPF alignment in Smaily for your domain
Configuring DKIM authentication for your Smaily emails
To enable DKIM for Smaily, add two CNAME records to your domain's Configuration page in Valimail Enforce:
Selector: blue.smly
Value: blue._dkim.smaily.com
Selector: green.smly
Value: green._dkim.smaily.com
You can then check to see if the DKIM key has been published, using a tool like Google Admin Toolbox Dig.
You can also find the instructions on how to set up DKIM and SPF for Smaily, here.
Add a Smaily DKIM key in Enforce
1. Go to your domain's Configuration page in Valimail Enforce and publish the newly created DKIM key.
a. Scroll down and add the two DKIM keys in your configuration, by clicking on Add a DKIM key.
b. Enter the selector name, CNAME target value, associate the key/s with Smaily and then click Add.
You can find more detailed information on how to add a DKIM key in Valimail Enforce here.
Configuring SPF authentication for your Smaily emails
Once you establish that Smaily is an authorized sender for your domain, you will need to add the service in your Enabled Senders list in Enforce.
1. Please go to your domain's Configuration page in Enforce.
2. Click on the + sign from the Enabled Senders section:
3. Choose Smaily from the list of configurable senders and then click Enable:
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.
Enable SPF alignment in Smaily for your domain
You may notice that Smaily emails are not authenticated via SPF, even after you have added Smaily to your domain's configuration. This is likely caused by Smaily not sending SPF aligned-mail.
After adding SPF and DKIM records to your domain you can check in Smaily, if the records have been correctly added by following the instructions here.
As always, if you have any questions, please don't hesitate to submit a ticket.