Reply to topic

Cannot send encrypted email from Kmail2

rraab
Registered Member
Posts
3
Karma
0
Hello all,

With the recent revelations here in the US about PRISM and such, I've been trying to get OpenPGP encryption set up between myself and a relative. I have myself a private & public key, and said relative's public key on file. I have my private key set in my Identity in Kmail. When I compose a message to my relative and click "encrypt" on the toolbar, the blue bar that says "message will be encrypted" appears.

However, when I click send, things start going wrong. First, Kmail warns that the recipient's public key isn't trusted (even though I set the key's trust one level below complete), and then I click continue. It asks me to verify the recipient's public key and encryption preference. I click OK on that dialog and the error message "Could not compose message: General error" appears in another dialog.

Afterwards, the message is neither encrypted nor sent.

Using KGPG's editor, I can manually encrypt a message-- usually. I may get "Error code 2" a few times before it works.

Any help getting KMail to encrypt messages on its own would be greatly appreciated. I'm using KDE 4.10.4 on OpenSUSE 12.3 x64, all packages installed from distro-provided RPMs. Nothing in KDEPIM or GPG is self-compiled. I'm using GPG 2.0.19, on linux kernel 3.7.10-1.11-desktop.
User avatar einar
Administrator
Posts
2285
Karma
5
OS
Do you have gpg-agent running? Do you have pinentry-qt4 installed as well?

I've been signing and encrypting mails for a long time without issues, so that's likely some communication problem between KMail and the rest of the stack.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
rraab
Registered Member
Posts
3
Karma
0
I do indeed have gpg-agent running, and I do have pinentry-qt4 installed.

Perhaps GPG has a log somewhere that could shed some light on the situation?

EDIT: So I set up gpg.conf and gpg-agent.conf to log to a file, and I saw that the encryption failed because GPG still didn't trust the public key. I changed said key trust to ultimate and signed it with my secret key, and now it works.

I had no idea GPG was so paranoid. In a way, I'm glad it is.

And thank you for your reply, einar.

 
Reply to topic

Bookmarks



Who is online

Registered users: afiestas, arojas, avishekk, Baidu [Spider], Bing [Bot], bjoernbalazs, Cris70, edmael, epsi1on, Exabot [Bot], ggael, Google [Bot], google01103, Hans, ivan, jgrulich, joshaughnessy, jstaniek, koriun, La Ninje, Majestic-12 [Bot], MSNbot Media, ooker, scummos, sinclair, Sogou [Bot], TheraHedwig, Tioz, Yahoo [Bot]