Hi, I installed new opensuse Leap 42.3 and unfortunately, I can't configure kmail to automatically crypt the message when I reply to someone that has crypted his message. And of course, I often forget to check before sending, so my message is sent uncrypted and even the quote message is uncrypted... It would be great if kmail could consider that if the incoming mail is crypted, the response should also be crypted to keep the whole discussion secured. I'm almost sure that on my old opensuse 13.2, kmail had this behavior by default and I could not find any check button in the config panel. The only options available are (translated from my french install) : - "always send crypted if possible" (in the identity config), but as it is not possible to decrypt on a smartphone via gmail, I rather send uncrypted unless content is sensitive ; - "ask when trying to send uncrypted message" (in the security panel), but that mean that I always have to click all day long on that window for all common uncrypted messages. Thanks for any advice if I could not find the right config, otherwise, I put that option on the wishlist ! Thanks for developing such a nice tool ! Marc
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!