Tickets :: Comment on [#12265] IMAP package throws errors

* Your Email Address
* Spam protection	Enter the letters below: . . ..__..__ .__ \| \|__\|\| \|[ __[__) \|___\| \|\|__\[_./[__)
Comment	>> Maybe >> I'll dig it when I have time, what I know so far is that only >> yesterday it started to happen at my server, although I've updated >> the imap client over 6 days ago. > > The point being is that the current issue exposed longstanding > (known) issues with IMAP servers. The regression was the handling of > these errors. > > In other words: the recent changes to the Imap Client library would > NOT have caused any of these issues (with one exception; see below). > These errors have been occurring in your IMAP server for years. The > issue was that, in an effort to fix another issue, these errors were > not being handled properly. > > The only other change that has happened in the IMAP library has been > the implementation of pipelined commands - the sending of several > commands in a row before reading any output from the server. But > pipelining is a basic principle outlined in the base RFC (3501), so > any server that doesn't support what we are doing - which is fairly > basic pipelining - is broken in every sense of the word. > > Normally, Horde/IMP has issues because our IMAP library is on the > cutting edge when it comes to advanced extension support. I can > vouch that IMP usage and error reporting has fixed multiple bugs in > advanced extensions in both Dovecot and Cyrus. > >> What I still dont know and bugs me completely is why I am the only >> one here that had again after this update have to manually edit >> "Imap/Client/Socket.php" at line 3300 and replace >> "_queryCapability()" with "queryCapability()" to remove the >> underscore, whithout which I'd just see a "500 server error" browser >> page: >>> "PHP Fatal error: Call to undefined method >>> Horde_Imap_Client_Socket::_queryCapability() in >>> /usr/share/pear/Horde/Imap/Client/Socket.php on line 3300" > > It is off-topic, but it is a totally valid bug report. You may be > the only one seeing this because it relies on the absence of UIDPLUS. > Almost every IMAP server supports UIDPLUS so you are using one of > the rare servers that doesn't support it (either that or you have > disabled the extension in your IMP configuration). > > This issue has been fixed in Horde_imap_Client 2.11.2 and, since it > is fairly critical for these non-UIDPLUS servers, a new release has > been created.
Attachment
Watch this ticket

Saved Queries