Bug 3264

Summary:	Claws Mail silently fails to encrypt after prompting for passphrase
Product:	Claws Mail (GTK 2)	Reporter:	Tim McCormack <track-clawsbugs>
Component:	Plugins/Privacy/PGP	Assignee:	users
Status:	RESOLVED INVALID
Severity:	normal
Priority:	P3
Version:	3.8.1
Hardware:	PC
OS:	Linux

Description Tim McCormack 2014-09-04 04:45:47 UTC

0. Claws 3.8.1 with PGP/Core, PGP/inline, PGP/MIME, and S/MIME plugins of same version
1. Create message, select PGP inline, Sign, Encrypt
2. Send/Send Later
3. Prompted for passphrase
4. Message sends (or goes to outbox)
5. Message has been signed, but not encrypted

I have marked this as a major bug because this is a silent failure; perhaps it should even be marked critical. I'm just glad I wasn't sending anything important when this happened to me!

Environment notes:

- I have used this feature in the past. However, that may have been before I switched from Ubuntu to Debian, so some config settings may have been lost, or program versions changed.
- I use Debian Stable, hence the slightly older version. I am willing to try other versions of Claws for bug-diagnostic purposes *if* they will not make non-backwards-compatible changes to my mail, servers, or settings.
- The only relevant console output is "WARNING: gnome-keyring:: couldn't connect to: /home/timmc/.cache/keyring-ABCDEF/pkcs11: No such file or directory", but I'll note that signing does still work.

Comment 1 Paul 2014-09-04 07:21:30 UTC

I'm pretty much certain that this is your mistake, and that you must have forgotten to check the 'encrypt' checkbox.

Comment 2 Paul 2014-09-04 07:30:58 UTC

If you can verify this then re-open it.

Comment 3 Tim McCormack 2014-09-04 13:01:42 UTC

Verified multiple times under different conditions:

* Replying to encrypted email vs. sending a fresh message (which explicitly requires checking that box)
* Using Send vs. Send Later
* PGP/Inline vs. PGP/MIME
* Sign + Encrypt vs. Encrypt
* To recipients I have one key for vs. those with multiple (incurs key selection dialog, still does not encrypt)

It's no mistake.

Comment 4 Paul 2014-09-04 13:16:42 UTC

Please look at the account preferences, "Privacy" page. Do you have the option "Save sent encrypted messages as plain text" turned on?

Comment 5 Paul 2014-09-04 13:20:22 UTC

Just to correct my typo, the option is actually called "Save sent encrypted messages as clear text"

Comment 6 Tim McCormack 2014-09-04 13:30:17 UTC

Oh lordy, yes I do. Thanks, and sorry for the heart attack. :-)

(The first time this happened, I noticed the cleartext Sent message and sent another response saying "sorry, encryption is broken in my client" and the recipient did not correct me...)