Closed Bug 311652 Opened 20 years ago Closed 20 years ago

"server has disabled login" for IMAP client

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: fnjordy, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 Error message new in 1.5 beta 1 and 2: "You cannot log in to imap... because the server has disabled login. You may need to connect via SSL or TLS. Please check the account settings for your mail server." Thunderbird 1.0.7 works fine with the same profile settings. Reproducible: Always Server: Hula Server r313 from Hula Project (www.hula-project.com.)
Tried version 1.6a1 (20051007) same problem, however enabling SSL in the security settings works.
If the server is telling us that LOGIN is disabled, then it sounds like we're disabling login, which is what we're supposed to do. I'm marking this Invalid, but if you want to generate an imap protocol log by following the instructions below, I can tell for sure if that's what's going on. http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
So a bug in Tbird 1.0.7, and hula r313, nice. Here's the debug log, I can see the LOGINDISABLED parameter from the IMAP server: 0[274758]: 25af260:10.34.6.99:NA:SetupWithUrl: clearing IMAP_CONNECTION_IS_OPEN 6084[25ba6e0]: ImapThreadMainLoop entering [this=25af260] 6084[25ba6e0]: 25af260:10.34.6.99:NA:ProcessCurrentURL: entering 6084[25ba6e0]: 25af260:10.34.6.99:NA:ProcessCurrentURL:imap://steve-o@10.34.6.99:143/select%3E/INBOX: = currentUrl 6084[25ba6e0]: ReadNextLine [stream=24a6270 nb=80 needmore=0] 6084[25ba6e0]: 25af260:10.34.6.99:NA:CreateNewLineFromSocket: * OK yorkion.com Hula IMAP4 Agent server ready <30526d.1128859913@yorkion.com> 6084[25ba6e0]: 25af260:10.34.6.99:NA:SendData: 1 capability 6084[25ba6e0]: ReadNextLine [stream=24a6270 nb=86 needmore=0] 6084[25ba6e0]: 25af260:10.34.6.99:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4 IMAP4rev1 ACL AUTH=LOGIN NAMESPACE STARTTLS XSENDER LOGINDISABLED 6084[25ba6e0]: ReadNextLine [stream=24a6270 nb=28 needmore=0] 6084[25ba6e0]: 25af260:10.34.6.99:NA:CreateNewLineFromSocket: 1 OK CAPABILITY completed, 6084[25ba6e0]: 25af260:10.34.6.99:NA:ProcessCurrentURL: aborting queued urls 6084[25ba6e0]: 25af260:10.34.6.99:NA:SendData: 2 logout 6084[25ba6e0]: ReadNextLine [stream=24a6270 nb=36 needmore=0] 6084[25ba6e0]: 25af260:10.34.6.99:NA:CreateNewLineFromSocket: * BYE IMAP4rev1 Server signing off 6084[25ba6e0]: 25af260:10.34.6.99:NA:TellThreadToDie: close socket connection 6084[25ba6e0]: ImapThreadMainLoop leaving [this=25af260]
right, exactly, thx for the log. marking bug verified.
Status: RESOLVED → VERIFIED
PGP 9.0.3 IMAP proxy suffers from the same problem - it reports LOGINSIABLED.
You need to log in before you can comment on or make changes to this bug.