Bug 93436 - Option "Encrypt always for yourself" is always enabled
Summary: Option "Encrypt always for yourself" is always enabled
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: 1.7.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 107787 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-11-17 11:43 UTC by ibc
Modified: 2007-09-14 12:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ibc 2004-11-17 11:43:54 UTC
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.
Comment 1 Martin Traverse 2005-01-21 04:22:47 UTC
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.
Comment 2 Iñaki Baz Castillo 2005-04-12 00:59:55 UTC
This bug still occurs in Kmail 1.8.
Comment 3 Thiago Macieira 2005-06-25 03:29:01 UTC
*** Bug 107787 has been marked as a duplicate of this bug. ***
Comment 4 Iñaki Baz Castillo 2005-06-25 09:17:59 UTC
|| If you restart KMail afterwards, does it work?

Not, it doesn't work. The same occurs.
Comment 5 Iñaki Baz Castillo 2005-08-26 17:20:34 UTC
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.
Comment 6 Iñaki Baz Castillo 2005-11-05 20:43:30 UTC
This bug still occurs in Kmail 1.8.2, can someone encrypt mails using an entity without gpg keys? 
Comment 7 Iñaki Baz Castillo 2005-11-10 22:42:39 UTC
I can confirm this bug in many computers with the last version of Debian Sid.
Comment 8 Ingo Klöcker 2005-12-15 23:58:18 UTC
I can confirm the bug and I already know why it happens. I'll see whether I can easily fix it.
Comment 9 Iñaki Baz Castillo 2005-12-16 00:07:19 UTC
Then Kmail will be nearly perfect!
Thanks a lot, really.
Comment 10 Iñaki Baz Castillo 2007-01-26 22:04:36 UTC
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
Comment 11 Daniel Hahler 2007-04-16 22:49:27 UTC
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).
Comment 12 Bruno Virlet 2007-08-27 15:25:29 UTC
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 ()
Comment 13 Bruno Virlet 2007-08-27 15:31:45 UTC
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 ()
Comment 14 Iñaki Baz Castillo 2007-08-27 15:48:45 UTC
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
>- Status|NEW                         |RESOLVED
>          Resolution|                            |FIXED


Great ;)

Thanks a lot.