Closed Bug 228127 Opened 22 years ago Closed 22 years ago

Secure authentication fails

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: andrewm, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 As of 1.6b release, secure authentication on my IMAPS server fails. All previous releases (example 1.6a) work fine. Dialog: "You cannot log into mail.somedomain.com because you have enabled secure authentication and this server does not support it. To log in, turn off secure authentication for this account." The server log contains: "Command stream end of file, while reading line user=??? host=UNKNOWN" Reproducible: Always Steps to Reproduce:
And? Switching "secure authentication" off as the dialog writes doesn't help? If not, please post a communications log (see http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap for how to). See bug 225809 for why you get this error.
Component: Security: General → Networking: IMAP
Yes, switching off the Use Secure authentication makes it possible to read e-mails again using IMAP.
Ok, so marking it WFM. It's a little bit annoying, but reliably only performing secure authentication when this option is checked improves security.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
The authentication problem coincides with: Received: from isoar.ca (fujitsu.isoar.ca [192.168.2.254]) (authenticated bits=0) by mail.isoar.ca (8.12.8/8.12.8) with ESMTP id hBIBNs0I013027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <andrewm@netwinder.org>; Thu, 18 Dec 2003 06:24:00 -0500 Notice that "verify=FAIL" when in the past it was "OK". I assume these two are related as nothing on the server has changed.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.