Description of problem: I just imported hitori. I used the spec file from Fedora. In the description Fedora used the following UTF-8 character: Ã. This looks like an 'x' but is actually different. It is a mathematics characters (10x10 => 10Ã10). You can enter this character by e.g.: <compose key>, <x>, <x> The changelog mailing list has the following header: Content-Type: text/plain; charset="iso-8859-1" This results in the email being rendered incorrectly. Spec files should be utf-8, so the header should contain: Content-Type: text/plain; charset="utf-8"
CC: (none) => mageiaSummary: changelog mails are utf-8 charset, not iso-8859-1 => changelog mails should use utf-8 charset, not iso-8859-1
http://gitweb.mageia.org/software/build-system/mga-youri-submit/tree/lib/Youri/Submit/Action/Mail.pm
URL: (none) => http://gitweb.mageia.org/software/build-system/mga-youri-submit/tree/lib/Youri/Submit/Action/Mail.pm
This also applies to (security) updates notifications as pointed out by Jake from LWN who let us know the following after the "MGASA-2016-0093: Updated openssl packages fix security vulnerabilities" announcement email was sent: FYI, this email does not have a Content-Type header, but has Latin1-encoded data (the ä in Käsper) ... this makes automated ingestion difficult ... our program guesses UTF8 and barfs ... we could, I suppose, try again with Latin1, but it would be best if your system just told us what it was sending ...
CC: (none) => mageiaSummary: changelog mails should use utf-8 charset, not iso-8859-1 => Changelog & updates mails should use utf-8 charset, not iso-8859-1 (and include appropriate header)
This can cause actual mail delivery failures too. Before this fix meant that the mail was malformed and contained no subject and other nice things... http://svnweb.mageia.org/advisories/17737.adv?r1=4327&r2=4330