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 ---
_______________________________________________
sieve mailing list
sieve(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/sieve