[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 00:38) wrote:

No IMAP log produced, no traffic with the IMAP server. Cleared all  
caches, disabled them. Git bisect shows this is the culprit:

mrubinsk at singularity:horde ((no branch, bisect started on master))$  
git bisect good
227e17105ca4e5878f2110c5ade26a3163782a0b is the first bad commit
commit 227e17105ca4e5878f2110c5ade26a3163782a0b
Author: Michael M Slusarz <slusarz at horde.org>
Date:   Wed Oct 16 15:04:07 2013 -0600

     Use Socket_Client package

:040000 040000 ad07dc0dd1410a8b2247fc97847e6b79939da23a  
16ea6b04fb6f44ad0973a63b351bf8399fab84a7 M      framework