[Evolution-users] Encryption problem - need help

Cyril Soler cyril.soler at inria.fr
Wed Oct 1 16:09:48 UTC 2025


Well, normally (and according to RFC4880) it should be possible to
encrypt for both the recipient and yourself, so that you can read the
mail that you sent using your own key. Thunderbird+enigmail does this
for instance. 

I suppose that feature is simply not implemented.

 
On Wed, 2025-10-01 at 11:59 -0400, janos via evolution-users wrote:
> On Wed, 2025-10-01 at 15:47 +0200, Matthias Kuntze wrote:
> > Oh, you are using PGP (or GPG) not S/MIME. Then its a little bit
> > different. But your suggestion in the previous post (point 2) is
> > not
> > totally right.
> > 
> point 2: "Sender encrypts the message with its own private (i.e.
> sender's private key) key and the Recipient's public key" - is this
> not
> totally right?
> > If you wish to sign a message for sending, the checksum of the
> > message
> > is encrypted by your private key. The receiver can decrypt this
> > information with your public key (point 3 of previous post),
> > calculate
> > the checksum and compare the results to test the mail integrity.
> > 
> > If you wish to encrypt a message for sending, the message is
> > encrypted
> > with the public key of the recipient (see prev post point 3). The
> > receiver must have and use the corresponding private key to decrypt
> > the
> > message.
> > 
> Yes, and the receiver could in fact decrypt
> 
> > The fingerprint of the PGP/GPG key to use by an mail-account is
> > defined
> > in the "Edit" -> "Preferences" -> "Mail Preferences" -> your-
> > account
> > ->
> > "Edit" -> "Security" section. You can view your PGP key with the
> > "seahorse" GUI. The recipient should see his PGP key with
> > "seahorse"
> > at
> > his installation too. 
> > The public PGP key of the recipient must be useable at your sender
> > site. You might use the "Certificates" tab in your "Contact Editor"
> > for
> > that task.
> > 
> This may be the SOLUTION - there is nothing in the Sender Evolution
> Contact for Recipient "Certificates" tab. I'll have to figure out why
> it is not finding the public key of the Recipient in ~/.gnupg/public-
> keys.d/ while Seahorse does show it.
> 
> My sender machine is Gentoo linux.
> 
> > Please check the PGP data (e.g. fingerprint / OpenPGP Key ID) at
> > both
> > sites with "evolution" and "seahorse" for correct configuration.
> I checked Seahorse on both machines and they are mutually correct:
> (S) Sender machine has public key ID of the receiver
> (R) Receiver machine has public key ID of sender
> 
> B.t.w. thank you all for your comments and interest in this sybject
> 
> Janos
> -- 
> sent from andraslinux machine
> https://jgklinux.jangkom.com/
> 
> 



More information about the evolution-users mailing list