Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3627

Emails from an invalid formatted "From" address will stop the mail puller

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

      Summary

      When the mail puller encounters an message in the mail channel mailbox originating from an invalid formatted "From" field, the mail puller will not be able to process that message, and continuously loop on this message, effectively rendering the mail pulling process broken. A correctly formatted looks like "name@domain.extension".
      A known source for this issue is Microsoft Outlook 365, where certain messages originate from "Microsoft Outlook" opposed to a valid email address in the "From" field.

      Steps to Reproduce

      1. Ensure the mailbox configured as mail channel in a Service Desk project contains an email originating from a source which does not provide a valid formatted email address in the "From" field as described in the summary
      2. Have the mail puller pull and process the email automatically

      Expected Results

      The mail gets pulled into the database.
      In this case, it is not relevant for the email to get processed further beyond this point.
      Once the email has been pulled, the mail puller should continue to pull mails from the mail box.

      Actual Results

      The mail puller gets stuck on the incorrect email and will continuously loop on it, instead of moving on to the next mail in the mailbox.
      The atlassian-jira-incoming-mail.log file will display the following error for each attempt to pull the mail in question:

      Unable to create issue with message.
      javax.mail.internet.AddressException: Local address contains control or whitespace in string ``Microsoft Outlook''
      

      Notes

      The relevant message in Microsoft Outlook is an automatically generated one to inform the user of certain changes on the mail platform, or the welcoming message when starting to use the product for the first time. So far, no other mail providers are known to cause similar issues.

      Workaround

      Delete the offending message from the mail box. This will allow the mail puller to proceed from that point onwards.

            [JSDSERVER-3627] Emails from an invalid formatted "From" address will stop the mail puller

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304682 ] New: JAC Bug Workflow v3 [ 3126086 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058594 ] New: JSD Bug Workflow v5 - TEMP [ 2304682 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056033 ] New: JSD Bug Workflow v5 [ 2058594 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956312 ] New: JSD Bug Workflow v5 - TEMP [ 2056033 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1616231 ] New: JSD Bug Workflow v5 [ 1956312 ]
            jonah (Inactive) made changes -
            Description Original: h3. Summary
            When the mail puller encounters an message in the mail channel mailbox originating from an invalid formatted "From" field, the mail puller will not be able to process that message, and continuously loop on this message, effectively rendering the mail pulling process broken. A correctly formatted looks like "name@domain.extension".
            A known source for this issue is Microsoft Outlook 365, where certain messages originate from "Microsoft Outlook" opposed to a valid email address in the "From" field.


            h3. Steps to Reproduce
            # Ensure the mailbox configured as mail channel in a Service Desk project contains an email originating from a source which does not provide a valid formatted email address in the "From" field as described in the summary
            # Have the mail puller pull and process the email automatically

            h3. Expected Results
            The mail gets pulled into the database.
            In this case, it is not relevant for the email to get processed further beyond this point.
            Once the email has been pulled, the mail puller should continue to pull mails from the mail box.

            h3. Actual Results
            The mail puller gets stuck on the incorrect email and will continuously loop on it, instead of moving on to the next mail in the mailbox.
            The atlassian-jira-incoming-mail.log file will display the following error for each attempt to pull the mail in question:
            {code}
            Unable to create issue with message.
            javax.mail.internet.AddressException: Local address contains control or whitespace in string ``Microsoft Outlook''
            {code}

            h3. Notes
            The relevant message in Microsoft Outlook is an automatically generated one to inform the user of certain changes on the mail platform, or the welcoming message when starting to use the product for the first time. So far, no other mail providers are known to cause similar issues.

            h3.Workaround
            Delete the offending message from the mail box. This will allow the mail puller to proceed from that point onwards.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-3627].
              {panel}

            h3. Summary
            When the mail puller encounters an message in the mail channel mailbox originating from an invalid formatted "From" field, the mail puller will not be able to process that message, and continuously loop on this message, effectively rendering the mail pulling process broken. A correctly formatted looks like "name@domain.extension".
            A known source for this issue is Microsoft Outlook 365, where certain messages originate from "Microsoft Outlook" opposed to a valid email address in the "From" field.


            h3. Steps to Reproduce
            # Ensure the mailbox configured as mail channel in a Service Desk project contains an email originating from a source which does not provide a valid formatted email address in the "From" field as described in the summary
            # Have the mail puller pull and process the email automatically

            h3. Expected Results
            The mail gets pulled into the database.
            In this case, it is not relevant for the email to get processed further beyond this point.
            Once the email has been pulled, the mail puller should continue to pull mails from the mail box.

            h3. Actual Results
            The mail puller gets stuck on the incorrect email and will continuously loop on it, instead of moving on to the next mail in the mailbox.
            The atlassian-jira-incoming-mail.log file will display the following error for each attempt to pull the mail in question:
            {code}
            Unable to create issue with message.
            javax.mail.internet.AddressException: Local address contains control or whitespace in string ``Microsoft Outlook''
            {code}

            h3. Notes
            The relevant message in Microsoft Outlook is an automatically generated one to inform the user of certain changes on the mail platform, or the welcoming message when starting to use the product for the first time. So far, no other mail providers are known to cause similar issues.

            h3.Workaround
            Delete the offending message from the mail box. This will allow the mail puller to proceed from that point onwards.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-3627 [ JSDCLOUD-3627 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server New: affects-cloud affects-server
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1603439 ] New: JSD Bug Workflow v4 [ 1616231 ]

              Unassigned Unassigned
              mnassette MJ (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: