29753 - [UE] encrypted email replies should be encrypted unless user clicks [OK]

Status: VERIFIED INVALID

(MailNews Core :: Security: S/MIME, defect, P3)

Description

[Bob Lord]

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.

Comment 1

[lchiang]

consolidating components

Comment 2

[John Unruh]

S/MIME

Comment 3

[bill]

I just noticed this bug as well.  I'd like to see this fixed too.

Comment 4

[Stephane Saux]

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".

Comment 5

[Charles Rosendahl]

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.

Comment 6

[Charles Rosendahl]

.