Policy Engine

Policies, which are built using the Sieve language, provide the filtering definition for PureMessage. PureMessage can be configured to use multiple policy scripts but uses only one by default. The default policy script is stored at /opt/pmx6/etc/policy.siv, beneath the PureMessage installation directory.

Policies consist of rules; rules consist of tests and actions. As the policy processes messages, rules are executed on the message in the order of their configuration.

Configure policies on the Policy tab of the PureMessage Manager, or by using the pmx-policy command-line program. A default policy is installed and enabled during PureMessage installation. The default policy varies according to your PureMessage license; for example, if you do not have a license for the PureMessage Virus component, virus-checking rules are not configured.

Tests define the characteristics of the message that must be matched in order for the action to be executed. Multiple conditions can be configured for a single rule.

Actions are the parts of rules that determine what happens to a message that meets or does not meet a test. Multiple actions can be specified.

You can modify the PureMessage policy using the options available on the Policy tab of the Manager. Clicking a rule description launches a new Rules page with configurable fields. Alternatively, clicking see the source displays the Sieve code that underlies the policy interface. The code can be edited directly through the Manager. See the Manager Reference and Administrator’s Reference for instructions on editing the policy.

PureMessage has a Policy Repository for storing Sieve snippets and scripts that can be incorporated into a PureMessage policy script. By default, the repository contains a number of general-purpose snippets that can be copied and pasted from the Policy Repository to the PureMessage policy and vice versa.