it's not possibile to create a message with pgp encryption

[marco.pallotta]

I have a public key imported and signed correctly with seahorse but when I want to create a message with the content encrypted with the public key just imported evolution replies that is not possible to create the message because "there is no assurance this key belongs to the named user".

I use Evolution 2.22.3.1 in Hardy Heron x86_64.

[marco.pallotta (marco-pallotta)]

I think I have found the origin of the issue and this is not related to evolution but I think is related to seahorse. In fact if I import the public key and I assign to it a trust value via cli using the tool gpg all runs ok. Moreover it also solves other evolution bugs (#304539).
After trusting and signing the key via gpg if you launch seahorse you can see that no trust is showed in the detail tab of the key properties (but if you test this via gpg you see that trust is assigned correctly and in fact evolution runs ok). So I think seahorse is the problem (I have realized that seahorse is the buggest software I have ever used in Ubuntu as its issues make it almost unusable)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * What else behaviour would you expect?

 This will help us to find and resolve the problem.

[marco.pallotta (marco-pallotta)]

Sebastien, yes it's reproducible (I tested this in two different fresh installations) even if sometimes, the problem seems to disappear. Anyway:

1) import a key with seahorse (the keys is put under collected keys)
2) sign the key and apply a trust level, for example, equals to "full"
3) try to send a new message, with evolution, to the owner of the previous key, and select "encrypt with pgp" in the security menu
4) when you click "send" you will have the issue (obviously I expect the email was sent as I signed the key so I have verified that the key belongs to the recipient user)

Possible ways to bypass this is:
1) via gpg cli, set the trust level of the key to "ultimately" (with seahorse you cannot as this trust level seems to be reserved automatically to own private key); obviously this isn't right as I shouldn't have to set this level of trust to send encrypted emails
2) checking the option "Always encrypt to myself when sending encrypted messages" but also this is not right as this option is not intended to choose if to send or not to send an email but to view pgp encrypted sent messages stored in "sent" folder

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.