MBOX-Line: From jkt at flaska.net  Thu Jan 24 10:11:01 2013
To: imap-protocol@u.washington.edu
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
Date: Fri Jun  8 12:34:50 2018
Subject: [Imap-protocol] Re: Courier =?iso-8859-1?Q?bug(=3F)?=
In-Reply-To: <51015F8D.8020300@isode.com>
References: <20130121144822.Horde.kbr5Y8IKwMlD1fH1Qun9hQ1@bigworm.curecanti.org>
	<CAKHUCzwJ8xq7O8vGDHe0D9Jviac06o-QtePMhKYV7HzwzRPMPA@mail.gmail.com>
	<1358846428.12608.2.camel@hurina>
	<CAC4RtVAobTOjLdLH++_qp=HCtdZJne5Q7TUF_P=9J6a+gg2fmQ@mail.gmail.com>
	<51015F8D.8020300@isode.com>
Message-ID: <9ade1aaa-6d67-443b-8fa3-43f00486d4cb@flaska.net>

On Thursday, 24 January 2013 17:21:33 CEST, Alexey Melnikov wrote:
>> If, as a client, you want to head off this situation, the way to do it
>> is to ask for FLAGS in addition to BODY.
>
> An alternative is to keep message numbers for the duration of a 
> UID FETCH and correlate multiple FETCH responses that way.

As far as I understand all of the RFCs, there is unfortunately nothing but the 5162's errata which would guarantee that unsolicited FETCH responses will have UIDs in them. Based on that observation, I claim that a client which wants to keep track of updates to messages' flags will have to keep a full mapping of the seq->UID for the relevant message ranges at all times. Remember, servers are free to send the data at any time, not just when fetching body parts.

With kind regards,
Jan

-- 
Trojit?, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/

