All of our projects are set up to use the default notification schema and set to use the following email address: jira@<companyname>.atlassian.net
This was working fine until last week when mails started getting sent from jira@mail-us.atlassian.net which is getting blocked by our email filtering.
It shouldn't be a problem to add jira@mail-us.atlassian.net to our whiltelist but why would this have suddenly changed last week, and why are notification no longer adhering to the schema / project settings?
Kindly check with your Messaging team on this, there could be a chance that company policy (your SMTP Team) might have added a new restriction causing this to be 'not delivered'.
On another case - try sending a test mail (if you're jira admin), and check for the notification testing based on the user action.
Thank you Piyush Annadate. It turns out it was the fault of internal security who had incorrectly blocked this address, thanks for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.