MBOX-Line: From barryleiba at computer.org  Mon Jan  7 18:26:42 2013
To: imap-protocol@u.washington.edu
From: Barry Leiba <barryleiba@computer.org>
Date: Fri Jun  8 12:34:50 2018
Subject: [Imap-protocol] Re: Missing UIDNEXT during mailbox synchronization
In-Reply-To: <20130106223402.Horde.ZSCj1mxY7M87XW6Ro4AX9A1@bigworm.curecanti.org>
References: <db123879-1082-4911-b7ce-3a861d62217a@flaska.net>
	<20121228112725.Horde.cM7EjLQoqQDix9dQMs5KcA1@bigworm.curecanti.org>
	<f45e9e58-e469-4e86-b95e-f2c0d38c5766@flaska.net>
	<20130106223402.Horde.ZSCj1mxY7M87XW6Ro4AX9A1@bigworm.curecanti.org>
Message-ID: <CAC4RtVCB=pNDC2Gjtf7z1=h50ZtyQKMUEOLDegBZPMwrshdtUg@mail.gmail.com>

>> 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.
>
> I reported this as an errata to RFC 3501, with the recommendation that the
> "assumption" sentence from the UIDNEXT text be removed in order to eliminate
> the ambiguity between this text (which implies that the UIDNEXT response may
> be optional) and the REQUIRED requirement located in Sections 6.3.1 & 6.3.2.

Um...

But this erratum is wrong.  You jumped to premature conclusions.

Look at the paragraph above the responses in Section 6.3.1.  It says this:

      The SELECT command selects a mailbox so that messages in the
      mailbox can be accessed.  Before returning an OK to the client,
      the server MUST send the following untagged data to the client.
      Note that earlier versions of this protocol only required the
      FLAGS, EXISTS, and RECENT untagged data; consequently, client
      implementations SHOULD implement default behavior for missing data
      as discussed with the individual item.

The text that you're suggesting removing is there very purposefully,
and should NOT be removed.  I intend to mark the erratum as
"Rejected", but I'll give us some time to discuss it further first.

Barry, Applications AD

