GNOME Bugzilla – Bug 204029
"wants to receive encrypted mail" contacts option
Last modified: 2021-05-19 11:46:13 UTC
It would be nice if Evolution could always try to encrypt outgoing mail - not sure how this would be implemented unless/until Evo uses a pgp/gpg glue library (like pgg rather than fork()ing the executable). One possibility would be that the user has to associate a gpg/pgp key with entries in their contacts. The basic idea being that if you have a public key for the address you're sending mail to, Evo should allow you to configure it to encrypt that mail by default.
Let me first say that there have been no updates to pgg in over a year and a half, which is why Evolution doesn't use pgg.
this should be handled like the html preferences for members in an addressbook. It would make things a whole lot simpler. Just a check box that said: wants to receive encrypted mail
sounds reasonable to me.
*** bug 208150 has been marked as a duplicate of this bug. ***
jeff: did this finally get implemented? comments on bug 205667 seem to indicate yes, but I don't have the very latest build here at home so I can't verify.
at the risk of speaking for Jeff I believe the answer is "no" - there are two different, but similar bugs - the one that has been resolved is the ability to sign >all< outgoing mail. This one is requesting the ability to tag individuals in your contacts to whom all mail should be encrypted.
Dan is 100% right on the money. This hasn't been implemented yet, and it's looking like it may not happen till a future version (1.1?) Since S/MIME is planned for 1.1, maybe this'd make a nice addition?
nominating for 1.1, then... not that there is a procedure for that but I agree it would make a useful companion to the S/MIME work. Perhaps it could also be not just per contact but also enable-able per domain- i.e., I could say 'if to any_address@ximian.com encrypt it'? I'd think that would be very useful for people in corporate settings.
re: selecting by domain - interesting idea, however encryption keys are per user - so unless you have keys for every user in a given domain, evo won't be able to encrypt outgoing mail.
Awesome idea! Personally I don't know anybody who (has told me s/he) prefers HTML messages, but I'd really like to be able to select certain contacts that will A) get PGP-signed and/or B) PGP-encrypted mail. ...and I though I like Louis' domain-wide encryption idea, I think it would be difficult to implement (where to stick in the UI?) and Dan also has a good point re the availability of keys...
*** bug 215091 has been marked as a duplicate of this bug. ***
It would be nice to add another address book option for bug 217541 (in-line pgp). This would help you cater to owners of broken email clients and still use proper rfc PGP/MIME for people with working mailers.
*** bug 217100 has been marked as a duplicate of this bug. ***
*** bug 212106 has been marked as a duplicate of this bug. ***
*** bug 225425 has been marked as a duplicate of this bug. ***
*** bug 227947 has been marked as a duplicate of this bug. ***
*** bug 219814 has been marked as a duplicate of this bug. ***
*** bug 212661 has been marked as a duplicate of this bug. ***
*** bug 201760 has been marked as a duplicate of this bug. ***
*** bug 223950 has been marked as a duplicate of this bug. ***
*** bug 231313 has been marked as a duplicate of this bug. ***
*** bug 212901 has been marked as a duplicate of this bug. ***
*** bug 248793 has been marked as a duplicate of this bug. ***
*** bug 235885 has been marked as a duplicate of this bug. ***
is this feature in Plan? or wont you implement this. I think it would be a very nice feature!
It is.
Too late for 2.0.
*** bug 242744 has been marked as a duplicate of this bug. ***
Whats up guys. This is still a VERY IMPORTANT issue for anybody who is using encryption. Without it people tend to forget about signuing mails, because you always have to uncheck before sending. Another possible solution: We could have three buttons when "allways sign mails" is on after submitting a mail: 1. Submit 2. Don't Sign 3. Cancel Right now we only have 1 and 3. This wouls also make this very much easier. I am a bit frustrated that his important issue has not ben touched für 3 years now. I think it would be number one on my list. I suppose very few developers use gpg?
thilo: your request is a duplicate of bug 212488. adding "mostfreq" keyword (15 dups should be enough imho ;-).
Is it possible that addressbook options "Doesn't want to receive signed mail" and "Doesn't want to receive encrypted mail" will be implemented in final 2.2? Sorry to harras you, but the feature is extremely important for interoperability with other mailers (e.g. old Outlook...)
retargetting to 2.5. latest comment would be bug 318059
*** Bug 312939 has been marked as a duplicate of this bug. ***
*** Bug 342792 has been marked as a duplicate of this bug. ***
Devashish : Can I add this to the Two Ten basket ?
Is there any chance of adding this feature?
Bumping version to a stable release.
I would suggest having this in the addressbook also, but include both positive and negative options, and for signatures also... So there is both an "always encrypt to this address" and a "never encrypt to this address"... and the same for sign. This would allow you to set a global always encrypt/sign flag, and then negate it for individual addresses, or a global never encrypt/sign... and then specify that specific users need it.
I wanted to fill similar bug but I will just post comment here. Could global option "sign always if the key in in keyring" exist?
I know this is only an enhancement request, but after 8 years isn't is slightly embarrassing that we've not managed to do this, it's quite simple and quite possibly somthing that would encourage corporate uptake...
This is the one feature that keeps me from moving to Evolution. Other mailers (kmail, thunderbird and even Mail.app on OS X) have this most basic feature.
Want to promote this bug as well. It is such a long issue and i remember back then there was talk about making the whole of the lacks in PGP functionality a GSoC project. Several summers have passed and nothing happened. Please, can we put some priority on this? I'm often not encrypting mails to my PGP-enabled contacts simply because i forget to re-select the menu entry. Enigmail for Thunderbird does this pretty well, as far as i remember and can therefor be used as a 'spec'.
Heh, kinda pretty old bug this ist :) I want to second the request for an option to encrypt outgoing messages by default. As forgetting to do the 2 clicks to enable the encryption for every message happens quite too often. Thanks alot to the devs!
Status: NEW This is obviously some strange new usage of the word "New" that I wasn't previously aware of. Sorry for the gratuitous Douglas Adams quote, and I know you guys are working hard to get ready for 2.30, or 3.0 whichever it will be, but please please please, can we finally have some love for this request.
The step on from NEW is ASSIGNED, so unless you are offering to work on it yourself then it's going to stay in NEW until someone else steps up to work on it. Remember that NEW isn't the initial state, that is UNCONFIRMED. NEW means it's a valid bug report that has been read and triaged.Thanks for taking the time to report this bug.
*** Bug 644155 has been marked as a duplicate of this bug. ***
*** Bug 386665 has been marked as a duplicate of this bug. ***
*** Bug 386667 has been marked as a duplicate of this bug. ***
*** Bug 676519 has been marked as a duplicate of this bug. ***
*** Bug 420211 has been marked as a duplicate of this bug. ***
*** Bug 259164 has been marked as a duplicate of this bug. ***
*** Bug 681706 has been marked as a duplicate of this bug. ***
*** Bug 681705 has been marked as a duplicate of this bug. ***
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.