The PureMessage quarantine stores messages that have been quarantined according to the configuration of the PureMessage policy. For example, messages quarantined because their spam probability exceeds a certain level.

By default, PureMessage uses the PostgreSQL database to index its quarantine.

Messages are quarantined when the Copy the message to quarantine (pmx_file) or Quarantine the message (pmx_quarantine) action is used in a policy rule.

When a message is quarantined, the message is moved to the var/qdir/new directory beneath the PureMessage installation directory. The quarantine indexer then assigns a quarantine identifier to the message, updates index files and moves it to the var/qdir/cur directory.

When messages are first quarantined, they are temporarily stored in /opt/var/qdir/new. At regular intervals, the quarantine indexer parses this directory, assigns quarantine ID numbers to the messages, updates the index, and moves the messages to/opt/var/qdir/cur.

Quarantined messages are managed using either the Manage Quarantine feature in the PureMessage Manager or the pmx-qman command-line program. Message management actions include deleting, approving for delivery, and saving.

Quarantine Digests

When quarantine digests are enabled, end users receive email notifications of quarantined messages. Notifications contain lists of quarantined messages that were originally destined for particular users. Users can reply to automatically release the desired messages from the quarantine.

Centralized and Consolidated Quarantines

Administrators can configure PureMessage to use either a centralized or consolidated quarantine. In a centralized quarantine, metadata from multiple quarantines is collected in a single PostgreSQL database. In a consolidated quarantine, messages are drawn from multiple quarantines and stored in a single location.