Bug 321163

Summary: Composed text/plain contains NULL bytes under certain circumstances
Product: [Applications] kmail2 Reporter: Jan Kundrát <jkt>
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: sgmoore
Priority: NOR    
Version: 4.10.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jan Kundrát 2013-06-14 22:45:52 UTC 
One message on the kde-pim mailing list [1] contains properly encoded NULL bytes within a text/plain body part in ISO-8859-1 charset. I suspect that this is not expected to happen, so I'm filing this bug (it happened to trigger a bug in Trojita where such mail was invisible because WebKit chose to display blank page when fed such data, even though the null byte was only in the middle of the text -- BUG #321160, RR 111030).

Relevant headers of that mail:

From: Scarlett Clark <scarlett@scarlettgatelyclark.com>
To: Burkhard =?ISO-8859-1?Q?L=FCck?= <lueck@hube-lueck.de>
Date: Fri, 14 Jun 2013 12:16:31 -0600
Message-ID: <3186578.nRav8CEG4t@neptune>
User-Agent: KMail/4.10.3 (Linux/3.8.13-gentoo; KDE/4.10.3; x86_64; ; )
Subject: Re: [Kde-pim] [kdepim] doc/kmail: use correct names for gui
	elements, ebn check fixes, use <quote> to ease translators work
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

[1] http://lists.kde.org/?l=kde-pim&m=137123381704459&w=2

Reproducible: Always
Comment 1 Scarlett Moore 2013-06-14 22:56:54 UTC 
Is this something on my end?
Comment 2 Denis Kurz 2016-09-24 17:54:11 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:16:26 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.