[Tickets #12265] Re: IMAP package throws errors

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12265
------------------------------------------------------------------------------
  Ticket             | 12265
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | IMAP package throws errors
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-05-28 11:40) wrote:

> Would be useful to actually explain the problem so it might get  
> fixed also for the IMAP servers affected.

I have.  Many times in the past.  We've uncovered literally dozens of  
IMAP server bugs the last few years.  You can search the list archives  
and/or the source code commits for further details on these various  
bugs.

For the record, this bug can only be triggered *if*:

1) The PHP server loses network connection to the IMAP server.  This  
could be either a network issue or a crash on the IMAP server side,  
which happens often - especially with certain older versions of  
Courier - that are triggered by a specific IMAP command.

2) The IMAP server responds to a command with a unsolicited BYE.   
Again, this should NEVER happen during a normal conversation (although  
this is something that is allowed, or at least contemplated, by the RFC)

Unfortunately, in moving things around to fix an error that I COULD  
reliably reproduce locally, these two cases were ignored.  And both  
cases are extremely difficult to write test cases for (I would  
essentially need to build a "dummy" PHP server for the test unit,  
which I don't have the time or funding for right now).

> The fact that different versions of Dovecot and also Courier are  
> affected point to a not obvious but common problem, no?

No, that doesn't mean anything.  Can't help but notice that nobody  
running Dovecot 2.1 or 2.2 are seeing anything, for example.

And FWIW, the other day I found a bug in Dovecot 2.2.2 (the latest  
version) that is not yet fixed.  Although granted, that issue would  
not trigger this bug - it's a problem with parsing CATENATE parameters  
with literal8 data.