GNOME Bugzilla – Bug 329342
wrong mail address with gpg keys containing multiple IDs
Last modified: 2018-06-27 10:31:31 UTC
Please describe the problem: I have multiple IDs on my GPG key (zali@movial.fi and zeenix@gstreamer.net are the two i'll mention here). I use evolution only for the office email (zali@movial.fi). When someone sends me an encrypted email, evolution doesn't decrypt the message for me. Moreover, it reports that the message was encrypted for my zeenix@gstreamer.net. mutt on the other hand doesn't have any problems. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
well, i also use a key with multiple mail addresses, and (at least when having sent the mail from evolution) i get the wrong email adress information. but i would rather say that it does not matter, because the password is the same. hmm. moving to mailer.
Bumping version to a stable release.
First of all, gpg encrypts the message with some key, not with an email address. The gpg binary finds the key and reports the address as set in the key as the primary address. It cannot determine whether the sender used the first or the last email address in the list of addresses. Evolution can do it (with the From/Sender header), but Evolution rather depends on the values reported by gpg, which are more accurate. And the address reporting is fir signatures, rather than for encryption. That the decryption failed is odd. It should not have anything to do with a different From/Sender address, it's still only about the used key, which either is or is not in the local gpg key store. The trust level may play its role there as well. I tried to reproduce it here, with a key which had three different user identities. I sent a signed & encrypted message from another machine to each of those addresses individually and evolution was able to decrypt all these three messages on the machine where I had also the private key with no problem. That's with the development version 3.29.3 of evolution (which should not matter that much) and gnupg2-2.2.6-1.fc28.x86_64 (this can matter more). I'm closing this bug report as obsolete.
Wow, I don't have any memory of filing this bug. Maybe my (12 years) younger self did something wrong. :) Thanks for trying to reproduce though. I'm back to using evolution.
You are welcome. Feel free to update the ticket in case you face the issue with more recent versions (the fix could land anywhere, from evolution/-data-server to gpg itself). There's always a chance I did something wrong and/or differently, which made it work for me, but would still fail for you.