in settings -> configure kmail -> security -> composing you can check or uncheck "store sent mails encrypted". this checkbox doesn't seem to have any effect. Reproducible: Always Steps to Reproduce: 1. check "store sent mails encrypted" and send an encrypted mail and an unencrypted mail 2. unceck "store sent mails encrypted" and send an encrypted mail and an unencrypted mail Actual Results: encrypted mails are stored encrypted, unencrypted mails are stored unencrypted, regardless of the checkbox state. Expected Results: at the very least, any effect at all would be nice. even better, if the option is set, all mails should be stored encrypted (at least the ones also sent encrypted), and if it isn't, all mails should be stored unencrypted (even if they were sent encrypted). while at it, this should better be a dropdown menu or radio button with three options: - always store encrypted - always store unencrypted - always store as sent
You're right this option is not implemented.... I didn't know. I will look at it. thanks for reporting it.
in kmail akonadi it's not possible in state. I will disable for the moment to avoid that user doesn't understand why it doesn't work. I keep open this bug report perhaps in future I will find a method to do it.
Git commit bb07f3265b6dab7cae7b175fd11e49a1792354f0 by Montel Laurent. Committed on 16/12/2014 at 07:22. Pushed by mlaurent into branch 'KDE/4.14'. Disable this action which was not implemented in kmail akonadi M +1 -0 kmail/configuredialog/configuresecuritypage.cpp http://commits.kde.org/kdepim/bb07f3265b6dab7cae7b175fd11e49a1792354f0
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.