Bug 306005

Summary:	Violation of rfc822: kmail2 end of line handling, CR (0x0D) is dropped from messages and not inserted when sending messages
Product:	[Applications] kmail2	Reporter:	Thomas Arend <thomas>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	dilfridge, thomas
Priority:	NOR
Version:	4.9.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thomas Arend 2012-08-29 18:22:51 UTC

Kmail2 handles the end of line (EOL) not in compliance the RfC 822. All CR (0x0D) are dropped. 

Although in 7Bit plain/text attachments the CR is dropped. This can cause a signature to to fail.


Reproducible: Always

Steps to Reproduce:
1. Create a message in the composer
2. Send message
3. Save outgoing message in mbox format
or receive message with kmail2 or another mail client.
4. view source code with hex editor / hexdump

Actual Results:  
Other mail clients have difficulties to interpret the message - especially signed multi part messages.
Attachments are corrupted by kmail2.

Verification of signatures may fail.



Expected Results:  
Instead of a LF the EOL should be signaled by the CR LF sequence ( 0x0D, 0x0A )

kmail2 should comply to RfC 822.

Attachments should not be altered by mail clients.

Comment 1 Thomas Arend 2012-12-09 16:25:42 UTC

Error is also in 4.9.4

Comment 2 Andreas K. Huettel 2012-12-09 16:48:48 UTC

Someone with appropriate permissions- please change the summary, this bug DOES invalidate signatures made with GPG, rendering the signing support partly useless.

Comment 3 Denis Kurz 2016-09-24 18:11:34 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 4 Denis Kurz 2017-01-07 22:03:28 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.