Bug 9476 - bugs.mageia.org mailing list puts XX in place of accented characters in sender field
Summary: bugs.mageia.org mailing list puts XX in place of accented characters in sende...
Status: RESOLVED FIXED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-21 19:22 CET by andré blais
Modified: 2017-04-16 02:37 CEST (History)
6 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description andré blais 2013-03-21 19:22:50 CET
Description of problem:
In the sender field, the bugs.mageia.org mailing list puts XX in place of accented characters in the sender field.
This probably applies to all utf8 characters.

This problem did not yet occur for emails sent 2012-10-22, but applies to emails sent starting 2012-12-31

This problem does not occur in other Mageia mailing lists, so assume that this is a problem with bugzilla.
Note that the associated bug reports themselves show the corresponding accents correctly (in the reporter or commentor field).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Visible in every email from bugs.mageia.org since 2012-12-31, in the sender field, if the users' name contains any accents.
e.g. "FrXXdXXric Buclin" instead of "Frédéric Buclin"

Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-03-23 13:25:54 CET
I see your name and them from Frédéric with the correct spelling. This is in thunderbird. Are you sure it's not a your side issue ?
Comment 2 Samuel Verschelde 2013-03-23 13:46:31 CET
I can confire the issue (using kmail here)

From: "andrXX blais" <bugzilla-daemon@mageia.org>
Comment 3 andré blais 2013-03-23 15:04:18 CET
I use seamonkey for email, essentially identical to thunderbird.
I see the same problem if I access my email via the web instead of POP3.

Maybe it is an issue with how bugs.mageia.org interacts with laposte.net ?

Note that laposte.net is an email service for the francophone world, so accents are common, and that only the bugs.mageia.org list is affected.
Other mageia mailing lists (dev, discuss, doc-discuss, qa-discuss) are correct.
Comment 4 Marja Van Waes 2013-03-23 20:57:18 CET
For me, in Thunderbird, Frédéric and André are shown correctly.

However, the Å of MichaÅ Wernicki and the à of Ãric Barrat are shown as white question marks on a black diamond

In the sources I see

From: "Micha� Wernicki" <bugzilla-daemon@mageia.org>
From: "�ric Barrat" <bugzilla-daemon@mageia.org>
From: "andré blais" <bugzilla-daemon@mageia.org>
From: "Frédéric Buclin" <bugzilla-daemon@mageia.org>

but there are *warnings*:

X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C5 hex):
	From: "Micha\305\202 Wernicki" <bu[...]
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C3 hex):
	From: "\303\211ric Barrat" <b[...]
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C3 hex):
	From: "Fr\303\251d\303\251ric Buclin"[...]
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C3 hex):
	From: "andr\303\251 blais" <bugzi[...]

CC: (none) => marja11

Marja Van Waes 2013-03-24 00:03:33 CET

CC: (none) => LpSolit

Comment 5 andré blais 2013-03-24 05:51:52 CET
I see what is happening :

The bugs.mageia.org list is encoding the headings as utf-8, without specifying the encoding, and laposte.net is replacing the utf-8 code outside the ascii range with X.  So those using laposte.net see X in place of accents.

Other email servers are not replacing the utf-8 encoding, so email agents such as thunderbird or kmail are able to correctly display the utf-8.

The error messages that Marja sees seem to be generated by Mageia, and are passed by laposte.net because they aren't in the sender field.
(I see them in the source as well)

Other mageia mailing lists use encoding as follows :

acute accent in dev list :
From: =?ISO-8859-1?Q?Pierre-Malo_Deni=E9lou?= <pierre-malo.denielou@rhul.ac.uk>

chinese characters in dev list :
From: =?GB2312?B?zfW17r34?= <1132321739qq@gmail.com>

arabic letters in discuss list :
From: =?windows-1256?B?x+Hj08fh4yDH4ePTx+HjyQ==?=
	<almusalimalmusalimah@gmail.com>

The encoding is explicitly specified, so laposte.net accepts it and properly displays the accented characters

So I expect that the solution is to specify utf-8 encoding if it applies ?
Frédéric "LpSolit" Buclin 2013-03-24 14:11:35 CET

Status: NEW => ASSIGNED
Assignee: sysadmin-bugs => LpSolit

Comment 6 Frédéric "LpSolit" Buclin 2013-03-24 14:33:39 CET
I emailed dmorgan a fix for the Mageia extension. It fixes the problem for me using Thunderbird. Up to him to install the updated extension.

Assignee: LpSolit => dmorganec

Comment 7 Frédéric "LpSolit" Buclin 2013-04-08 18:03:05 CEST
dmorgan: ping? Did you update the Mageia extension?
Comment 8 Marja Van Waes 2014-07-20 11:07:15 CEST
The warning is still there:
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C3 hex):
	From: "Atilla \303\226NTA\305\236" <bugzil[...]
<snip>
Tue, 15 Jul 2014 22:15:08 +0200 (CEST)
From: "Atilla �NTA�" <bugzilla-daemon@mageia.org>


The others show fine here, in spite of the warning:

X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C3 hex):
	From: "Fr\303\251d\303\251ric Buclin"[...]
<snip>
Sun, 20 Jul 2014 00:52:25 +0200 (CEST)
From: "Frédéric Buclin" <bugzilla-daemon@mageia.org>
Comment 9 Rémi Verschelde 2014-07-20 13:30:55 CEST
CC'ing Colin, he solved a similar issue with git commit hooks in #12374.

CC: (none) => mageia, remi

Comment 10 Frédéric "LpSolit" Buclin 2015-11-29 21:17:47 CET
This problem is fixed in Bugzilla 5.0.2.
Comment 11 Frédéric "LpSolit" Buclin 2017-04-15 14:49:55 CEST
Problem fixed, AFAIK.

Status: ASSIGNED => RESOLVED
Assignee: dmorganec => sysadmin-bugs
Resolution: (none) => FIXED

Comment 12 andré blais 2017-04-16 02:37:45 CEST
It was fixed for me since 2014-11-21 or before.
Still saw error 2014-09-27

Note You need to log in before you can comment on or make changes to this bug.