From a conversation with a customer: Sample session: -A sends encrypted email to B and C -B replies to A, but does not have C's cert -mail client tells B that it does not have C's cert and asks the user if it is OK to send anyway, and presents two dialogs: [OK] [Cancel] In Communicator 4.x, the default is [OK], when it should be [Cancel]. The user should have to take the extra step to send the mail unencrypted when the original source was encrypted.
Component: Security: Crypto → Security: General
Assignee: ddrinan → ssaux
Component: Security: General → S/MIME
Product: MailNews → PSM
QA Contact: lchiang → alam
Version: other → 2.2
Summary: encrypted email replies should be encrypted unless user clicks [OK] → [UE] encrypted email replies should be encrypted unless user clicks [OK]
I just noticed this bug as well. I'd like to see this fixed too.
My understanding is that the fix to 137071 decreases or invalidates the relevance of this bug. We now set the status of a reply or forward to an encrypted message to "Encrypt". The user will either send encrpted or will have to explicitly say "Do not Encrypt".
Target Milestone: 2.2 → Future
I would have to agree - Bob, any objections to resolving this as either invalid or won't fix? If so, please reopen. Bug 137071 changes the default behavior now. combined with the current inability to send a message if a user cert cannot be found, this bug is no longer valid. Once an 'encryption when possible' comes into being, the default button selection can be addressed there.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
Component: Security: S/MIME → Security: S/MIME
Product: Core → MailNews Core
QA Contact: carosendahl → s.mime
You need to log in before you can comment on or make changes to this bug.