I received an HTML email: http://lists.kde.org/?l=kde-edu&m=140827246021112&w=2 I replied to this email (and it was as HTML mail): http://lists.kde.org/?l=kde-edu&m=140830959601155&w=2 But my settings have at Composer -> General the option "Reply or forward using HTML if present" unchecked as unmarked. So I expect the mail to be plain text only. The odd thing, the composer actually should a plain-text only mail. Reproducible: Always Steps to Reproduce: see above Actual Results: ah HTML email Expected Results: a plain text email Maybe for clarification it might be good to an option to the composer saying something "Enable HTML for composing mails" and reorder the other options accordingly.
(In reply to Andreas Cord-Landwehr from comment #0) > I received an HTML email: > http://lists.kde.org/?l=kde-edu&m=140827246021112&w=2 > > I replied to this email (and it was as HTML mail): > http://lists.kde.org/?l=kde-edu&m=140830959601155&w=2 > > But my settings have at Composer -> General the option "Reply or forward > using HTML if present" unchecked as unmarked. So I expect the mail to be > plain text only. > The odd thing, the composer actually should a plain-text only mail. no :) We are able to write in html too. > Maybe for clarification it might be good to an option to the composer saying > something "Enable HTML for composing mails" and reorder the other options > accordingly.
Oh, just noticed a really bad typo on my side :) Instead of writing "The odd thing, the composer actually should a plain-text only mail." I wanted to write: "The odd thing, the composer actually showed a plain-text only mail".
I can confirm the behaviour with KMail 4.13.3 and to be honest I am a little bit concerned about it: Disabling html rendering/interpretation is suggested for security reasons - which I support. But at some point the html seems to be interpreted so that it can be displayed as plain text as the reporter writes.
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.
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.