[Tickets #8131] Re: IMAP literal read timeout

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8131
------------------------------------------------------------------------------
  Ticket             | 8131
  Updated By         | Michael Slusarz <slusarz at horde.org>
-Summary            | IMAP continuation problem
+Summary            | IMAP literal read timeout
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-04-02 00:42) wrote:

FWIW, I can't reproduce but this has something to do with my efforts  
to change all stream reading to fread().  My goal: I was playing  
around with the COMPRESS IMAP extension - and reading data in from the  
stream using fgets() is not possible (since it is not clear from the  
RFC whether the line breaks are also compressed or not).  Regardless,  
it is a moot point for now since the only practical way of doing  
stream compressions (using PHP filters) can't be done due to the  
overall lousiness of the PHP compression filters - there is no way to  
indicate that you want the output buffer to be flushed.

Long winded way of explaining that I reverted back to the fgets() for  
most commands.  This should fix things - although I have  
moved/consolidated the code a bit so this is not a straight revert.  A  
confirmation that this fixes would be great.