GNOME Bugzilla – Bug 545851
Signed mails with S/MIME are marked PGP+S/MIME on post-sending edition
Last modified: 2009-10-16 08:42:51 UTC
Please describe the problem: After sending an e-mail with S/MIME signature, trying to edit this e-mail forces the "Sign with PGP" line to be checked in "Security" menu. This is an upstream from bug #115039 in Ubuntu. See https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/115039 for more. Steps to reproduce: 1. Send a e-mail with an S/MIME signature but without any PGP signature. 2. Open this e-mail from Sent folder with "Edit as a new mail" 3. Open the Security menu and see: "Sign with PGP" is now checked, but shouldn't. Actual results: After editing such an e-mail, one should uncheck the "Sign with PGP" line in Security menu, or re-sending the e-mail will fail (unless you actually have a pgp cert) with: Impossible to create the message Because "gpg: « xxx.yyyyy@zzz.com» has been ignored: private key is not avaliable gpg: signing failed: private key is not avaliable. ", you may need to select different mail options. Expected results: The "Sign with PGP" line in Security menu shouldn't be checked. Does this happen every time? Happens every time. Other information:
As said, there actually is an easy workaround, which must be applied for every mail: open the Security menu and uncheck "Sign with PGP", but it's pretty unconvenient.
I'm getting this bug to. +1 on the inconvenience.
Ditto. Very annoying when trying to diagnose email problems. +1
I have this too on Evolution 2.24.3 on Ubuntu Intrepid 8.10 (and every earlier version). Note that this also happens when there is an error in the mail address and the mail gets stuck in the Outbox. If you edit the mail to correct the faulty address and then hit send this message appears.
Bug still present on Ubuntu Jaunty with Evolution 2.26.1
Ditto. Just verified. This needs to be changed to CONFIRMED.
Created attachment 138185 [details] [review] proposed evo patch for evolution; The only thing I'm not able to get is whether the message was encrypted and signed, as the signing part is inside the encrypted, which is not accessible within composer.
Created commit 527e9e4 in evo master (2.29.1+)