Platform Deployment Guide › Integration with Voltage SecureMail › Set Up SecureMail Integration › Define Rule for Voltage SecureMail Gateway

Define Rule for Voltage SecureMail Gateway

If you use a Voltage SecureMail clientless solution (also known as 'SecureMail FlagSecure'), emails are not encrypted when they are sent but contain an x-header to indicate that encryption is required. Therefore you must define a rule on your SecureMail Gateway to encrypt the email.

Note: If you use a Voltage SecureMail end-to-end solution, emails are already encrypted before they leave the workstation or mobile device.

You must use 'x-voltage: encrypt'

To support CA DataMinder integration with SecureMail, you must define a SecureMail Gateway rule to detect the following x-header:

x-voltage: encrypt

This is the default x-header for SecureMail FlagSecure. Do not specify a different x-header!

Note: For details about configuring gateway rules, see the Voltage SecureMail Management Console Administrator Guide.

Why is this necessary?

CA DataMinder policy engines can only recognize 'x-voltage: encrypt' x-headers in SecureMail emails. They cannot recognize different x-headers.

CA DataMinder uses this x-header to mark SecureMail emails as 'Encrypted' when a user reviews these emails in the iConsole.

Note: If you use a different x-header, CA DataMinder still applies policy to the email. And the email is still encrypted by the SecureMail Gateway. However, CA DataMinder does not mark the email as 'Encrypted' in the iConsole.