In this example, a Webmail is sent to an external Hotmail recipient. The NBA detects the Webmail and passes it to a policy engine, which applies the External Sender’s policy. When the Webmail is quarantined, a reviewer can either release it or reject it. If released, the email is forwarded by the Quarantine Manager, via an SMTP server and the NBA, to its intended recipient.
Note: For simplicity, this diagram omits ‘quarantine notification’ emails sent by the Socket API.
Example: NBA and quarantined emails
A user sends an email (1) to a Hotmail recipient. The NBA (2) detects the email and passes it via the Socket API (3) to a policy engine (4). The policy engine applies a ‘Quarantine Quietly control action and calls back to the NBA to block the associated data packets. It then replicates the email to the CMS.
The CMS (5) maintains a queue of quarantined emails (6). A reviewer checks this queue in the iConsole (7) and either releases or rejects the email.
The Quarantine Manager (8) regularly checks this queue and forwards released emails (9) to the intended recipients. Emails rejected by the reviewer are not forwarded (10).
Emails released from quarantine are sent via an SMTP server (11) through the NBA (12) on their way to the Hotmail server (13). The NBA detects that the email has already been processed by CA DataMinder and does not quarantine it again. The recipient sees the email when they next view their Hotmail inbox.
|
Copyright © 2014 CA.
All rights reserved.
|
|