Open
Bug 521388
Opened 15 years ago
Updated 13 years ago
Automatically encrypt e-mail if recipient has certificate
Categories
(SeaMonkey :: MailNews: Composition, enhancement)
SeaMonkey
MailNews: Composition
Tracking
(Not tracked)
NEW
People
(Reporter: bugzilla-seamonkey-ds, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090913 SeaMonkey/2.0b2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090913 SeaMonkey/2.0b2
SeaMonkey should automatically encrypt e-mails if the recipient has a certificate. This would make life much easier as one would not have to remember clicking on "Encrypt this message" every time and it would help to promote e-mail encryption.
Note that this is different from the "Default encryption required" setting.
Reproducible: Always
Steps to Reproduce:
1. Compose new e-mail to recipient with certificate
2. Forget to click "Encrypt this message"
3. Send e-mail
Actual Results:
E-mail is not encrypted automatically.
Expected Results:
E-mail is encrypted automatically.
Is this the same as MailNews Core bug 448964?
Reporter | ||
Comment 2•15 years ago
|
||
If I get it right, bug 448964 is mainly about key generation and getting certs into TB/SM. I already have my own CAcert S/MIME certificates and those of other people and would like to have SM encrypt my e-mails to them automatically.
Comment 3•14 years ago
|
||
Current options (Account Settings, Security) are:
- Never (do not use encryption)
- Required (can't send message uneless all recipients have certificates)
Having a third possibility, encrypting if (all) recipients have certificates and maybe show a warning/confirmation if not, is surely a valid RFE. Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86 → All
Version: unspecified → Trunk
There is a Thunderbird extension Auto Encryption (http://sourceforge.net/projects/autoenc/) which knows it for TB.
Reporter | ||
Comment 5•14 years ago
|
||
"Auto Encryption 0.2.5 could not be installed because it is not compatible with SeaMonkey 2.0.14."
Comment 6•13 years ago
|
||
Any progress on this?
You need to log in
before you can comment on or make changes to this bug.
Description
•