James servers are able to evaluate and execute Sieve scripts.
Sieve is an extensible mail filtering language. It's limited expressiveness (no loops or variables, no tests with side effects) allows user created scripts to be run safely on email servers. Sieve is targeted at the final delivery phase (where an incoming email is transferred to a user's mailbox).
To be correctly executed, please note that the Sieve mailet is required to be positionned prior the LocalDelivery mailet.
A user willing to manage his Sieve scripts on the server can do so via several means:
He can ask an admin to upload his script via the CLI
As James supports ManageSieve (RFC-5804) a user can thus use compatible software to manage his Sieve scripts.
WARNING: ManageSieve protocol should be considered experimental.
Consult managesieveserver.xml in GIT to get some examples and hints.
The service is controlled by a configuration block in the managesieveserver.xml. The managesieveserver tag defines the boundaries of the configuration block. It encloses all the relevant configuration for the ManageSieve server. The behavior of the ManageSieve service is controlled by the attributes and children of this tag.
This tag has an optional boolean attribute - enabled - that defines whether the service is active or not. The value defaults to "false" if not present.
The standard children of the managesieveserver tag are: