MBOX-Line: From tss at iki.fi  Sun Jan  6 20:02:03 2008
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:41 2018
Subject: [Imap-protocol] Checking for new messages
In-Reply-To: <1199677810.8368.16.camel@infidel>
References: <1199677810.8368.16.camel@infidel>
Message-ID: <1199678523.883.716.camel@hurina>

On Sun, 2008-01-06 at 17:50 -1000, Steve Freitas wrote:
> With IMAP4, it seems to be more complicated, but I hope I'm missing
> something here. I can't use message sequence numbers in any way to do
> this, because they're unstable (since deleting a message decrements all
> sequence numbers above that of the deleted message). And I can't use
> UIDs if, like I'm experiencing when dealing with the Courier IMAP
> server, I get a new UIDVALIDITY number every time I connect to the
> server and open a mailbox.

Your Courier setup is then somehow broken. UIDVALIDITY doesn't normally
change, even with Courier. I think it's just as likely for POP3 UIDLs to
change as IMAP UIDVALIDITY.

Another possibility anyway could be using keywords. Mark them with some
"mysoftware-processed" keyword when you're finished with them. Although
not all servers support keywords.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20080107/7595c471/attachment.sig>
