Closed
Bug 122933
Opened 23 years ago
Closed 23 years ago
NSS 3.4 Unable to send signed message with 20020128-115010 build
Categories
(MailNews Core :: Security: S/MIME, defect, P1)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
psm2.2
People
(Reporter: alam, Assigned: KaiE)
Details
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.
Reporter | ||
Comment 1•23 years ago
|
||
Raise severity to "blocker" since this bug is blocking me from running any of the signing messages test cases.
Severity: normal → blocker
Comment 2•23 years ago
|
||
"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?
Reporter | ||
Comment 3•23 years ago
|
||
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.
Reporter | ||
Comment 4•23 years ago
|
||
Tried /u/kaie/mozilla-win32-nss34-20020201-115010-115209-122961.zip, and I still see the same problem...
Comment 5•23 years ago
|
||
kai We have to wait till 3.4 to be able to look at this in a meaningfull way.
Assignee: ssaux → kaie
Priority: -- → P1
Target Milestone: --- → 2.2
Reporter | ||
Comment 6•23 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
URL: http://http://
You need to log in
before you can comment on or make changes to this bug.
Description
•