User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312 Error code: -8075. cannot establish SSL connection with mailserver. Reproducible: Always Steps to Reproduce: 1.Open inbox on mailserver. 2. 3. Actual Results: Error establishing an encrypted connection to mail.xxxx.com. Error code: -8075. No SSL connection with mailserver. Expected Results: Establish SSL and request user certificate.

has your cert expired? Can you connect to other mail servers via ssl?

this bug doesn't contain anything confidential so i'm clearing the flag.

WorksForMe using FizzillaMach/2003-04-15-08-trunk connecting to an SSL IMAP server.

According to the NSS documentation on page http://www.mozilla.org/projects/security/pki/nss/ref/ssl/sslerr.html#1038501 error code -8075 means: "The location for the certificate status server has invalid format." This sounds like a problem with the server's cert. Is mail.xxxx.com really the server name?

my cert is fine. works at other locations. found my problem. mozilla mail client was set up for OCSP responder that was unavailable. i would expect an "unable to validate" warning rather then an "cannot do SSL -8075" error? i did not encounter this with 1.0.? i am working fine now, your call on the mozilla mail client's response to the user.

-> Nelson, if it's a case of which error code the seclib stuff returns. his call about how to resolve the bug.

It sounds to me like this bug has transmuted into yet another complaint about mozilla/PSM's poor error messages, which often show only a number, or (in some cases) merely say "unknown error occured", even though the NSS error code number that generated the message was distinctly meaningful. There is already at least one other bug filed about that problem. I will try to find that bug and mark this one a duplicate of that one.

Changing product to PSM, before reassigning to PSM owner

This bug is yet more proof that bug 107491 remains unfixed.

*** This bug has been marked as a duplicate of 107491 ***