MBOX-Line: From tjs at psaux.com  Mon Jun  6 14:15:09 2011
To: imap-protocol@u.washington.edu
From: Tim Showalter <tjs@psaux.com>
Date: Fri Jun  8 12:34:46 2018
Subject: [Imap-protocol] Where to start?
In-Reply-To: <4DEBDFF5.9000301@BusCom.net>
References: <4DEBB242.2090200@BusCom.net>	<4DEBB58D.3090101@logicprobe.org>	<4DEBBAB3.2030301@BusCom.net>	<4DEBBEC1.3080600@BusCom.net>	<201106051924.p55JOwpG003543@mxout12.cac.washington.edu>
	<4DEBDFF5.9000301@BusCom.net>
Message-ID: <4DED435D.9070900@psaux.com>

On 6/5/11 12:58 PM, Lynn W. Taylor wrote:
> The mailstore is in RFC-2822 format. There is a UID, and it's cast in
> jello -- it can be changed so that the POP3 server uses an IMAP
> compatible UIDL. I think I can keep the UIDs unique and ascending as
> required in the RFC.

Ancient versions of Cyrus used only the UID as a UIDL value, and it can 
cause problems when a user is moved from one POP server to a new host. 
POP has no equivalent to UIDVALIDITY, and the only way to blow the cache 
is to change all the UIDL values.

If you use the UIDVALIDITY+UID as a UIDL scheme, that works pretty well.

Tim

