290185 - signing a mail fails if the master password was not entered before

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[kr]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050319
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050319

If the master password was not entered until a new and signed mail is composed,
this mail cannot be signed / sent.

After entering the master password (ie. checking for new mails), the newly
composed mail can be sent without problems.

Reproducible: Always

Steps to Reproduce:
1. start mozilla mail
2. compose a new mail
3. select to "digitally sign this message"
4. send the message

Actual Results:  
The mail cannot be sent:

********
Error Header: Send Message Error
Error Text: Sending of message failed.
Unable to sign message. Please check that the certificates specified in Mail &
Newsgroups Account Settings for this mail account are valid and trusted
********


Expected Results:  
1. system prompts for the master password for the PSM Internal FIPS-140-1 Cryptogr.
2. message is signed & sent

Comment 1

[Andreas Lange]

WFM in daily usage during many versions. I can only recall the described
behaviour when the specified certificate had expired.

Comment 2

[kr]

Thanks for the answer. My certs are still valid, though. So I went by and
checked other things:

If I disable FIPS within the security device manager, it works as expected. As
soon as I turn FIPS on again, it stopps again.

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.