After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 415646 - Can't read signed + encrypted mail when sig-key not available
Can't read signed + encrypted mail when sig-key not available
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-07 10:04 UTC by Sebastian Breier
Modified: 2010-12-12 14:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sebastian Breier 2007-03-07 10:04:13 UTC
Please describe the problem:
I just got a mail that was encrypted (for me) and signed (from the other person). Because I did not yet have his key, Evolution showed a red error message about not being able to find the public key, together with the encrypted mail.

Saving the mail and decrypting on the command line ("gpg -d mail") was possible, though GPG also complained about not being able to verify the signature.

Evolution should at least decrypt the message, showing only errors about the signature verification.

Steps to reproduce:
1. Open Evolution
2. Receive GPG-encrypted & -signed mail
3. Open the mail
4. Enter GPG password


Actual results:
I see a red error message about the public key for the signature not being found + the encrypted mail text.

Expected results:
I'd like to see the decrypted mail text + a signature verification warning.

Does this happen every time?
Yes.

Other information:
Comment 1 Sebastian Breier 2007-03-07 10:09:07 UTC
In Ubuntu: https://bugs.launchpad.net/evolution/+bug/90339
Comment 2 Sebastian Breier 2009-03-30 14:41:33 UTC
Fixed since evolution 2.24.3-0ubuntu1 or earlier.
Comment 3 Pauli Virtanen 2010-12-12 14:28:00 UTC
I'm still seeing this bug on evolution 2.30.3-1ubuntu7.1. Was it really fixed?