Bug#754265: kmail: uses wrong charset/encoding indicator for Inline PGP messages
Package: kmail
Version: 4:4.12.4-1
Severity: normal
Hi *,
if sending an Inline PGP message from an MUA which sets the header
charset to ASCII (see #754262 for an example), Kontact/KMail wrongly
uses the MIME header as charset/encoding indicator for the PGP body.
This is wrong: with Inline PGP, the RFC822 and MIME handling is only
used to decode the message prior to PGP operation. Following this is
dearmouring, PGP decoding, and then display according to the charset
denoted for the PGP message, which is independent of the MIME charset
denoted for the message “RFC822 transport container”.
The absence of a “Charset:” PGP pseudo-header should mean UTF-8 is
to be used.
In general, UTF-8 is a sane fallback for messages declared as ASCII
with bit7-set bytes in them, in this time and day; use cp1252 only
as last-resort fallback (if UTF-8 decoding fails). But independently
of this, using the MIME charset for the after-PGP body is wrong (e.g.
I could have the MIME charset say KOI8-R with a latin1 PGP body, which
probably¹ leads to mojibake).
① didn’t test that… but I could, if needed. ($dayjob calls.)
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Versions of packages kmail depends on:
ii kde-runtime 4:4.13.1-1
ii kdepim-runtime 4:4.12.4-2
ii kdepimlibs-kio-plugins 4:4.12.4-1
ii libakonadi-calendar4 4:4.12.4-1
ii libakonadi-contact4 4:4.12.4-1
ii libakonadi-kde4 4:4.12.4-1
ii libakonadi-kmime4 4:4.12.4-1
ii libakonadiprotocolinternals1 1.12.1-1+b1
ii libc6 2.19-5
ii libcalendarsupport4 4:4.12.4-1
ii libfolderarchive4 4:4.12.4-1
ii libgcc1 1:4.9.0-10
ii libgpgme++2 4:4.12.4-1
ii libgrantlee-core0 0.3.0-5
ii libincidenceeditorsng4 4:4.12.4-1
ii libkabc4 4:4.12.4-1
ii libkalarmcal2 4:4.12.4-1
ii libkcalcore4 4:4.12.4-1
ii libkcalutils4 4:4.12.4-1
ii libkcmutils4 4:4.13.1-1
ii libkdecore5 4:4.13.1-1
ii libkdepim4 4:4.12.4-1
ii libkdeui5 4:4.13.1-1
ii libkio5 4:4.13.1-1
ii libkleo4 4:4.12.4-1
ii libkmime4 4:4.12.4-1
ii libknewstuff3-4 4:4.13.1-1
ii libknotifyconfig4 4:4.13.1-1
ii libkontactinterface4 4:4.12.4-1
ii libkparts4 4:4.13.1-1
ii libkpgp4 4:4.12.4-1
ii libkpimidentities4 4:4.12.4-1
ii libkpimtextedit4 4:4.12.4-1
ii libkpimutils4 4:4.12.4-1
ii libkprintutils4 4:4.13.1-1
ii libksieveui4 4:4.12.4-1
ii libktnef4 4:4.12.4-1
ii libmailcommon4 4:4.12.4-1
ii libmailimporter4 4:4.12.4-1
ii libmailtransport4 4:4.12.4-1
ii libmessagecomposer4 4:4.12.4-1
ii libmessagecore4 4:4.12.4-1
ii libmessagelist4 4:4.12.4-1
ii libmessageviewer4 4:4.12.4-1
ii libnepomukcore4 4:4.12.4-1+b1
ii libpimcommon4 4:4.12.4-1
ii libqt4-dbus 4:4.8.6+dfsg-2
ii libqt4-network 4:4.8.6+dfsg-2
ii libqt4-xml 4:4.8.6+dfsg-2
ii libqtcore4 4:4.8.6+dfsg-2
ii libqtgui4 4:4.8.6+dfsg-2
ii libqtwebkit4 2.2.1-7
ii libsendlater4 4:4.12.4-1
ii libsolid4 4:4.13.1-1
ii libsoprano4 2.9.4+dfsg-1.1
ii libstdc++6 4.9.0-10
ii libtemplateparser4 4:4.12.4-1
ii perl 5.18.2-5
Versions of packages kmail recommends:
ii gnupg-agent 2.0.25-1
ii gnupg2 2.0.25-1
ii pinentry-qt4 [pinentry-x11] 0.8.3-2
Versions of packages kmail suggests:
pn clamav | f-prot-installer <none>
ii kaddressbook 4:4.12.4-1
ii kleopatra 4:4.12.4-1
pn procmail <none>
pn spamassassin | bogofilter | annoyance-filter | spambayes | bsfi <none>
-- no debconf information
Reply to: