JIRA's mail handler does not properly parse group email addresses

XMLWordPrintable

    • 8
    • Severity 3 - Minor

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

      If a catch email is specified as part of a group address (http://www.ietf.org/rfc/rfc2822.txt section A.1.3) JIRA does not parse it.

      Three scenarios exist here:

      1. Catch email exists before the group:
        To: "John Smith" <catchemail@example.com>,
                Web Support: "Web Support minor" <minorsupport@example.com>,
                "WebSupport Major" <majorsupport@example.com>;
      2. Catch email exists after the group:
        To: Web Support: "Web Support minor" <minorsupport@example.com>,
                "WebSupport Major" <majorsupport@example.com>;,
                "John Smith" <catchemail@example.com>
      3. Catch email exists within the group:
        To: Web Support: "Web Support minor" <minorsupport@example.com>,
                "WebSupport Major" <majorsupport@example.com>,
                "John Smith" <catchemail@example.com>;

      Scenarios 1 and 2 result in a properly parsed email.
      Scenario 3 results in a "do not match the catch email" error.

      Expected: Scenario 3 should be parsed without issue.

      Steps to repro:

      1. Download the ingroup.eml file and place it within the <JIRA HOME>/import/mail folder
      2. Add a new mail handler, and specify the local directory instead of a POP/IMAP server
      3. Specify the catch email to be:
        catchemail@example.com
      4. Set a default assignee, and test the connection, click on More Details
      5. Error is:
        Found 1 message(s) in the <JIRA HOME>/import/mail folder.
        Cannot handle message as the recipient(s) (Web Support: "Web Support minor" <minorsupport@example.com>, "WebSupport Major" <majorsupport@example.com>, "John Smith" <catchemail@example.com>;) do not match the catch email catchemail@example.com

            Assignee:
            Oliver Hookins (Inactive)
            Reporter:
            Boris Berenberg (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: