Re: [apps-discuss] Kathleen Moriarty's Discuss on draft-ietf-appsawg-sieve-duplicate-07: (with DISCUSS and COMMENT)

[Stephan Bosch <[e-mail]>]

Hi Kathleen, Barry,

On 6/24/2014 6:55 PM, Kathleen Moriarty wrote:
> On Tue, Jun 24, 2014 at 11:54 AM, Barry Leiba <[e-mail]
> <mailto:[e-mail]>> wrote:
>
>
>     OLD
>        In its basic form, the "duplicate" test keeps track of which
>     messages
>        were seen before by this test during an earlier Sieve execution.
>        Messages are by default identified by their message ID as contained
>        in the Message-ID header.  The "duplicate" test evaluates to "true"
>        when the message was seen before and it evaluates to "false"
>     when it
>        was not.
>     NEW
>        The "duplicate" test identifies the message by a "unique ID", and,
>        using that unique ID,  keeps track of which messages were seen
>        by a "duplicate" test during an earlier Sieve execution.  In
>     its basic
>        form, the test gets the unique ID from the content of the message's
>        Message-ID header.  The "duplicate" test evaluates to "true" when
>        the message was seen before and it evaluates to "false" when it
>        was not.
>     END
>
>
> WFM and thank you.  My words were meant to help the discussion and get
> edited as needed.  You are more familiar with the terminology used by
> the group.
>   
>
>     OLD
>        As a side-effect, the "duplicate" test adds the message ID to an
>        internal duplicate tracking list once the Sieve execution finishes
>        successfully.  This way, the same test will evaluate to "true"
>     during
>        the next Sieve execution in which that message ID is encountered.
>        Note that this side-effect is performed only when the "duplicate"
>        test is actually evaluated.  If the "duplicate" test is nested in a
>        control structure or it is not the first item of an "allof" or
>        "anyof" test list, its evaluation depends on the result of
>     preceding
>        tests, which may produce unexpected results.
>     NEW
>        As a side-effect, the "duplicate" test adds the unique ID to an
>        internal duplicate tracking list once the Sieve execution finishes
>        successfully.  The first time a particular unique ID is seen, the
>        message is not a duplicate, and the unique ID is added to the
>        tracking list.  If a future Sieve execution sees a message whose
>        unique ID appears in the tracking list, that test will evaluate to
>        "true", and that message will be considered a duplicate.
>
>        Note that this side-effect is performed only when the "duplicate"
>        test is actually evaluated.  If the "duplicate" test is nested in a
>        control structure or it is not the first item of an "allof" or
>        "anyof" test list, its evaluation depends on the result of
>     preceding
>        tests, which may produce unexpected results.
>     END
>
>
> WFM, thank you!

Applied in -08.

Regards,

Stephan.