MBOX-Line: From jkt at flaska.net  Sat Dec 29 00:00:54 2012
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: Missing UIDNEXT during mailbox synchronization
In-Reply-To: <20121228112725.Horde.cM7EjLQoqQDix9dQMs5KcA1@bigworm.curecanti.org>
References: <db123879-1082-4911-b7ce-3a861d62217a@flaska.net>
	<20121228112725.Horde.cM7EjLQoqQDix9dQMs5KcA1@bigworm.curecanti.org>
Message-ID: <f45e9e58-e469-4e86-b95e-f2c0d38c5766@flaska.net>

On Friday, 28 December 2012 19:27:25 CEST, Michael M Slusarz wrote:
> Courier definitely does this, and it is not against spec.

Looks like that part of 3501 was not updated from 2060, then -- the UIDNEXT is listed as REQUIRED in the description of the SELECT command, as Bron pointed out.

The safest thing to assume is probably that one is talking to a 2060-compliant server when UIDNEXT is missing. The text you quote indicates that UIDVALIDITY was not required in 2060, either; my code will work in such case, but the cache will be invalidated on next reconnect.

With kind regards,
Jan

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

