Ask Your Question

AKoine's profile - activity

2017-11-01 09:30:00 -0600 received badge  Editor (source)
2017-11-01 09:28:54 -0600 answered a question [Solved]Fail to send encrypted emails using evolution

Solution found thanks to villykruse : Just tick the box "Always trust keys in my keyring when encrypting" in the security panel of your email account. To do so, from the Evolution Main Menu, select Edit -> Preferences. In the left pane, select Mail Accounts. In the right pane, select the email account you use for Fedora Project correspondence. Then select the Edit button. The Account Editor dialog appears. Select the Security tab. This this guide for a screenshot.

Hope this will help somebody else.

2017-11-01 09:26:02 -0600 commented answer [Solved]Fail to send encrypted emails using evolution

Thanks for the reply, ticking the box "Always trust keys in my keyring when encrypting" did the trick for me !

2017-10-30 17:23:42 -0600 commented answer [Solved]Fail to send encrypted emails using evolution

No, I did not mark the gpg key as trusted. How do I do that ? In seahorse, when I try to sign the key (as I guess that would be what you're suggesting), I get a "failed to sign the key. General error" window poping up.

How can I know in which gpg a key has been imported ?

2017-10-22 11:00:25 -0600 answered a question [Solved]Fail to send encrypted emails using evolution

Hi,

Thanks for the reply.

When I tick those boxes, and I try to send an encrypted message to myself, I got the following error : "Il se peut que vous ayez besoin de choisir d'autres options de messagerie. Détails de l'erreur : Échec de chiffrement : destinataire 0 XXXXXXXX non valide. Une raison fréquente est que gpg2 n'a pas importé de clé publique pour ce destinataire." Which I roughly translate as follows :

You may need to select different mail options. Error details : encryption failed : recipient 0 XXXXXXXX is not valid. A common issue is that gpg2 has not imported the public key for this recipient.

Maybe the problem comes from the way I selected my GPG key you mentioned in step 1 : I typed the last 8 digits returned by the command "gpg --fingerprint". Should I have been able to select it from a drop-down list or use a different command to determine it ?

Thanks again for your help,

2017-10-20 08:45:10 -0600 received badge  Nice Question (source)
2017-10-20 03:32:36 -0600 received badge  Student (source)
2017-10-20 03:05:29 -0600 asked a question [Solved]Fail to send encrypted emails using evolution

Hi there,

I can't send encrypted emails using evolution. I managed to import my private pgp key, as well as the public key of my intended recipient, using command line. These keys are visible in seahorse. In my email account properties -> security tab, field "ID of the OpenPGP key" I typed the 8 last digits of my private key (found using the command "gpg --fingerprint"). (sorry if the translation of the tabs and error messages are not perfect, I run a french localised fedora) Good news is I can decrypt emails sent to me by the recipient mentioned above.

However, when I want to reply, I get the following error message (XXing the keys ID):

Il se peut que vous ayez besoin de choisir d'autres options de messagerie.
Détails de l'erreur : Échec de chiffrement : destinataire 0 XXXXXXXX non valide. Une raison fréquente est que gpg2 n'a pas importé de clé publique pour ce destinataire.

approximate translation :

You may need to select different mail options. Error details : encryption failed : recipient 0 XXXXXXXX is not valid. A common issue is that gpg2 has not imported the public key for this recipient.

From there :

  1. If I tick the box "Always encrypt for myself when sending encrypted emails" in the security tab of my email account properties, the XXXXXXXXX of the previous error message are replaced by my pgp key ID (see above)
  2. If I do not tick the box "Always encrypt for myself when sending encrypted emails" in the security tab of my email account properties, the XXXXXXXXX are replaced by my recipient email address (for which the public key seems correctly imported since visible in seahorse, see above)

Does any of this sounds familiar to anyone out there ?

Merci beaucoup !!