[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 12:33) wrote:

> Still same behavior, with the same workaround fixing it.

The problem is that since I am using TLS,  
Horde/Socket/Client::_connect will NOT set $this->_secure to true so  
the check in Horde_Imap_Client_Socket::_connect on line 557:

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

will always set 'secure' to false. Therefore, TLS will never be  
started in Horde_Imap_Client_Socket::_login.