27 lines
1.1 KiB
Plaintext
27 lines
1.1 KiB
Plaintext
MBOX-Line: From arnt at gulbrandsen.priv.no Sat Mar 17 10:20:54 2007
|
|
To: imap-protocol@u.washington.edu
|
|
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
|
|
Date: Fri Jun 8 12:34:38 2018
|
|
Subject: [Imap-protocol] what does UIDNOTSTICKY really mean?
|
|
In-Reply-To: <"07Mar16. 184958pst. 57996"@synergy1.parc.xerox.com>
|
|
References: <"07Mar16. 123633pst. 57996"@synergy1.parc.xerox.com>
|
|
<alpine.WNT.0.83.0703161613040.1748@Tomobiki-Cho.CAC.Washington.EDU>
|
|
<"07Mar16. 184958pst. 57996"@synergy1.parc.xerox.com>
|
|
Message-ID: <L4pj+QY3zD/bvyRda2FR+A.md5@libertango.oryx.com>
|
|
|
|
Bill Janssen writes:
|
|
> 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?
|
|
|
|
IMO you should not. UIDNOTSTICKY is a hint to clients that caching is
|
|
pointless, and in your case caching is useful (although not 100%
|
|
useful).
|
|
|
|
Arnt
|
|
|