Ned Freed wrote:
There are basically two ways to address one. One is to say "some
of :list and variaus MATCH-TYPES" are going to fail in some cases".
Alternately, we can simply say "the MATCH-TYPE is implied by the list
and :list is therefore best thought of as a MATCH-TYPE".
I strongly prefer the latter. The former has least astonishment violation
written all over it. It also fails to allow for lists whose underlying
criteria do not align with existing Sieve match types, and there are a
those; prefix match, suffix match, IP address pattern matches, etc.
anyone suggests defining new match types for these, allow me to point
in some cases the ynderlying match types allowed from some sources are
ended and extensible.
Would we need to have :list-is, :list-matches, :list-contains, or can we
get away with just :list, which would check for the exact match?