Deployment Guide › Quarantine Manager › Quarantine Manager Architecture

Quarantine Manager Architecture

The role of the Quarantine Manager is to ensure that e‑mails released from quarantine are sent on to their original recipients. To achieve this, the Quarantine Manager regularly queries the CMS for released or timed-out e‑mails and forwards these to their intended recipients. The architecture is summarized below:

Quarantine procedure: Example based on Exchange server integration

This example shows how the Quarantine feature operates in conjunction with Exchange server integration. However, it can also operate in conjunction with Outlook and Notes client agents.

An email is sent (1) and monitored by CA DLP (2) as it transits through the Exchange server (3). A control trigger quarantines the email. The CMS (4) maintains a queue of quarantined emails (5). A reviewer (6) checks quarantined e‑mails in the iConsole or Data Management console. The reviewer can either release or reject a quarantined email.

The Quarantine Manager (7) regularly checks the quarantine queue on the CMS, checking for e‑mails that have been released or which have timed out (8). It then forwards these e‑mails, either via the original Exchange server (9a) or, if so configured, though an alternative Exchange server (9b) to the intended recipient (10).

Note: For simplicity, this diagram omits the policy engine hub and policy engines.