How Jira handle custom sender email notification: lesson learn and some advices

[Chiara Squilloni]

Hi all,

I want to share my experience by customize the email used by jira to send email notifications.

As you know jira create a default email that is used to send notifications for jira users (obviously always following the rules of the notification scheme).

This could be fine but I prefer to use an email with our company domain, also because I have colleagues with different backgrounds who use jira for very different reasons and receive an email outside our company domain can cause confusion.

So, I follow the steps contained in this article: 

https://support.atlassian.com/organization-administration/docs/what-are-the-steps-for-setting-up-custom-email-addresses/

and all goes well, also because I had alredy registered my domain in order to manage my users. Than I chose this email in some projects in order to test this change.

At first I see notifications, but after one day some collegues point out that they din't recieve the notifications. So I roll back to default jira email and than notifications came back again.

At first I thought it was my mistake and contacted Atlassian support, but testing it with another Jira administrator he recieved the notifications also with my email domain!

So I deeply investigate and I find out that the email used by jira is not the company email, but from the domain @atlassian-bounces.mycompany.it.

Our antispam filter blocked the emails and because of this the notifications stop working. I solved asking to put this email in the white list.

If I could make a wish, I would prefer that there was a secure connection (for example Oauth2.0) with the inbox and that this was actually used for sending notifications, also to have traces of sent emails in the inbox.

Sometimes I miss the server version and the ability to choose settings with greater detail and control.

Hope that these experience helps others administrators!

[Krista Stellar]

Thanks so much for sharing your experience.

I was aware that these email notifications would not actually be sent by the custom domain, but having the specific sender details is very useful and a key part of the configuration so that organizations can PROACTIVELY confirm their corporate spam filters will not choke on these emails.

I do like your suggestion, I wonder if there is a feature request for such a change?

[Kirstin Seidel-Gebert]

Today, we got notified by Atlassian via a banner that we need to re-authenticate our mail server because they are switching to OAuth 2.0 with Microsoft.