[Tickets #12772] Re: Unable to authenticate after recent Horde_Imap_Client / Horde/Client/Socket changes.

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12772
------------------------------------------------------------------------------
  Ticket             | 12772
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Unable to authenticate after recent Horde_Imap_Client /
                     | Horde/Client/Socket changes.
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-10-17 03:21) wrote:

In Horde_Imap_Client_Socket::_connect() the code:

             if (!$this->_connection->secure) {
                  $this->setParam('secure', false);
             }

seems to be called before TLS is started, and sets the secure  
parameter to false, so that in ::_login(), in the code to switch to  
TLS if not secure never gets called since $this->getParam('secure')  
will return false, and not 'tls' like I have configured.

Commenting out the code in _connect() that sets secure to false  
"fixes" it for me. No idea how to fix it properly.