Re: [Evolution-hackers] Support for LIST-EXTENDED's SUBSCRIBED parameter

2007-12-20 Thread Philip Van Hoof
I further changed Camel-lite in such a way that only the following protocol conversation takes place: if CAPABILITIES contains NAMESPACE - NAMESPACE - NAMESPACE ((namespace that matters dir_sep_char) ... ) # Camel ignores the other namespaces (this is bad!) item = namespace that matters +

Re: [Evolution-hackers] Support for LIST-EXTENDED's SUBSCRIBED parameter

2007-12-20 Thread Philip Van Hoof
This is some first piece of code to parse the other namespaces In: imap_connect_online result = camel_imap_response_extract (store, response, NAMESPACE, ex); if (!result) goto done; #if 0 /* new code... */

Re: [Evolution-hackers] Support for LIST-EXTENDED's SUBSCRIBED parameter

2007-12-20 Thread Philip Van Hoof
Oh, and it's wrong. It seems that an IMAP server can send an multiple parameters after the directory separator for a namespace. So after the directory separator, the ptr should be read skipping each \string\ until )) is seen. And it seems that it's a skiplist, so a parameter can be a SOMETHING

Re: [Evolution-hackers] Support for LIST-EXTENDED's SUBSCRIBED parameter

2007-12-20 Thread Philip Van Hoof
On Thu, 2007-12-20 at 21:46 +0100, Philip Van Hoof wrote: This is some first piece of code to parse the other namespaces Forget that, imap_parse_namespace_response implements this already and looks like a fine starting point. -- Philip Van Hoof, freelance software developer home: me at

[Evolution-hackers] Support for LIST-EXTENDED's SUBSCRIBED parameter

2007-12-19 Thread Philip Van Hoof
The net result of this patch is less round trips when connecting with an IMAP server that has support for LIST-EXTENDED. http://tinymail.org/trac/tinymail/changeset/3155 Note that Evolution merges LIST and LSUB together. This is wrong behaviour. An item not in LIST yet in LSUB simply doesn't