This is Bugzilla: the Mozilla bug system. For more information about what Bugzilla is and what it can do, see mozilla.org's bug pages.

Bug processed

Bug List: (71 of 149) First Last Prev Next   Show list      Query page      Enter new bug

The next bug in your list is:

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5) Gecko/20011011
BuildID:    2001101117

On a test server, I'm running qpopper 4.0.3 which was compiled with openssl. I
have it set to listen on port 995 for pop3s connections. Eudora 5 will download
mail from it (over SSL) fine, but Mozilla gives me the following error:

"You cannot connect to jinx.unknown.nu because of as unknown SSL error (-8182)"

I'm pretty sure this is happening for one of two reasons:

Either there is some sort of incompatability with the qpopper daemon for SSL, or;

Mozilla is upset because I signed my certs myself rather than having Verisign or
whoever do it.

I suspect it's the latter; however, without more specific debugging information
I can't tell for sure. I'm not sure how to get it to tell me more.


Reproducible: Always
Steps to Reproduce:
1. Set up a server running qpopper 4.0.3-ssl
2. Sign the certs yourself on said server
3. Attempt to POP your mail on the server with "secure" selected in the Mozilla
mail server properties.

Actual Results:  I got the error ""You cannot connect to jinx.unknown.nu because
of as unknown SSL error (-8182)".

Expected Results:  Warned me that the authenticity of the cert could not be
established, and asked me if I wanted to continue; then, after I clicked "yes",
downloaded my mail normally.

Unfortunately, the server is only networked internally right now; otherwise, I'd
be happy to give a developer an account to test it with. I'd be glad to do more
extensive debugging tests if somebody can give me some instructions, or point me
to a page that has some. If the problem is indeed that the certs are locally
signed with a bogus authority, it seems to me that it ought to warn you about
the server but let you accept the cert anyway, like it does with https. Anyway,
let me know what else I can do.

I have my server online now, and I'd be glad to give an account for testing
purposes to whoever wants to work on this bug. Let me know.

Reporter,
Can you set up a test account and give the info in the bug to see this problem?
thanks

Okay, I've set up a pop-only account on the server. Please let me know when
you're done with it so I can remove it.

Username: poptest
Password: poptest
Address: poptest@unknown.nu
Server: jinx.unknown.nu

Reporter,
I tried to set up the account with the information below. I am not able to 
connect to the server without using ssl.  Is the outgoing and incoming sever 
same as jinx.unknown.nu?
I do see the error reported here when I checked ssl with the invalid 
certification error.  

But I am not able make a connection to the server even without the ssl.

That's probably because I'm not running non-SSL POP3 on there. 

Will this be a problem in diagnosing? I'd rather not enable unencrypted POP3 but
I will if absolutely necessary. If you just want to see if it works, both Eudora
5 and Outlook Express can get the mail off it in SSL mode (OE barks at you,
Eudora requires the cert be manually imported).

Finally, I could also give you a shell account on there if you like. Obviously,
I wouldn't want to give that information in the bug report, but contact me
privately and I'll set you up if you think that would be helpful.

This bug has more to do with SSL because it is failing when we are trying 
to make a connection.

cc javi/mscott who knows more about SSL

FYI: SMTP over SSL also have the same problem. Our cert is also locally signed.
However, IMAP over SSL works fine...

Changing summary -- safe to say this is not a qpopper issue.