Message expiration

Message expiration automatically removes messages from the Message Store based on configured criteria. For example, automatic expiration can selectively remove old messages, overly large messages, seen or deleted messages, messages with specific Subject: lines, messages of a certain type, etc..

Note: Oracle Communications Messaging Server removes messages without giving a warning, so it is important to inform users about message expiration policies! Unexpected message removal can be a source of consternation for users and administrators.

Message expiration is performed by the  utility. This utility may be run manually, and/or be configured to run automatically on a schedule as configured for the Scheduler&#x27;s expire task.

The rules for what the  utility (the  expire task) does -- which messages it checks, for which expiration criteria -- may be controlled in two distinct ways. An older, and nowadays less preferred, method is to define global rules (applying to all messages and users) via Message Store expirerule options (corresponding to legacy configuration configutil parameters). The preferred method is to define the expiration rule via   files.

For use of  post-message-delivery to scan messages for spam or viruses, see    invoking spamfilter pacakges.

See also:
 * expire task options
 * Message Store expirerule options
 * imexpire invoking spamfilter packages
 * store.expirerule files
 * imexpire folder patterns
 * imexpire and localized mailbox names
 * The Message Store