Hi, I have been looking at search and sorting with dovecot and have run into some things. The first one I think may be a minor bug because a set of commands result in the socket connection being closed without warning: UID SEARCH RETURN (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 updated by the RFC describing the NOTIFY extension to IMAP so maybe it has been decided to not add these keywords until a later time? I am using dovecot version 2.0.15 (with patches from Apple). Best Regards Anders
Timo Sirainen
2012-Jan-10 14:16 UTC
[Dovecot] A small bug and a question about CONTEXT=SEARCH
On Tue, 2012-01-10 at 15:05 +0100, Anders wrote:> the socket connection being closed without warning: > > UID SEARCH RETURN (SAVE COUNT) CHARSET UTF-8 (UNDELETED TEXT "foo")You mean it closes with above also? It works fine with me.> UID SEARCH RETURN (COUNT MIN) CHARSET UTF-8 () $This was fixed in v2.0.17.> 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?All of it is supported, as far as I know.> At least when I include the CONTEXT ADDTO or REMOVEFROM keywords I get > an error,These are server notifications. Clients aren't supposed to send them.
On Tue, 2012-01-10 at 15:05 +0100, Anders wrote:> > the socket connection being closed without warning: > > UID SEARCH RETURN (SAVE COUNT) CHARSET UTF-8 (UNDELETED TEXT "foo") > > You mean it closes with above also? It works fine with me.No, that also works fine here :-)> > UID SEARCH RETURN (COUNT MIN) CHARSET UTF-8 () $ > > This was fixed in v2.0.17.Great, thanks!> > 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? > > All of it is supported, as far as I know.> > At least when I include the CONTEXT ADDTO or REMOVEFROM keywords I get > > an error,> These are server notifications. Clients aren't supposed to send them.Sorry, apparently I was a bit too fast there. ADDTO and REMOVEFROM should not be sent by a client, but I think that a client can send CONTEXT as a hint to the server, see http://tools.ietf.org/html/rfc5267#section-4.2 Thanks! Regards Anders
Timo Sirainen
2012-Jan-28 22:00 UTC
[Dovecot] A small bug and a question about CONTEXT=SEARCH
On 11.1.2012, at 17.57, Anders wrote:> Sorry, apparently I was a bit too fast there. ADDTO and REMOVEFROM should not > be sent by a client, but I think that a client can send CONTEXT as a hint to > the server, see > > http://tools.ietf.org/html/rfc5267#section-4.2Yes, that was a bug. Thanks, fixed: http://hg.dovecot.org/dovecot-2.0/rev/fd16e200f0f7