Email Gateway Provider setup for DMARC/SPF/DKIM to handle incoming email from Atlassian
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Purpose
On November 28th 2023, Atlassian decided to make a change to require all emails to pass an SPF or DKIM check to prove they are coming from Atlassian, or they will be they will be sent to your inbox’s spam / junk folder. At present, we have detected that some emails from Atlassian are failing both SPF and DKIM when they go through your mail servers, so they will be dropped when this change is made. They can be failing due to automatic forwarding, or a mail gateway / spam filter that needs to be re-configured. This page is intended to guide you through configuring your mail gateway or spam filter so that it performs the appropriate checks to start receiving emails.
Email Gateway Provider | Documentation Link | Instructions |
|---|---|---|
Office365 | Follow the instructions under the section: * Set up a connector to apply security restrictions to mail sent from your partner organization to Microsoft 365 or Office 365 | |
Google Forwarding Set up an inbound mail gateway Additional Troubleshooting: Troubleshoot DMARC issues | Follow the steps in the section: * Set up an inbound gateway Highly likely you need to enable the "Automatically detect external IP" setting. | |
Ironport | Ironport to Office365 Configure Incoming Email in Microsoft 365 from Cisco Secure Email | Follow the instructions under the section: * Configure Incoming Email in Microsoft 365 from Cisco Secure Email |
Ironport | Ironport to Gsuite Configuring Google Workspace (Gmail) with Cisco Secure Email | Follow the steps in the section: * Configuring Google Workspace (Gmail) with Cisco Secure Email |
Proofpoint | Proofpoint to Office 365 | Follow all instructions on the page |
Proofpoint | Proofpoint to Gsuite Configuring Google Workspace (Gsuite) for Proofpoint Essentials | Follow all instructions on the page |
Mimecast | Mimecast to Office365 | Follow the instructions under the section: * Microsoft 365 |
Mimecast | Mimecast to Gsuite | Follow the instructions under the section: * Google Workspace |
Symantec | Symantec to Office 365 | Follow all instructions on the page |
Symantec | Symantec to Gsuite | Follow all instructions on the page |
Check the Atlassian IP address ranges
Customers who setup and utilize SRS for email forwarding, should take the appropriate steps to ensure their configuration doesn't allow unauthorized access to resources on the forwarding domain.
We encourage you to reach out to your mail administrator, and mail service provider for support if needed. If you need more clarity on this change from Atlassian then please reach out to us at https://support.atlassian.com/contact/.
Was this helpful?