Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30135

Jira sends emails that result in bounces and it does not deal cleanly with them

    XMLWordPrintable

Details

    • Severity 2 - Major
    • Hide
      Atlassian Update – 11 October 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 11 October 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      We see the following pattern in On Demand:

      An email is sent to JIRA which JIRA is not able to process because the username is not on the system. This is typically due to a mistyped email address in the admin Gui, a message from an autoreply or other automata to JIRA.

      JIRA then replies to that email with a notification that the user is not in the system. When this reply notification hits the On Demand external MX servers, a delivery attempt is made and this fails (eg, if the message was from postmaster@ and the demote system is misconfigured and does not accept postmaster email). This email then bounces and JIRA does not deal with the bounce, leaving it in the mailbox, or worse it generates another notification causing a mail loop.

      Suggested Resolutions:

      • Have JIRA only email an invalid address once
      • Have JIRA set a hashed reply to address to monitor the source of bounces and use it to tie it back to the sent email and disable the user/notify the admin.
        • Note, this will require work from Hosted Infrastructure in order to support

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              gbarnett George Barnett
              Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: