search for: rfc5267

...ETURN (SAVE COUNT) CHARSET UTF-8 (UNDELETED TEXT "foo") UID SEARCH RETURN (COUNT MIN) CHARSET UTF-8 () $ The empty paranthesis before the reference to the previous search result ($) is not legal IMAP, but should not cause the socket to be closed I think. Then I have question about RFC5267 and the announcement of CONTEXT=SEARCH in the capabilities. I think this RFC is supported by dovecot, or maybe just part of the RFC is supported? At least when I include the CONTEXT ADDTO or REMOVEFROM keywords I get an error, but UPDATE and CANCELUPDATE seem to be supported. The RFC has been...

Hello, I am looking at PARTIAL responses using a dovecot version 2.2.5 and am running into an inconsistency with the RFC which I would like to ask about. The following section http://tools.ietf.org/html/rfc5267#section-4.4 lists client requests and server responses which I have tried running against a folder, specifying the ranges that fit the contents of the folder I have selected. The Last of the?listed client requests returns a response that?is not as I would expect: C: A04 UID SEARCH RETU...

...t. :) I'm not sure when I'll have time for it. A full patch would probably have to have some session_save()/session_restore() functions in lib-storage API. But a quick and dirty way is possible to implement for v2.1 as well, as long as some IMAP extensions aren't used (most importantly rfc5267). -------------- next part -------------- A non-text attachment was scrubbed... Name: imap-state.diff Type: text/x-patch Size: 11305 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20121029/c4e6f599/attachment-0004.bin>