[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1

https://bugs.kde.org/show_bug.cgi?id=387926 kzi changed: What|Removed |Added CC||k...@snafu.de --- Comment #28 from kzi --- I can

[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1

https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #31 from kzi --- (In reply to Fabian Vogt from comment #30) > ksmtp sends the server's hostname instead of the local hostname by accident > with the "EHLO" command. The mail.snafu.de server rejects that immediately, &g

[kmailtransport] [Bug 388160] New: ksmtp EHLO sends server hostname as domain parameter by default

https://bugs.kde.org/show_bug.cgi?id=388160 Bug ID: 388160 Summary: ksmtp EHLO sends server hostname as domain parameter by default Product: kmailtransport Version: unspecified Platform: openSUSE RPMs OS: Li

[kmailtransport] [Bug 388160] ksmtp EHLO sends server hostname as domain parameter by default

https://bugs.kde.org/show_bug.cgi?id=388160 --- Comment #1 from kzi --- My system is openSUSE Tumbleweed. kmailtransport 17.12.0-1.1-x86_64 ksmtp 17.12.0-3.1-x86_64 (How does that relate to the 'Version' dropdown above?) -- You are receiving this mail because: Y

[kmailtransport] [Bug 388160] ksmtp EHLO sends server hostname as domain parameter by default

https://bugs.kde.org/show_bug.cgi?id=388160 --- Comment #3 from kzi --- Thank you, Fabian! localhost.invalid and foo.localnet make up nice domain names, too. :) -- You are receiving this mail because: You are the assignee for the bug.

[kmail2] [Bug 447297] New: UTF-8 characters decoded incorrectly on reply

https://bugs.kde.org/show_bug.cgi?id=447297 Bug ID: 447297 Summary: UTF-8 characters decoded incorrectly on reply Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Sev

[kmail2] [Bug 392239] Messages or parts with Content-Transfer-Encoding: base64 have no line breaks displayed

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.

[kmail2] [Bug 392239] Messages or parts with Content-Transfer-Encoding: base64 have no line breaks displayed

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.

[kmail2] [Bug 392239] Messages or parts with Content-Transfer-Encoding: base64 have no line breaks displayed

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.

[kmail2] [Bug 392239] Messages or parts with Content-Transfer-Encoding: base64 have no line breaks displayed

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

[kmail2] [Bug 392239] Messages or parts with Content-Transfer-Encoding: base64 have no line breaks displayed

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.

[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

[kmail2] [Bug 392239] New: Messages or parts have no line breaks displayed

https://bugs.kde.org/show_bug.cgi?id=392239 Bug ID: 392239 Summary: Messages or parts have no line breaks displayed Product: kmail2 Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: no

[kmail2] [Bug 392239] Messages or parts with Content-Transfer-Encoding: base64 have no line breaks displayed

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