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

JIRA email handlers shouldn't process emails with the DELETED flag set

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

      Office365 mail handlers will send you deleted emails to process. Any email that is marked as deleted should not be processed.

            [JRASERVER-38594] JIRA email handlers shouldn't process emails with the DELETED flag set

            Ian Dick added a comment -

            The jira-mail-plugin has been modified so that incoming messages with the DELETED flag set do not get processed. This takes care of the particular situation where an Office365 IMAP server sends JIRA emails that have already been processed by JIRA and marked for deletion but that haven't yet been expunged from the IMAP server yet. Such emails were originally processed twice by JIRA resulting in things like duplicate comments on issues. Now the jira-mail-handler plugin checks for the DELETED flag and ignores email messages with that flag. Unit test coverage was added along with the fix to guard against regressions.

            Ian Dick added a comment - The jira-mail-plugin has been modified so that incoming messages with the DELETED flag set do not get processed. This takes care of the particular situation where an Office365 IMAP server sends JIRA emails that have already been processed by JIRA and marked for deletion but that haven't yet been expunged from the IMAP server yet. Such emails were originally processed twice by JIRA resulting in things like duplicate comments on issues. Now the jira-mail-handler plugin checks for the DELETED flag and ignores email messages with that flag. Unit test coverage was added along with the fix to guard against regressions.

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              idick Ian Dick
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: