This article covers the SPF and DKIM authentication processes for Atlassian Cloud 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 Atlassian Cloud emails
- Add an Atlassian Cloud DKIM key in Enforce
- Configuring SPF authentication for your Atlassian Cloud emails
Configuring DKIM authentication for your Atlassian Cloud emails
In order to enable DKIM signing for your domain, you will need to add the following two CNAME records in your DNS.
s1._domainkey IN CNAME s1._domainkey.atlassian.net.
s2._domainkey IN CNAME s2._domainkey.atlassian.net.
Important: If you manage DKIM for your domain in Valimail, you will need to add the 2 CNAME DKIM keys on your domain's Configuration page in Valimail Enforce.
You can also find the instructions on how to set up DKIM and SPF for Atlassian Cloud, here.
Add an Atlassian Cloud DKIM key in Enforce
Configuring SPF authentication for your Atlassian Cloud emails
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.