[dev] [commits] Horde branch master updated. f494c3628019c2d3e00843ff4d959bb200c2ef00

[Jan Schneider]

> commit bf660243870932de6bcacd54f4dec6c376cc5226
> Author: Michael M Slusarz <slusarz at horde.org>
> Date:   Thu Aug 29 16:12:13 2013 -0600
>
>     Revert "Revert "[mms] By default, use TLS if available and  
> necessary to login to server.""
>
>     This reverts commit 6daa00469d213bb4483af15b7512bb75a10f4ba0.
>
>     Your IMAP server is totally hosed.
>
>     S: * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE  XIMAPPROXY]  
> neo Cyrus IMAP v2.4.16-Debian-2.4.16-4 server ready
>     C: 1 STARTTLS
>     S: 1 BAD Please login first
>
>     Login before starting TLS?  Nothing like sending your auth credentials
>     in plaintext before starting encryption.
>
>     But the main issue is instead that your server doesn't advertise/support
>     STARTTLS, which is MANDATORY under IMAPv4rev1 (RFC 3501 [6.1.1, 7.2.1, 9,
>     11.2, etc., etc.]).  Not sure why it didn't throw an Exception a line
>     before the STARTTLS is issued, (although it won't throw an Exception if
>     this was an already existing Horde_Imap_Client and you upgraded in the
>     middle of a session, which obviously won't work).

This is actually not the server which is broken, but imapproxy.  
Disabling imapproxy logging in works and the capability line looks  
correct too:

S: * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE STARTTLS AUTH=PLAIN  
SASL-IR] neo Cyrus IMAP v2.4.16-Debian-2.4.16-4 server ready
1 [SASL-IR AUTHENTICATE Command - method: PLAIN, username: jan]
>> CACHE: Using the Horde_Imap_Client_Cache_Backend_Db storage driver.
C: 2 ENABLE QRESYNC
C: 3 LOGOUT
S: * ENABLED CONDSTORE QRESYNC
S: 2 OK Completed
S: * BYE LOGOUT received
S: 3 OK Completed

-- 
Jan Schneider
The Horde Project
http://www.horde.org/