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

Notifications from filter shares may be blocked due to SPF fail

XMLWordPrintable

      Summary

      When sharing a filter (not a ticket) in Jira, the email header will contain the following Return-Path:

      Return-Path: <bounces+something@201701confluence.atlassian.net>

      The Return Path's domain is 201701confluence.atlassian.net and this is what SPF uses to check. That domain is not the same used in other basic notifications in Jira, which is mail-us.atlassian.net.

      The domain 201701confluence.atlassian.net is not configured to accept some of the IPs used by Jira Cloud, so it gets a HARD FAIL for SPF and those messages may be rejected, depending on email server configuration.

      Environment

      • Cloud

      Steps to Reproduce

      Go to issues and filters > Click to share any filter

      Expected Results

      The email will be sent and the domain in 'Return Path' will be the same as in other notification messages.

      Actual Results

      The email is being sent but with '201701confluence.atlassian.net' domain as Return Path and may be blocked.

      Workaround

      • For now, we don't have yet a workaround for this issue.

        1. image-2019-05-25-19-27-33-812.png
          image-2019-05-25-19-27-33-812.png
          28 kB
        2. Screen Shot 2019-05-24 at 16.48.27.png
          Screen Shot 2019-05-24 at 16.48.27.png
          184 kB
        3. Screen Shot 2019-05-24 at 17.02.08.png
          Screen Shot 2019-05-24 at 17.02.08.png
          94 kB

            [JRACLOUD-72132] Notifications from filter shares may be blocked due to SPF fail

            Carl Pritchett (Inactive) added a comment -

            ohookins@atlassian.com The filter share is the old Jira share not the new common share component, thus this is not going through the new share pipeline to Notifications Platform. The new share component looks different and it's icon looks like a circle node connecting to two other circle nodes.

            I suspect this is is a misconfiguration  of the path from the old share to the mail sending code in Jira. abadea@atlassian.com may have an idea where this is configured, or could quickly find out.

            The new common share component looks like the following image:

              

             

            Carl Pritchett (Inactive) added a comment - ohookins@atlassian.com The filter share is the old Jira share not the new common share component, thus this is not going through the new share pipeline to Notifications Platform. The new share component looks different and it's icon looks like a circle node connecting to two other circle nodes. I suspect this is is a misconfiguration  of the path from the old share to the mail sending code in Jira. abadea@atlassian.com may have an idea where this is configured, or could quickly find out. The new common share component looks like the following image:     

              Unassigned Unassigned
              laguirre Lucas Aguirre (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: