Spam Quarantine threshold considerations
Issues to consider before you modify Spam Quarantine thresholds describes the issues that you should consider before you modify Spam Quarantine thresholds.
Issues to consider | Details |
|---|---|
Thresholds are enforced when the Expunger runs. The Expunger deletes older messages to enforce thresholds. | Thresholds may be exceeded temporarily until the next Expunger run. |
Per-user thresholds are the most processing-intensive to enforce. | Per-user thresholds are not recommended for larger deployments, such as those with over 5000 users. When the Expunger runs, per-user thresholds are checked and enforced before the other thresholds. |
The Maximum size of Quarantine and Maximum number of messages thresholds provide the most precise control over disk usage and message count. | Spam Quarantine searches run faster with fewer messages. |
Shortening the Spam Quarantine message retention period can also limit the size of Spam Quarantine. | A more efficient method to manage Spam Quarantine size is to conserve disk space rather than using Spam Quarantine thresholds. |
No alert or notification occurs if the specific Spam Quarantine thresholds are exceeded. | You can configure an alert for Usage of the maximum configured disk space for Spam Quarantine exceeds . |