This article covers the SPF and DKIM authentication processes for Smaily 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.

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.

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

Once you establish that Smaily 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.

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.