Re: [apps-discuss] Review of draft-ietf-appsawg-sieve-duplicate

[Ned Freed <[e-mail]>]

> Stephan

> Thanks for that - you have addressed the points I had in mind.

> A separate question, hence the top post.  If this function is used by
> sieve script X which is included in both sieve scripts A and B, is there
> an internal duplicate tracking list for X; or two, one for A.X and
> one for B.X; or ... ?

In the case of the include extension, there's only one. This is covered
explicitly in the draft:

   The "duplicate" test MUST only check for duplicates amongst message
   ID values encountered in previous executions of the Sieve script; it
   MUST NOT consider ID values encountered earlier in the current Sieve
   script execution as potential duplicates.  This means that all
   "duplicate" tests in a Sieve script execution, including those
   located in scripts included using the "include" [INCLUDE] extension,
   MUST always yield the same result if the arguments are identical.

Note the last sentence.

If you want your included scripts to operate in a different namespace, that's
what :handle is for.

More generally, this all gets very complex in a multiple sieve-per-message
environment. There's a correct answer, one that has been arrived at
independently by multiple implementors, but since such environments are outside
our current standards, I see no reason to worry about them here.

				Ned