Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-77758

Improvement in the case Atlassian mail sending IP address get blocklisted

    XMLWordPrintable

Details

    • 333
    • 113
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Update as of 3 Aug 2023

      Hello all, 

      Atlassian is focused on the sending reputation of its emails and strives to ensure email deliverability.  However, there is no specific change that can be done to completely prevent any future issues, its an area that requires constant investment which we are actively doing.  As issues occur, we investigate, find how it occurred, and work on preventing that vector.  On top of this, we do proactively work on features to prevent bad actors using our systems, but the specifics of these systems are kept internal.

      There are hundreds of block lists that exist which are all 3rd party controlled and we don't have visibility into their inner workings.  Some can be quite sensitive, and others less so.  We do monitor these, but once an ip is on these lists, there is little we can do to expedite its removal.  All we can do is ensure the bad actors have been stopped on our side, which ensures the ip will fall off the block list after a set time determined by the block list itself.

      The best analogy for this issue is it's like anti-virus software.  There is no anti-virus software that prevents all viruses from now into the future.  It may stop all current threats, but as new ones are found, further updates and changes need to be done to protect the systems.  That's the same as in this case.

      We will continue our efforts in this area and our email deliverability reputation should keep continuing to improve over time.

      Cheers, 

      Michael Baskerville

      EM Messaging

      Problem Description

      We have come across scenarios where our notification sending IP addresses are added in the blocklist and are considered as SPAM. As a result, customers utilising that spam filter disregards our email that falls into that sending IP address range.

      This leads to customers email notifications cannot be received. Getting those IPs delisted from these providers sometimes takes time and till then, the customers do not receive notifications. The only workaround is to whitelist Atlassian IP address range but that is also sometimes not a feasible option.

      Suggested Solution

      Improve the current situation to ensure smooth experience for users/ JSM customers to receive notifications.

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              e87386e27ed9 Simran G
              Votes:
              93 Vote for this issue
              Watchers:
              73 Start watching this issue

              Dates

                Created:
                Updated: