I run with Kmail composer HTML settings Disabled, but on several occasions - after changing e.g. spell- checking settings change, or a system software update - the HTML settings have been found to have been re-enabled, causing quite a nuisance until the settings are restored. The last occasion was when I used System Settings/Locale/Spellchecking to enable spell checking, after which I realised that the KMail HTML settings had been re-enabled. So somewhere within KDE is some code that is mandating HTML enabled.... Reproducible: Sometimes Steps to Reproduce: 1. Work with HTML options disabled in KMail (4.10.2) Composer 2. Make some change, e.g. set spellchecking on/off via System Settings/Locale, or do some system software update changing KDE components. 3. (I now make a weekly check for the HTML settings, and several times each month find they have been re-enabled.) Actual Results: HTML settings have been fortuitously re-enabled. Expected Results: HTML settings sacrosanct; only the user (or root?) can change them. # rpm -qif /bin/kmail Name : kmail Epoch : 2 Version : 4.10.2 Release : 3.mga3 Architecture: i586 Install Date: Tue 28 May 2013 18:25:36 BST Group : Networking/Mail Size : 1480564 License : GPLv2 and LGPLv2 and GFDL Signature : RSA/SHA1, Sat 13 Apr 2013 18:47:54 BST, Key ID b742fa8b80420f66 Source RPM : kdepim4-4.10.2-3.mga3.src.rpm Build Date : Sat 13 Apr 2013 18:42:24 BST Build Host : jonund.mageia.org Relocations : (not relocatable) Packager : tmb <tmb> Vendor : Mageia.Org URL : http://www.kde.org/applications/internet/kmail Summary : KDE Email Client Description : KMail is the email component of Kontact (the integrated personal information manager of KDE).
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.