[dev] IMP and Archiveopteryx 3.1.3

[Michael M Slusarz]

Quoting Michael M Slusarz <slusarz at horde.org>:

> Quoting Ian Roth <iron_hat at hotmail.com>:
>
>> The recent IMP and Imap_Client releases have stopped my horde  
>> installation. The IMAP server is Archiveopteryx .... The IMP debug  
>> log when accessing the default IMP index page is as follows:
>
> [snip]
>
>> S: OK [CAPABILITY IMAPrrev ACL ANNOTATE-EXPERIMENT- BINARY CATENATE  
>> CHILDREN COMPRESS=DEFLATE CONDSTORE ENABLE ESEARCH INNNLEVEL= ID  
>> IDLE LIST-EXTENDED LITERAL+ MULTIAPPEND NAMESPACE RIGHTS=ekntx SORT  
>> SORT=DISPLAY STARTTLS UIDPLUS UNSELECT URLAUTH WITHIN] done
>
> The server announces it supports LIST-EXTENDED (RFC 5258)...
>
>> C: LIST () "" ("INBOX")
>> S: BAD Expected IMAP atom, but saw: ) "" ("INBOX")
>
> ...and then doesn't know how to parse it.  An empty list-select-opts  
> list (i.e. ()) is explicitly mentioned by the RFC as being allowed  
> (RFC 5258 [6]).
>
> Your only recourse is to upgrade, use a different server, or disable  
> LIST-EXTENDED support via imp/config/backends.local.php  
> ('capability_ignore' parameter).

Turns out this is the kind of server error we can catch and workaround  
in Horde_Imap_Client (since we can try to redo the query using base  
IMAP4rev1 commands).  So Horde_Imap_Client 2.1.4 will automatically  
workaround this.

It still would make sense to add to the capability_ignore list,  
however, since this auto-detection code comes with a performance  
penalty since the object will not downgrade functionality until it  
sends and receives a BAD response to an extended LIST command.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]