136212 - S/MIME security preference should follow account defaults after switch

Status: RESOLVED EXPIRED

(MailNews Core :: Composition, defect)

Description

[Michael Baffoni]

I have two IMAP accounts, IMAP1 and IMAP2.  In IMAP1 (my primary account), I
have a digital signature setup, and no digital signature setup in IMAP2.  I have
IMAP1 setup to always sign outgoing email.  IMAP2 account is left at the default
grey (no certificates selected).

What happens:
When I click compose to send email (IMAP1 is the default), email is sent
properly, and messages are signed.
When I click compose to send email, I switch the "from" from IMAP1 account to
IMAP2, but it attempts to send the message digitally signed by default, and I
have to unselect the "digitally sign" checkmark, even though I don't have any
certificates selected or enabled.

What is expected: the preference to digitally sign should follow the preference
of the "from" account - if I change from IMAP1 to IMAP2, the digitally signed
preference (not to sign) should follow, just as if I change back to IMAP1, the
preference to automatically sign should be implemented.  In no case should I
have a preference to sign be enabled when no certificates are setup with that
setting (digitally signing should be disabled).

Comment 1

[Michael Baffoni]

Sorry, forgot:

Build ID 2002040403, Win2k

Comment 2

[Jason M. Abels]

Seems valid enough.

Reporter: can you confirm this still happens on a recent build?

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.