You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Sometimes email notifications or invitations from Atlassian Cloud services (Jira, Confluence, Bitbucket, Trello, and more) may not deliver correctly. Here we’ll go over creating a Mail Flow rule in Exchange Online to ensure emails from Atlassian don’t get stuck. This article is intended for anyone using Office365, Exchange Online, or Outlook as part of an O365 tenant.
This rule should help prevent emails from bouncing or an address from getting blocked. Particularly, if Atlassian Support has helped remove an email address from the “block list” or “bounce list” and mentioned this error:
550: 550 5.4.1 Recipient address rejected: Access denied.
An Exchange Admin user will need to complete the following steps:
Log in to Exchange Admin Center, and click on the Rules link in the Mail flow section. Click here for a direct link
Click the + icon to create a new rule, and choose Bypass spam filtering… from the list
Enter the name for the rule in the Name field. Suggestion: “Atlassian Cloud”
In the “apply this rule if” dropdown, select “A message header > includes any of these words”
and type Authentication-Results for the header, followed by dmarc=bestguesspass and dmarc=pass for the values. DMARC is an important anti-spoofing authentication mechanism, and this step ensures only validated emails get processed by the rule.
Click the add condition button to add another condition
For the second condition, select “The Sender’s domain is…” and add atlassian.net and atlassian.com
Alternatively, you can use the IP ranges published on the Outbound Email section of our IP addresses and domains list. Microsoft’s documentation notes that the domain name is preferable to IP addresses.
Confirm the “Stop processing more rules” box is checked. This box is checked by default.
(completed rule shown here - click image to expand)
Save the rule!
If you have other transport or mail flow rules set up, reprioritize this rule to take precedence before other rules.
Why this is necessary
If you are currently not receiving emails or invitations from Atlassian Cloud, it is possible your email address is on the bounce list. Our mail delivery service keeps track of addresses which have returned error codes. Office365 and Exchange Online in particular will return an error code to our mail service if the SCL at your organization exceeds a certain level. Our mail service will then pause delivery of future emails to that address, in order to stay in good standing with spam prevention lists. While the mail flow rule above will fix this particular error for future emails, you may need to contact Atlassian Support to remove your email address from the bounce list. You can do this by raising a support issue if you are an Atlassian Site Admin, or by creating a new question on Community and requesting to be unblocked.
This rule (using the atlassian.net and atlassian.com domains) will not cover messages sent if you have configured Jira Cloud to send emails on behalf of your domain . If Jira is sending emails using your organization's domain name, please follow the documentation to ensure you have set up SPF and DKIM records set up correctly on your domain. Jira will then be able to send emails that pass DMARC, and any mail flow rules you want to add for those emails should use your organization's domain.
613 accepted answers