Closed
Bug 232391
Opened 21 years ago
Closed 21 years ago
IMAPS login fails with "Use Secure Authentication"
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: johnw, Assigned: Bienvenu)
Details
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
1) Mozilla 1.5 mail account settings successfully logs into mail server:
Server Settings checked: use secure connection (ssl), use secure authentication
2) Mozilla 1.6 with same settings fails to log into mail server with message:
"You cannot log into host because you have enabled secure authentication and
this server does not support it. To log in, turn off secure authentication for
this account."
Corresponding mail server maillog says:
"Jan 28 00:34:40 JUPITER imapd[8278]: Command stream end of file, while reading
line user=??? host=MARS [192.168.0.3]"
3) After turning off secure authentication for this account, it successfully
logs into mail server.
4) Strangely, after turning back-on the "Secure Authentication" checkbox,
mozilla 1.6 client continues to successfully log into mail server.
5) Exit and restart of mozilla 1.6 with "Secure Authentication" checked results
again as in (2) above.
Mail server in this test is: Redhat AS-2.1 with sendmail-8.11.6-28.72 and IMAPS
enabled.
Reproducible: Always
Steps to Reproduce:
1. configure mozilla 1.6 mail account and check "Use Secure Connection", "Use
secure Authentication", and port 993. Click OK.
2. Click "Get Msgs" button
3. see error message reported above.
Assignee | ||
Comment 1•21 years ago
|
||
this is invalid - 1.5 would silently fall back to non-secure authentication,
leading you to think that your server supported secure authentication (CRAM-MD5)
and we were using it. 1.6 tells you if your server doesn't support secure
authentication and doesn't fall back to non-secure authentication. So the actual
bug was with 1.5, and your server doesn't support cram-md5.
IMAPS, or SSL IMAP, is distinct from secure authentication. If you're connecting
over SSL, there's not much reason to turn secure authentication on.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•