• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Email - Incoming
    • None
    • 0
    • 4
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem definition

      Emails with MIME header that do not comply to the RFC2046 convention will be rejected by the Service Desk incoming mail handler.

      • There was an error reading the body of email message. will be seen in the Processing log for the rejected email.
      • Error below appears in the atlassian-jira.log
        2017-08-28 09:17:06,643 Caesium-1-3 WARN admin@atlassian.com     [c.a.s.i.feature.emailchannel.IncomingEmailParser] Error processing email message
        java.io.IOException: Unknown encoding: 7-bit
        	at javax.mail.internet.MimePartDataSource.getInputStream(MimePartDataSource.java:115)
        	at com.sun.mail.handlers.text_plain.getContent(text_plain.java:80)
        	at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:795)
        	at javax.activation.DataHandler.getContent(DataHandler.java:542)
        	at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:657)
        ...
        

      Suggestion

      Better approach to handle emails with invalid header

      Notes

      The cause of the issue is that the mail server is sending emails with an invalid encoding which cannot be processed by javamail. The workaround is to change the mail server settings to send base64 or binary encoded emails to the Service Desk email channel.

            [JSDSERVER-5423] Error processing incoming email - Unknown encoding: 7-bit

            Atlassian Update – 18 January 2022

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Data Center & Server

            Charlie Marriott added a comment - Atlassian Update – 18 January 2022 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Data Center & Server

            mchrastny added a comment - - edited

            It's no exatctly Atlassian issue. It's Java behaviour. Workaround is possible by changing Java enviroment settings.

            /opt/atlassian/jira/bin/setenv.sh

            add to JVM_REQUIRED_ARGS  -Dmail.mime.ignoreunknownencoding=true

            https://docs.oracle.com/javaee/6/api/javax/mail/internet/MimeUtility.html#decode(java.io.InputStream,%20java.lang.String)

            mchrastny added a comment - - edited It's no exatctly Atlassian issue. It's Java behaviour. Workaround is possible by changing Java enviroment settings. /opt/atlassian/jira/bin/setenv.sh add to JVM_REQUIRED_ARGS  -Dmail.mime.ignoreunknownencoding=true https://docs.oracle.com/javaee/6/api/javax/mail/internet/MimeUtility.html#decode(java.io.InputStream,%20java.lang.String )

              Unassigned Unassigned
              michin Michelle Chin
              Votes:
              8 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: