expunged draft

[Timo Sirainen <[e-mail]>]

On Mon, 2005-01-31 at 18:44 +0000, Alexey Melnikov wrote:
> I've just submitted a new draft that describes how CONDSTORE 
> modification sequences can be used to track expunged messages. Before it 
> is announced, people can find it at:
> http://ietf.webdav.org/imapext/draft-melnikov-imap-expunged-00.txt
> 
> I will welcome all suggestions, especially on issues marked with <<>> in 
> the document.

It shows that HIGHESTMODSEQ update is sent after EXPUNGE command. What
about when other session did the EXPUNGE and we're seeing untagged
EXPUNGEs? Maybe always send it after untagged expunges (and don't
mention EXPUNGE command at all)?

Servers supporting UNSELECT should most likely also send HIGHESTMODSEQ
just as with CLOSE, but this isn't mentioned. And what about with
SELECT? Maybe just point out more generally that "when using a command
which closes the mailbox, send HIGHESTMODSEQ". Perhaps LOGOUT should do
that too?

   <<What if the server can’t remember some expunged UIDs, for example
   the provided mod-sequence is too old? Can the server just return
   all UIDs not in the UID set? This can generate additional traffic,
   but should be Ok otherwise.>>

Yes, I think so.

In 3.4 EXPUNGED Response it seems rather useless trying to rewrite what
RFC3501 says about EXPUNGEs. Just point out that it works exactly as
normal untagged EXPUNGE? It would be really bad if they accidentally got
different rules.

Maybe rename the EXPUNGED to UIDEXPUNGE or similar to make it more clear
that it's sending UIDs and not sequences?