After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 555659 - Subject line with UTF-8 characters not displayed properly
Subject line with UTF-8 characters not displayed properly
Status: RESOLVED DUPLICATE of bug 442934
Product: evolution
Classification: Applications
Component: Mailer
2.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-10-09 11:20 UTC by Assen Totin
Modified: 2009-08-19 12:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
Screenshot showing the message (152.16 KB, image/png)
2008-10-09 11:21 UTC, Assen Totin
Details

Description Assen Totin 2008-10-09 11:20:23 UTC
We have an email message with subject line, which is partially UTF-8 encoded using standard MIME. The line is shown by Evolution as plain text instead of being decoded and displayed as UTF-8. 

Subject: =?UTF-8?B?0KTQsNC60YLRg9GA0LAg0L3QvtC80LXRgCA=?=0320000671

The UTF-8 part is actually some Cyrillic text. The digits after the =? sign are plain text and should be displayed as plain text. 

The same subject line is handled properly by other email clients (Mozilla Thunderbird and several web mail systems).

An attachment shows what is displayed by Evolution.

WWell,
Comment 1 Assen Totin 2008-10-09 11:21:31 UTC
Created attachment 120260 [details]
Screenshot showing the message

Screenshot showing the subject line in question.
Comment 2 André Klapper 2008-10-09 17:44:20 UTC
Please provide the subject line from the *message source*.
Comment 3 Assen Totin 2008-10-10 07:34:42 UTC
Here is the full message with just some "Received" lines removed and from/to addresses replaced. The attachment also skipped. 

The message is created and sent by the Perl Mail::Sender module; however, the "Subject:" line is encoded and composed by the web page, not by the Perl module (it gets fed to the Perl module as a string).

---

Return-Path: <some-guy@some-company.com>
Received: from some-server.some-domain.com ([unix socket]) by other-server.some-domain.com (Cyrus v2.3.9-Stoko-RPM-2.3.9-7) with LMTPA; Thu, 09 Oct 2008 11:54:19 +0300
To: other-guy@some-company.com
Subject: =?UTF-8?B?0KTQsNC60YLRg9GA0LAg0L3QvtC80LXRgCA=?=0320000671
Date: Thu, 9 Oct 2008 11:53:09 +0300
X-Mailer: Perl script "invoice_send.asp" using Mail::Sender 0.8.13 by Jenda
        Krynicky, Czechlands running on wf.itdnet.net (87.118.150.138) under
        account "apache"
Message-ID: <20081009_085309_099590.some-guy@some-company.com>
MIME-Version: 1.0
Content-type: multipart/mixed; boundary="Message-Boundary-by-Mail-Sender-1223542386"
X-Evolution-Source: imap://some-guy%40some-company.com@mail.some-domain.com/

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--Message-Boundary-by-Mail-Sender-1223542386
Content-type: text/plain; charset="utf-8"
Content-description: Mail message body
Content-transfer-encoding: quoted-printable
Content-disposition: inline

=D0=A4=D0=B0=D0=BA=D1=82=D1=83=D1=80=D0=B0 =D0=BD=D0=BE=D0=BC=D0=B5=D1=80 0=
320000671=
=
--Message-Boundary-by-Mail-Sender-1223542386
Content-type: acro-doc/pdf; name="temp_tex.pdf"
Content-transfer-encoding: base64
Content-disposition: attachment; filename="0320000671invoice.pdf"

------- SKIPPED ATTACHMENT --------

--Message-Boundary-by-Mail-Sender-1223542386--
Comment 4 Akhil Laddha 2009-08-19 12:14:26 UTC

*** This bug has been marked as a duplicate of bug 442934 ***