Closed Bug 204387 Opened 21 years ago Closed 21 years ago

Setting a message's default encryption

Categories

(MailNews Core :: Security: S/MIME, enhancement)

1.0 Branch
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 195940

People

(Reporter: john, Assigned: ssaux)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030502 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030502 Probably most people don't use the encryption, so this might not be obvious to everybody. when one installs the encryption, with certificates, etc., it implies that it's IMPORTANT (to them). They don't want to forget, even once, to encrypt certain important email, so they set the DEFAULT to "encryption/digitally signed=ON". BUT...98% of their email contacts DO NOT use encryption, so they have to change the settings, time after time after time.... If they forget, up comes the dialog box, "you screwed up, yada, yada..." Suggestion: a) set the "suggested" encryption settings at the time that the address is set in the compose operation. You can check whether you have a key for the recipient, and the user can still override it. (This doesn't address digital signing, and I've had some people say that it screws up their email client). or b) have some user-settable flags in the address book, and the user can set the default encryption/digital signing to "Get encryption/signing settings from address book" Reproducible: Always Steps to Reproduce: 1. 2. 3.
S/MIME
S/MIME
Assignee: mstoltz → ssaux
Component: Security: General → S/MIME
Product: MailNews → PSM
QA Contact: junruh → bmartin
Version: Trunk → 2.4
*** This bug has been marked as a duplicate of 195940 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: PSM → Core
Version: psm2.4 → 1.0 Branch
Product: Core → MailNews Core
QA Contact: bmartin → s.mime
You need to log in before you can comment on or make changes to this bug.