GNOME Bugzilla – Bug 335984
unhelpful error message on failure to decode s/mime encrypted message
Last modified: 2009-02-24 18:25:54 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/evolution/+bug/33990 "I got an s/mime encrypted message the other day and got the message Decoder failed, error -8147 Took me some time before I realized that the problem was that I hadn't imported my certificate. I even installed Thunderbird in hopes that this "decoder failure" might be a evolution-only problem. The message should say something about what is actually wrong. http://librarian.launchpad.net/1660365/error-8147.png Screenshot of the error message. ... > Thanks for your bug. What version of Ubuntu do you use? Do you have an example of such mail? ... The bug exists on Dapper and Breezy. It's very likely an upstream bug. Any s/mime encrypted email to which you don't have the key should produce the bug. I will try to attach an example that is encrypted to myself. http://librarian.launchpad.net/1834239/example.eml This email is encrypted to myself. If you can find a way to import it into evolution you should see the same bug."
I experience the same problem and saw the same message appearing. I am using: - Ubuntu 6.10 - Kernel 2.6.17-10-generic - KDE 3.5.6 - Evolution 2.8.1 I hope there's a workaround. Thanks for keeping me posted. ML
Well. I don't think there is a "workaround". Maybe the error message is unhelpful but it is normal that you can't decrypt a message that you sent to someone else because you don't have his/her private key...
There is a 'workaround' for the non-problem. Comment #2 is correct. A message encrypted with the receiver's public key should be unreadable by any other person, including the sender (I get Decoder failed, error -8147). Exactly as it should be! But, yes, the error message could be clearer. Something like "Decryption key for foo@bar.com not found" could avoid spurious tickets? There is a 'workaround' however. In the preferences window select the 'Mail Accounts' icon, select your default account (or each of them in turn), click on 'Edit', go to the 'Security' tab, and check the box next to 'Also encrypt to self when sending encrypted email'. And voila! your problem is gone.
I should added that this will not make previous encrypted emails legible.
I'll merge this with the other bug, as it is almost the same. *** This bug has been marked as a duplicate of 273233 ***