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

Stephan Bosch <stephan@rename-it.nl> Sun, 07 April 2013 16:48 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 6E77F21F85DA for <sieve@ietfa.amsl.com>; Sun, 7 Apr 2013 09:48:50 -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 LAZNBkXLhQua for <sieve@ietfa.amsl.com>; Sun, 7 Apr 2013 09:48:50 -0700 (PDT)
Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id AC73621F859D for <sieve@ietf.org>; Sun, 7 Apr 2013 09:48:48 -0700 (PDT)
Received: from klara.student.utwente.nl ([130.89.162.218]:64632 helo=[10.168.3.2]) 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 1UOslg-00007h-QF for sieve@ietf.org; Sun, 07 Apr 2013 18:48:46 +0200
Message-ID: <5161A34D.3040805@rename-it.nl>
Date: Sun, 07 Apr 2013 18:48:13 +0200
From: Stephan Bosch <stephan@rename-it.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Sieve mailing list <sieve@ietf.org>
References: <20130407160743.19463.39851.idtracker@ietfa.amsl.com>
In-Reply-To: <20130407160743.19463.39851.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130407160743.19463.39851.idtracker@ietfa.amsl.com>
Content-Type: multipart/mixed; boundary="------------040200000000010203080000"
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
Subject: [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: Sun, 07 Apr 2013 16:48:50 -0000

Hi,

I made a new version of the "duplicate" draft. It should address the 
comments by Ned, Kristin and Alexey. I added the example I gave to Alexey.

This resulted in quite a bit of restructuring in the description of the 
new test command, so it is best to review at least that section entirely.

There is one thing I thought of and haven't addressed so far. My current 
implementation makes a new entry in the duplicate tracking list 
irrespective of whether one exists already, overwriting the old one and 
thereby resetting the expiry time to whatever is configured using 
":seconds". This will make example 3 in the draft yield unexpected 
results; if duplicates arrive within the expiry time, the total expiry 
time is in effect extended. The semantic difference here is that the 
expiry time is either measured relative to the initial message or 
relative to the last duplicate. This means that the 30 minutes in the 
example can stretch indefinitely if duplicates keep arriving before the 
expiry deadline. So, for the scenario of example 3, such behavior is 
quite obviously wrong. However, would there be an application for having 
the expiry time be relative to the last message received with the 
specified ID rather than the initial one? How would we accommodate for that?

Regards,

Stephan.
--- Begin Message ---
A new version of I-D, draft-bosch-sieve-duplicate-02.txt
has been successfully submitted by Stephan Bosch and posted to the
IETF repository.

Filename:	 draft-bosch-sieve-duplicate
Revision:	 02
Title:		 Sieve Email Filtering: Detecting Duplicate Deliveries
Creation date:	 2013-04-07
Group:		 Individual Submission
Number of pages: 10
URL:             http://www.ietf.org/internet-drafts/draft-bosch-sieve-duplicate-02.txt
Status:          http://datatracker.ietf.org/doc/draft-bosch-sieve-duplicate
Htmlized:        http://tools.ietf.org/html/draft-bosch-sieve-duplicate-02
Diff:            http://www.ietf.org/rfcdiff?url2=draft-bosch-sieve-duplicate-02

Abstract:
   This document defines a new test command "duplicate" for the "Sieve"
   email filtering language.  This test adds the ability to detect
   duplicate message deliveries.  The main application for this new test
   is handling duplicate deliveries commonly caused by mailing list
   subscriptions or redirected mail addresses.  The detection is
   normally performed by matching the message ID to an internal list of
   message IDs from previously delivered messages.  For more complex
   applications, the "duplicate" test can also use the content of a
   specific header or other parts of the message.

                                                                                  


The IETF Secretariat

--- End Message ---