Next: , Previous: Invoking Sieve, Up: sieve interpreter


3.9.1.2 Sieve Configuration

The behavior of sieve is affected by the following configuration statements:

Statement Reference
debug See Debug Statement.
tls See TLS Statement.
mailbox See Mailbox Statement.
locking See Locking Statement.
logging See Logging Statement.
mailer See Mailer Statement.

The following statements configure sieve-specific features:

— Sieve Conf: sieve { ... }

This block statement configures search paths sieve uses to locate its loadable modules. See Require Statement, for a detailed information of this feature.

This statement may contain the following sub-statements: clear-library-path, clear-include-path, library-path, include-path, which are described below.

— Sieve Conf: clear-library-path bool

Used within the sieve block statement.

If bool is ‘true’, clear library search path.

— Sieve Conf: clear-include-path bool

Used within the sieve block statement.

If bool is ‘true’, clear include search path.

— Sieve Conf: library-path path

Used within the sieve block statement.

Add directories to sieve library search path. Argument is a string containing a colon-separated list of directories.

— Sieve Conf: include-path path

Used within the sieve block statement.

Add directories to the include search path. Argument is a string containing a colon-separated list of directories.

— Sieve Conf: keep-going bool

If bool is ‘true’, do not abort if execution of a Sieve script fails on a particular message.

— Sieve Conf: mbox-url url

Sets URL of the mailbox to be processed.

— Sieve Conf: ticket file

Sets the name of the ticket file for user authentication.

— Sieve Conf: debug flags

Sets Sieve debug flags. See Logging and Debugging, for a detailed description.

— Sieve Conf: verbose bool

If bool is ‘true’, log all executed actions.

— Sieve Conf: line-info bool

If bool is ‘true’, print source locations along with action logs. This statement takes effect only if verbose true is also set.

— Sieve Conf: email addr

Set user e-mail address. This is useful for reject and redirect actions. By default, the user email address is deduced from the user name and the full name of the machine where sieve is executed.