[lemonade] Re: expunged draft

Alexey Melnikov <Alexey.Melnikov@isode.com> Tue, 01 February 2005 11:35 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17853 for <lemonade-web-archive@ietf.org>; Tue, 1 Feb 2005 06:35:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvwc6-0006sB-0M for lemonade-web-archive@ietf.org; Tue, 01 Feb 2005 06:54:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvwCm-00063o-8G; Tue, 01 Feb 2005 06:28:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CvwCP-0005pD-Vr for lemonade@megatron.ietf.org; Tue, 01 Feb 2005 06:28:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17209 for <lemonade@ietf.org>; Tue, 1 Feb 2005 06:28:00 -0500 (EST)
Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvwUY-0006ge-Rv for lemonade@ietf.org; Tue, 01 Feb 2005 06:46:47 -0500
Received: from [192.168.0.7] ([62.3.217.253]) by rufus.isode.com via TCP (internal) with ESMTPA; Tue, 1 Feb 2005 11:27:13 +0000
Message-ID: <41FF678A.1080701@isode.com>
Date: Tue, 01 Feb 2005 11:27:06 +0000
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
To: Timo Sirainen <tss@iki.fi>
References: <f39f4c363e2d2ec7ee5f10db816eaeed@osafoundation.org> <41FE7CA0.2010003@isode.com> <1107204693.12365.238.camel@hurina>
In-Reply-To: <1107204693.12365.238.camel@hurina>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-7"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Encoded: Changed encoding from 8bit for 7bit transmission
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
Cc: IMAP Extensions WG <ietf-imapext@imc.org>, lemonade@ietf.org
Subject: [lemonade] Re: expunged draft
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable

Timo Sirainen wrote:

>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)?
>  
>
Yes, that was the idea.

>Servers supporting UNSELECT should most likely also send HIGHESTMODSEQ
>just as with CLOSE, but this isn't mentioned.
>
UNSELECT doesn't cause any message to be expunged.

> And what about with
>SELECT?
>
Same as above.

> Maybe just point out more generally that "when using a command
>which closes the mailbox, send HIGHESTMODSEQ". Perhaps LOGOUT should do
>that too?
>  
>
Remember, that the CONDSTORE extension requires the server to send 
mod-sequences for flag changes (using MODSEQ FETCH data items) and 
whenever a message is appended. The EXPUNGED document extends this to 
cover expunges. So there is no point to send HIGHESTMODSEQ when nothing 
has changed, this should cover LOGOUT, SELECT and UNSELECT.
Of course, if messages got expunged in another session, the server still 
needs to send HIGHESTMODSEQ.

>   <<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.
>  
>
As EXPUNGED returns a list of UIDs, I was wondering if it should obey 
the same rule as EXPUNGE, i.e. whether it should be allowed during 
regular FETCH/STORE.

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


_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade