Sieve Extension: Externally Stored Lists

The Sieve scripting language can be used to implement whitelisting,blacklisting, personal distribution lists, and other sorts of listmatching. Currently, this requires that all members of such lists behardcoded in the script itself. Whenever a member of a list is addedor deleted, the script needs to be updated and possibly uploaded to amail server. This document defines a Sieve extension for accessingexternally stored lists -- lists whose members are stored externallyto the script, such as using LDAP (RFC 4510), ACAP (RFC 2244), orrelational databases. ToDo o Should we add a mandatory-to-implementtag? Ned suggests (and I agree) that it might be good to add aregistry of well-defined strings that can be used instead of URIs, anddefine the initial string "ab" to represent the user's personaladdress book. o Do we want to have the :list test set variables? SeeNed's comments in the text.