[Tickets #8478] Bad or malformed request. Server Responded: Command unrecognized: LOGIN

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8478
------------------------------------------------------------------------------
  Ticket             | 8478
  Created By         | bhalsema at purdue.edu
  Summary            | Bad or malformed request. Server Responded: Command
                     | unrecognized: LOGIN
  Queue              | IMP
  Version            | 4.3.4
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


bhalsema at purdue.edu (2009-08-04 13:36) wrote:

Software that we are running:

         * Horde Groupware Webmail Edition (version 1.2.3) (IMP 4.3.4)
         * UW-IMAP (version 2007e)

Webmail is configured to authenticate using the IMP application.

The handling of the NO response for untagged responses doesn't appear  
to be consistent with RFC 3501 Section 7.1.2 (NO Response).

         http://www.rfc-editor.org/rfc/rfc3501.txt

 From what I can tell from the logs and the corresponding code, the  
handling of the response is done in the case statment found in the  
_runCommand() function in
the file

         horde/imp/lib/IMAP/Client.php

We noticed this behavior while testing the following scenario:

* We use the IMAP host's native account expiration.

* From the time that the expiration field is set and excluding its  
final day, the status information, displayed by IMP (as provided by  
the IMAP server via an untagged alert), is correct:

         Account expires in x days(s)!

* On the final day (the account has not yet expired), the login  
attempt fails, and the following informational message is provided on  
the Horde login page:

    Bad or malformed request. Server Responded: Command unrecognized: LOGIN

* The expected behavior is a successful login and the status:

         Account expires today!

When we look at the untagged IMAP server responses for the two cases  
they were:

         * NO [ALERT] Account expires today!
         * OK [ALERT] Account expires in x day(s)!

Here is an excerpt from our logs:

-------------
Aug  3 16:38:20  HORDE[14505]: [imp] Could not complete request.  
Reason Given: [ALERT] Account expires today!: NO [pid 14505 on line  
382 of "/opt/horde-webmail-1.2.3/imp/lib/IMAP/Client.php"]
Aug  3 16:38:20 HORDE[14505]: [imp] Bad or malformed request. Server  
Responded: Command unrecognized: LOGIN: BAD [pid 14505 on line 382 of  
"/opt/horde-webmail-1.2.3/imp/lib/IMAP/Client.php"]
Aug  3 16:38:20 HORDE[14505]: [imp] IMAP alerts: [ALERT] Account  
expires today! [pid 14505 on line 170 of  
"/opt/horde-webmail-1.2.3/imp/lib/IMAP.php"]
-------------