Re: [sieve] Fwd: New Version Notification for draft-bosch-sieve-duplicate-02.txt

Stephan Bosch <stephan@rename-it.nl> Fri, 03 May 2013 08:40 UTC

Return-Path: <stephan@rename-it.nl>
X-Original-To: sieve@ietfa.amsl.com
Delivered-To: sieve@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8190F21F93FC for <sieve@ietfa.amsl.com>; Fri, 3 May 2013 01:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 217Q45ICEVEa for <sieve@ietfa.amsl.com>; Fri, 3 May 2013 01:40:17 -0700 (PDT)
Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id 9F08721F93FB for <sieve@ietf.org>; Fri, 3 May 2013 01:40:16 -0700 (PDT)
Received: from ewi1299.ewi.utwente.nl ([130.89.145.113]:49428) by drpepper.rename-it.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <stephan@rename-it.nl>) id 1UYBXI-0004Dy-4C; Fri, 03 May 2013 10:40:14 +0200
Message-ID: <518377E2.3000307@rename-it.nl>
Date: Fri, 03 May 2013 10:40:02 +0200
From: Stephan Bosch <stephan@rename-it.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
References: <20130407160743.19463.39851.idtracker@ietfa.amsl.com> <5161A34D.3040805@rename-it.nl> <5165D08D.4040404@rename-it.nl> <01OSWJ6MW7KE000054@mauve.mrochek.com>
In-Reply-To: <01OSWJ6MW7KE000054@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-RenameIT-MailScanner-SpamScore: -2.3 (--)
X-RenameIT-MailScanner-SpamCheck: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=ham version=3.3.1
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Fwd: New Version Notification for draft-bosch-sieve-duplicate-02.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 08:40:23 -0000

Op 4/25/2013 11:44 PM, Ned Freed wrote:
>> One other thing: we recently defined this great new Sieve use-case
>> called IMAPSieve. Is there any application imaginable for the duplicate
>> test in this context, i.e. do we want to allow it there? Either way, I
>> think we should state its applicability explicitly.
>
> I think there are legitimate use-cases, but it's also incredibly easy 
> to misuse
> in this context.
>
> The basic problem is that moving messages around in IMAP doesn't carry 
> with it
> any sort of inherent special semantic and people move messages around 
> for all
> sorts of reasons (or for no real reason at all). This is quite unlike 
> message
> delivery.
>
> So, for example, you could define a Sieve in IMAP to prevent, say, the
> inclusion of a second copy of the same message in a given folder. But bad
> things are going to happen if, say, you forget the filter is there and 
> move
> some of the messages out and back in a couple of times.
>
> We'd have to extend the semantics of the extension substantiantially 
> to take
> care of this, and even if we were to do that actually using it would be
> very tricky indeed.
>
> Since I see the main benefit of this extension as how simple it makes
> duplicate checks in Sieve, this usage makes me very nervous, so nervous
> that I could certainly accept a "NOT RECOMMENDED" label for this case.

Yes, I agree with that.

BTW, any further comments on the document as it is now? More thoughts on 
the ':last' issue?

Regards,

Stephan.