Version: unknown (using KDE 3.2 BRANCH >= 20040204, compiled sources) Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB Using only Aegypten1 stuff. Crypto format is "Any", signing and encryption is enabled. If I send the message KMail tells me "Valid trusted encryption keys were found for all recipients. Encrypt this message?" Doh! Why do you think I have enabled encryption? This pointless question should be suppressed.
On Sunday 11 July 2004 16:28, Ingo Klöcker wrote: > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > http://bugs.kde.org/show_bug.cgi?id=84927 > Summary: KMail asks whether the message should be encrypted even > if encryption is enabled explicitely > Product: kmail > Version: unspecified > Platform: unspecified > OS/Version: Linux > Status: NEW > Severity: normal > Priority: NOR > Component: encryption > AssignedTo: kmail-devel kde org > ReportedBy: kloecker kde org > > > Version: unknown (using KDE 3.2 BRANCH >= 20040204, compiled sources) > Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) > OS: Linux (i686) release 2.4.20-4GB > > Using only Aegypten1 stuff. > > Crypto format is "Any", signing and encryption is enabled. If I send the message KMail tells me > > "Valid trusted encryption keys were found for all recipients. > Encrypt this message?" I see the code for this in MessageComposer::determineWhetherToEncrypt() It happens when the encryption preferences are: case Kleo::AskOpportunistic: case Kleo::Ask: Could the problem be that somehow the default is one of those? > Doh! Why do you think I have enabled encryption? > > This pointless question should be suppressed. Well if the user wants to be asked........ But in general there's indeed a bit of a conflict between the toolbar buttons and the more pre-recipient settings; not an easy problem to solve.
Hi, just noting that this is still a problem in 4.1.0, and makes using the crypto functions of KMail really confusing.
Could someone please add some instructions on how to reproduce this bug? Thanks.
As the original reports text is no longer in the 4.3 RC3 source and there was no reply to comment #3, I'll close this bug.