140067 - Reset Master Password removes certs but doesn't update Mail Account Settings.

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[esther]

Reset Master Password removes Certs.  However, the MailNews Account Settings is
not updated regarding mail accounts that have selected to Sign and Encrypt mail
messages using certs.  Result: Sending Fails.

1. Launch App
2. Add a Cert so you can Sign and Encrypt mail messages. (done through
Preferences Privacy and Security Certificates), to see this right away select
Ask Every Time.
3. Launch Mail, go to the mail account for the cert you added and select
Security to turn on Signing and Encrypting mail messages.  Use the Select button
to retrieve a list of the certs you have, choose one and then check the box for
signing.
4. Send a mail message, you should be prompted for the Master Password.  Give it
and confirm it's working.
5. Click on Reset Master Password from the Tools|Password Manager| menu
Note: this removes the cert.
6. Try to send a message, you will get a message that Sending failed because you
still have that mail account set up for signing and encrypting even though you
have removed the cert via Reset Master Password.
7. Exit and relaunch you still can't send until you uncheck the Security box in
Account Settings.  Note: the cert is still listed even though you have removed.

Major confusion for the Mail user due to the Password Manager fix (102709) to
replace menu item Clear Sensitive Information with Reset Master password, not
just a name change but a functionality change where the cert is deleted.

Comment 1

[esther]

Note: if user had checked the radio button for Required Encryption as well as
Signed then Reset Master Password (deleting cert) when they uncheck the
Digitially Signed box as in #7 to avoid the error when sending, they can now
send but recipient will get an broken encryption icon. 

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420