122933 - NSS 3.4 Unable to send signed message with 20020128-115010 build

Status: VERIFIED WORKSFORME

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

Description

[Antonio Lam]

Build: /u/kaie/mozilla-win32-nss34-20020128-115010.zip

Try to send a signed message using dual-key certs give me the following error 
message:

"Sending of message failed.
Please verify that your mail account settings are correct and try again"

When I used the latest trunk build (2002013003) to open the cert manager, I 
notified that the user's encrypting cert has moved to the "Other's People", and 
"Your Certificates" has only the signing cert presented. However, it showed 
correctly in the NSS 3.4 enabled build.

I have used the trunk build 2002013003 to confirm that I can send a signed 
message, then I used the NSS 3.4 enabled build with exact same profile to send a 
sign message but failed.

I have also tried to create a brand new profile, import the user certs, enable 
the CA's trust bits, select both signing/encrypting cert, and try to sign a 
message, but same problem occurs.

Comment 1

[Antonio Lam]

Raise severity to "blocker" since this bug is blocking me from running any of 
the signing messages test cases.

Comment 2

[[not reading bugmail]]

"Sending of message failed.
Please verify that your mail account settings are correct and try again"

-I get this message all the time with not have a Outbound SMTP server setup
after creating a newsgroup account with a new build.  Here is how this relates..
do you have a outbound SMTP server set?  does this affect your problem?

Comment 3

[Antonio Lam]

Dennis, I don't have a outbound smtp server setup. 
And this problem only happened with NSS 3.4 enabled private build provided by 
the developer.  It worked just fine using the nightly trunk build.

Comment 4

[Antonio Lam]

Tried /u/kaie/mozilla-win32-nss34-20020201-115010-115209-122961.zip, and I still
see the same problem...

Comment 5

[Stephane Saux]

kai
We have to wait till 3.4 to be able to look at this in a meaningfull way.

Comment 6

[Antonio Lam]

Tried with commercial trunk build 2002020803 (with NSS 3.4).  I am not able to 
reproduce this problem. Sending signed message worked for me now.

Comment 7

[John Unruh]

Verified works for me.