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

non-ASCII characters incorrectly encoded in field "From:" in emails

XMLWordPrintable

      From version 3.0.0 onward, JIRA enters actual user as sender in the email notifications (instead of using a predefined e-mail address). This means that sender field can now contain non-ASCII characters, as user's "fullname" is used as the description part of the email address. Unfortunately, the field is encoded incorrectly, as it is always encoded in ISO-646.

      Strangely, the subject field ("Subject:") is correctly encoded in UTF-8... It seems as if somebody forgot to properly encode "From:" field.

      Relevant parts of the e-mail header from JIRA:
      ------
      From: =?ISO646-US?Q?Bo=3Ftjan_Dolenc_=28JIRA=29?= <jira.razvoj@marand.si>
      Subject: =?utf-8?Q?[JIRA]Created=3A=28PE=2D27=29_test_=C5=A1umnikov_v_emailu?=
      To: bostjan.dolenc@Uni-Lj.si
      ------

            [JRASERVER-5176] non-ASCII characters incorrectly encoded in field "From:" in emails

            Dylan Etkin [Atlassian] added a comment -

            The problem was that we were not setting the internetAddress.setPersonal field with the passed in encoding. We now check if we have a non-null encoding and use it to set the field.

            Dylan Etkin [Atlassian] added a comment - The problem was that we were not setting the internetAddress.setPersonal field with the passed in encoding. We now check if we have a non-null encoding and use it to set the field.

            Jeff Turner added a comment -

            I think you're right (system encoding should always equal JIRA encoding) but we'll need to do some investigating before unifying them in JIRA, so I'll leave this issue open for now. Thanks for the report.

            Jeff Turner added a comment - I think you're right (system encoding should always equal JIRA encoding) but we'll need to do some investigating before unifying them in JIRA, so I'll leave this issue open for now. Thanks for the report.

            Deleted Account (Inactive) added a comment -

            After setting -Dfile.encoding it works OK. Maybe you should consider overwriting this property on JIRA startup. I can't imagine a scenario in which those two settings (-Dfile.encoding and "Character Encoding") must have different values.

            Deleted Account (Inactive) added a comment - After setting -Dfile.encoding it works OK. Maybe you should consider overwriting this property on JIRA startup. I can't imagine a scenario in which those two settings (-Dfile.encoding and "Character Encoding") must have different values.

            Deleted Account (Inactive) added a comment -

            Yep, system encoding is set to ISO-646. I though that "Character Encoding" from "General Configuration" pane is used for all encoding purposes... I'll set system encoding to UTF-8 later today - I hope this will take care of the problem.

            Deleted Account (Inactive) added a comment - Yep, system encoding is set to ISO-646. I though that "Character Encoding" from "General Configuration" pane is used for all encoding purposes... I'll set system encoding to UTF-8 later today - I hope this will take care of the problem.

            Jeff Turner added a comment -

            Hi,

            Could you please check what your system encoding is set to? This can be found in Administration -> System -> System Info. If it is not UTF-8, could you try setting it to this by starting JIRA with -Dfile.encoding=UTF-8?

            Jeff Turner added a comment - Hi, Could you please check what your system encoding is set to? This can be found in Administration -> System -> System Info. If it is not UTF-8, could you try setting it to this by starting JIRA with -Dfile.encoding=UTF-8?

              dylan@atlassian.com Dylan Etkin [Atlassian]
              8bcb1553-196a-4cae-9387-2e155042a50a Deleted Account (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: