GNOME Bugzilla – Bug 252111
Mailer defaults encrypted mail to unencrypted when responding
Last modified: 2016-04-18 11:22:08 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: When I receive email that's been GPG encrypted, and then reply to it, evolution does not re-encrypt the message. In fact, the "PGP Encrypt" option in the menu is unchecked. This results in accidentally sending unencrypted mail, repeatedly. Steps to reproduce the problem: 1. Send yourself a gpg encrypted message 2. Reply to it in evolution 3. Read the reply, and notice that it is unencrypted Actual Results: Plaintext mail is sent. Expected Results: Encrypted mail should be sent. How often does this happen? 100% of the time Additional Information:
probably a dup
I too find this bothersome. I don't think there has been a single case I have not wanted to encrypted a reply to an encrypted mail.
updating version number, still missing in 2.0.3, also want this :-)
...or forwarding, see dup bug 268917 for this. adding keyword.
*** bug 268917 has been marked as a duplicate of this bug. ***
oh, fixing typo in the summary by the way
still in 2.3.7
uhm, would be cool to also support inline-pgp as we're now having that gorgeous plugin by matt (see bug 217540)... :-)
*** Bug 320833 has been marked as a duplicate of this bug. ***
This would be a very important security enhancement. People often leave parts of the original as they make comments in their replies. Security shouldn't rely on users remembering manually checking encrypt on their responses. This should of course work for S/MIME as well as PGP.
*** Bug 343478 has been marked as a duplicate of this bug. ***
Bumping version to a stable release.
Has there been any progress on this issue? The report is remarkably old for such an (from my point of view) rather simple issue, and it is still unfixed as of Evolution 2.26 (didn't find anything on this in the 2.28 changelog either). I regard this as a considerable security problem; It's dangerous to undermine people's security efforts by accidentaly replying unencrypted - some people do not find this funny at all. As a consequence, I had to use other MUAs for certain conversations just to make sure - which is annoying since Evolution is exactly what I want in all other respects. I've seen this implemented as a boolean option like "Encrypt replies to encrypted emails" ("true" would be a sane default) which is respected when replying. A warning shown when replying unencrypted to encrypted emails as seen in some MUAs would certainly be a plus, and I'd actually already be over the moon with just that for now.
This is still an issue - And one I would expect given considerably higher priority. I upgraded to Ubuntu 9.10 over the weekend and have just 'leaked' sensitive information because a. In replying to an encrypted mail from a Thunderbird user, the mail was decrypted for me to read - but the reply prompted me with the ASCII-armoured message. I had to cut and paste segments from the automatically decrypted version in my Inbox. b. There is no option to encrypt by default where you have a key, or to make certain addressbook entries as "must encrypt" c. Any reply to an encrypted email should throw up great big warnings if you've not sending encrypted. d. If sending to a mix of recipients where you can encrypt to some - but not all - you should get warnings, option to only send to those you can encrypt to, &c. e. (possibly unreported elsewhere). Evolution *should* have an automatic, but disable-able option that when sending an encrypted message you get warned to "sanitise" the subject and not have anything about the message contents 'leaked' in that way.
*** Bug 581474 has been marked as a duplicate of this bug. ***
*** Bug 632525 has been marked as a duplicate of this bug. ***
I believe that this issue has been fixed since at least Evolution 3.2.3 Replying to encrypted mails will create a new encrypted reply.
I can confirm that this issue has been fixed. Works fine in Evolution 3.12.x and 3.16.x
Closing as per last two comments. Thanks for retesting!