Previous Topic: Tracking ID 221-75: Incorrect Timestamp For Events Captured Immediately Before DST EndsNext Topic: Tracking ID 417-17: Do Not Include PST Files In Scanning Jobs


Tracking ID 397-45: Emails Released From Quarantine Are Not Encrypted

If an email activates a trigger with a quarantine action plus a trigger with any action that generates x-headers on the email, the x-headers are not applied when the email is released from quarantine.

For example, if a trigger has an Encrypt action, CA DataMinder normally inserts an 'encryption request' x-header into an unprotected outgoing email. This x-header is then be detected by a third party encryption provider before the email leaves the corporate network. But for emails released from quarantine, the x-header is not inserted and so consequently the email is not encrypted.

Therefore, we recommend that you do not use Quarantine and Encrypt actions together. That is, ensure that policy is configured such that these two actions cannot be invoked by the same email.

Note: This issue does not affect quarantined emails where the 'encryption request' x-header was inserted by a third party encryption provider (for example, the Voltage SecureMail clientless solution, also known as 'SecureMail FlagSecure'). Such emails are encrypted when they are released from quarantine.