[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 --- Comment #11 from Laurent Montel --- Git commit 65372b5304a504446259ec1504aa5e2856105e46 by Laurent Montel. Committed on 25/05/2020 at 05:06. Pushed by mlaurent into branch 'release/20.04'. Add autotest for bug 392239 So we extract correctly \r Now we need to know why it doesn't display them A +19 -0autotests/data/mails/bug392239.mbox M +9-0autotests/messagetest.cpp M +1-0autotests/messagetest.h https://invent.kde.org/pim/kmime/commit/65372b5304a504446259ec1504aa5e2856105e46 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 --- Comment #10 from kzi --- Salut Laurent, > But which mailer generates it ? While I think KMail should be capable do deal with any kind of line break, no matter the source, the answer (taken from the header) is: esmtps (Exim 4.92.3) I received the mail from the accounting of a web shop as an invoice carrier (hence the nondisclosure in the first place), so it's likely to originate from some kind of ERP system. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #9 from Laurent Montel --- indeed I confirm it. But which mailer generates it ? It seems that we can't load it from thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 xchain changed: What|Removed |Added Ever confirmed|0 |1 Summary|Messages or parts with |CR linebreaks in message |Content-Transfer-Encoding: |view are not shown |base64 have no line breaks | |displayed | Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #8 from xchain --- Thanks, test cases are always helpful, as they often allow to better pinpoint the core issue. Glad you found the cause! Can confirm that CR linebreaks in base64-encoded messages are not displayed using current git master. In fact, this is not really specific to base64 encoding: Converting any mbox file (e.g. with "Content-Transfer-Encoding: 7Bit") with "unix2mac" to use CR linebreaks yields an empty message view already, and converting only the mail body shows the header at least, but misses linebreaks in the message text. Note that only the message view is affected. When opening the "Message as Plain Text" window through "View Source", the linebreaks are displayed just fine. -- You are receiving this mail because: You are watching all bug changes.
