GNOME Bugzilla – Bug 662914
Reply to gnupg signed mails should be signed
Last modified: 2011-11-14 14:25:21 UTC
The summary says all. Basically when you reply to encrypted mail, the data is sensitive so the reply should be encrypted too. Selecting that by default makes sense.
Thanks for a bug report. This had been addresses in bug #545851. What is the message structure you are replying to, please? Seeing the change in the other bug then the functionality depends on message itself, thus to cover your case, the test should be extended for those types too.
Are you sure it's related? #545851 seems to be only about sending mail and editing sent mails. In my case, I receive a GPG-signed and/or GPG-encrypted mail (wether inline or PGP/MIME). In this case, when replying, I think the reply should, by default, have the same security settings as the initial mail.
Yup, the change in the bug makes sure that options for Security in composer for Sign/Encrypt are checked if user replies to signed/encrypted message. If this works fine for you for non-inline signatures/encryptions, then fine. With inline signatures/encryptions it'll be slightly harder, and that case doesn't seem to be covered by the aforementioned bug.
Well, then I can confirm it doesn't work for GPG mails, wether inline or GPG/MIME, in 3.0.
(In reply to comment #4) > Well, then I can confirm it doesn't work for GPG mails, wether inline or > GPG/MIME, in 3.0. The applies my question from comment #1.
Sent direct signed mail to Milan so he has the messages to work on.
Thanks, I can reproduce it too, and I found the reason, it's bug #607595 for signed messages. The gpg encrypted message should work, though (mine GPG key ID is F3C36A0D).
(In reply to comment #7) > Thanks, I can reproduce it too, and I found the reason, it's bug #607595 for > signed messages. The gpg encrypted message should work, though (mine GPG key ID > is F3C36A0D). Indeed, encryption work. In my case, I disagree with Adam, I'd prefer to sign by default when people send me signed mail :) Not sure what we can do from now.
It sounds like a need for an option somewhere.
Created attachment 201370 [details] [review] evo patch for evolution; This adds an option to Edit->Preferences->Composer Preferences, at the very bottom of that page.
Created commit 78a2a77 in evo master (3.3.2+)