MBOX-Line: From janssen at parc.com  Fri Mar 16 19:49:51 2007
To: imap-protocol@u.washington.edu
From: Bill Janssen <janssen@parc.com>
Date: Fri Jun  8 12:34:38 2018
Subject: [Imap-protocol] what does UIDNOTSTICKY really mean?
In-Reply-To: <alpine.WNT.0.83.0703161613040.1748@Tomobiki-Cho.CAC.Washington.EDU>
References: <07Mar16.123633pst."57996"@synergy1.parc.xerox.com>
	<alpine.WNT.0.83.0703161613040.1748@Tomobiki-Cho.CAC.Washington.EDU>
Message-ID: <07Mar16.184958pst."57996"@synergy1.parc.xerox.com>

I'm a bit confused on the UIDPLUS tag UIDNOTSTICKY.  RFC 4315 says,

      The selected mailbox is supported by a mail store that does not
      support persistent UIDs; that is, UIDVALIDITY will be different
      each time the mailbox is selected.  Consequently, APPEND or COPY
      to this mailbox will not return an APPENDUID or COPYUID response
      code.

My system will persist UIDs until the the server is re-booted for some
reason; that is, UIDVALIDITY may be different each time a mailbox is
selected, though it's not likely to be.  Depends on the frequency of
selection.  So UIDs tend to be persistent, but are not guaranteed to be.

Should I send UIDNOTSTICKY, or not?

Bill

