[Evolution-users] Encryption problem - need help

[Matthias Kuntze]

On Wed, 2025-10-01 at 08:52 -0400, janos wrote:
> As far as I understand SMIME is another privacy method, using
> certificates from community trusted organizations. When I sent the
> encrypted message I did not check any of the SMIME check boxes. This
> is
> why I do not understand the SMIME errors - apart from how come I
> could
> not read my own encrypted email in the Sent folder.
> 
> Janos
> 
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.

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.

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.

Please check the PGP data (e.g. fingerprint / OpenPGP Key ID) at both
sites with "evolution" and "seahorse" for correct configuration.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5910 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/evolution-users/attachments/20251001/d88abc01/attachment.p7s>