Version: 1.7.1 (using KDE 3.3.1, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-2) OS: Linux I use two identities to send emails in Kmail (A and B), both of them have their own email direction, and just A has gpg keys. I try to send an encrypted email from B to a contact of my list (I have him public key to encrypt, of course), and Kmail says me that the option "Encrypt always for yourself" is enabled, so I can't continue, because B hasn't keys to encrypt for himself. Ok, I understand, so I go to "Preferences" - "Security" - "Editing" and disable the option, and try again but the same occurs. It seems like Kmail doesn't know that I have disabled the option (now in fact it's disabled but doesn't work). Because I'm Spanish it's possible that the name of the option in English isn't "Encript always for yourself" (in Spanish is written "Cifrar siempre para si mismo"). That's all. Thanks.
I have this too. If you are trying to encrypt an email to someone, It insists on encrypting the copy of that mail kept in sent-mail, even if I disable the "always encrypt to self" option in the settings. If the identity you are sending from does not have a public key on your keyring, then it refuses to encrypt at all, giving the message: You have requested that messages be encrypted to yourself, but the currently selected identity does not define an (OpenPGP or S/MIME) encryption key to use for this. Please select the key(s) to use in the identity configuration.
This bug still occurs in Kmail 1.8.
*** Bug 107787 has been marked as a duplicate of this bug. ***
|| If you restart KMail afterwards, does it work? Not, it doesn't work. The same occurs.
Can someone encrypt mails using an entity without gpg keys? I'd like to know if this bug occurs to all people or just to some of them.
This bug still occurs in Kmail 1.8.2, can someone encrypt mails using an entity without gpg keys?
I can confirm this bug in many computers with the last version of Debian Sid.
I can confirm the bug and I already know why it happens. I'll see whether I can easily fix it.
Then Kmail will be nearly perfect! Thanks a lot, really.
Kmail 1.9.6 in Kubuntu with KDe 3.5.6. The bug still exists. Kmail says me that the option "Encrypt always for yourself" is enabled, but in kmailrc there is: crypto-encrypt-to-self=false
I also confirm this. It seems the "Undefined Encryption Key" popup (when clicking on "Encrypt Message") does not check the setting "crypto-encrypt-to-self" correctly (the checkbox in "Configure KMail / Security / Composing" seems to get toggled/displayed correctly).
SVN commit 705215 by bvirlet: Always encrypt to self function was always on. BUG: 93436 M +3 -1 kmcomposewin.cpp --- branches/KDE/3.5/kdepim/kmail/kmcomposewin.cpp #705214:705215 @@ -2245,7 +2245,9 @@ } bool KMComposeWin::encryptToSelf() const { - return !Kpgp::Module::getKpgp() || Kpgp::Module::getKpgp()->encryptToSelf(); +// return !Kpgp::Module::getKpgp() || Kpgp::Module::getKpgp()->encryptToSelf(); + KConfigGroup group( KMKernel::config(), "Composer" ); + return group.readBoolEntry( "crypto-encrypt-to-self", true ); } bool KMComposeWin::queryExit ()
SVN commit 705217 by bvirlet: Port r705205 to enterprise branch. CCBUG: 93436 M +3 -1 kmcomposewin.cpp --- branches/kdepim/enterprise/kdepim/kmail/kmcomposewin.cpp #705216:705217 @@ -2260,7 +2260,9 @@ } bool KMComposeWin::encryptToSelf() const { - return !Kpgp::Module::getKpgp() || Kpgp::Module::getKpgp()->encryptToSelf(); +// return !Kpgp::Module::getKpgp() || Kpgp::Module::getKpgp()->encryptToSelf(); + KConfigGroup group( KMKernel::config(), "Composer" ); + return group.readEntry( "crypto-encrypt-to-self", true ); } bool KMComposeWin::queryExit ()
> What |Removed |Added > --------------------------------------------------------------------------- >- Status|NEW |RESOLVED > Resolution| |FIXED Great ;) Thanks a lot.