https://bugs.kde.org/show_bug.cgi?id=392239
--- Comment #7 from kzi ---
(In reply to kzi from comment #6)
> Apparently 0D (CR) characters are stripped from the resulting message.
...or just not rendered as line break.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=392239
--- Comment #6 from kzi ---
Thx for hinting mbox redaction.
While trying to come up with a disclosable example I found the cause is the
line break character used in the base64-decoded plain text message: Apparently
0D (CR) characters are stripped from
https://bugs.kde.org/show_bug.cgi?id=392239
--- Comment #4 from kzi ---
Created attachment 128668
--> https://bugs.kde.org/attachment.cgi?id=128668&action=edit
mbox where plain text has 0D (CR) line breaks
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=392239
--- Comment #5 from kzi ---
Created attachment 128669
--> https://bugs.kde.org/attachment.cgi?id=128669&action=edit
mbox where plain text has 0D0A (CRLF) line breaks
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=392239
--- Comment #3 from kzi ---
Created attachment 128667
--> https://bugs.kde.org/attachment.cgi?id=128667&action=edit
mbox where plain text has 0A (LF) line breaks
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=392239
--- Comment #2 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=392239
xchain changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=392239
kzi changed:
What|Removed |Added
Summary|Messages or parts have no |Messages or parts with
|line breaks dis
