Re: [lemonade] Regarding CONDSTORE IMAP extension

Likely you’re seeing this behavior only with Dovecot server, which enables modseq tracking lazily. And in Dovecot you can always work around that with the ENABLE CONDSTORE command (or any other CONDSTORE-enabling command).

On 3.12.2013, at 0.48, Samsung SVL <samsungsvl@yahoo.com> wrote:

> Hi Timo,
> 
> Thanks for your response.
> 
> But if IMAP server does not support "ENABLE" command, what should be the client behavior ?
> 
> Regards,
> Jay
> 
> From: Timo Sirainen <tss@iki.fi>
> To: Samsung SVL <samsungsvl@yahoo.com> 
> Cc: "lemonade@ietf.org" <lemonade@ietf.org> 
> Sent: Monday, 2 December 2013, 17:01
> Subject: Re: [lemonade] Regarding CONDSTORE IMAP extension
> 
> On 2.12.2013, at 23.51, Samsung SVL <samsungsvl@yahoo.com> wrote:
> 
> 
> > As per RFC 4551,  client issues SELECT command  for a mailbox in the below format and receives the response with HIGHESTMODSEQ value as  "1"
> > 
> > C: A142 SELECT INBOX
> > 
> > During the subsequent SELECT command, client receives "HIGHESTMODSEQ" value always set to "1". Its not getting incremented with respect to the changes in the mailbox. 
> > 
> > Some IMAP server changes the HIGHESTMODSEQ value only when client issues SELECT command in the below format.
> > 
> > C:A142 SELECT "INBOX" (QRESYNC ("UIDVALIDITY" "HIGHESTMODSEQ"))
> > 
> > Kindly clarify which format is right one, because most of the IMAP server behaves differently.
> 
> 
> If server advertises also ENABLE capability, you can send ENABLE CONDSTORE as your first command. Then all servers will work correctly.
> 
> 
> 
> _______________________________________________
> lemonade mailing list
> lemonade@ietf.org
> https://www.ietf.org/mailman/listinfo/lemonade
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/lemonade