202283 - unhelpful error message. Error code: -8075.

Status: RESOLVED DUPLICATE of bug 107491

(Core Graveyard :: Security: UI, defect)

Description

[Dan Turissini]

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.

Comment 1

[David :Bienvenu]

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

Comment 2

[timeless]

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

Comment 3

[Greg K.]

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

Comment 4

[Nelson Bolyard (seldom reads bugmail)]

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?

Comment 5

[Dan Turissini]

 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.

Comment 6

[David :Bienvenu]

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

Comment 7

[Nelson Bolyard (seldom reads bugmail)]

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.

Comment 8

[Nelson Bolyard (seldom reads bugmail)]

Changing product to PSM, before reassigning to PSM owner

Comment 9

[Nelson Bolyard (seldom reads bugmail)]

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

Comment 10

[Nelson Bolyard (seldom reads bugmail)]

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