Comment 5 for bug 365315

Point 1 is not a problem with seahorse since even gpg thinks your key is not signed with a trusted signature. You have to trust at least one of the keys which signed the key. You can adjust the trust settings in seahorse or the gpg-commands to accomplish that.

Point 2 isn't a real problem, too. Check in the security-settings of evolution that you do not have an option like "always encrypt to self" activated, check the same for System->Preferences->Encryption and Keyrings. With this option active, you are supposed to be able to decrypt a message. It still will be decryptable by the key of your friend. That's how gpg/pgp works.

I'm closing here since what you reported does not look like a bug in seahorse. As a general reminder, you can always open a support question on https://answers.launchpad.net and will get quality help. Thanks for your understanding.