Be aware that any x-headers generated from CA DataMinder user policies must adhere to the following requirements:
x-header names must start with X— or x—. CA DataMinder specifically checks for 'x hyphen' smart tags when generating x-headers.
This is crucial. When agreeing the x-header name with a third party, you must choose a 'strong' name. That is, choose a name that will not conflict with other x-headers. Specifically, avoid names that are generic or too short.
Notes and Domino users must also take care to choose x-header names that (when they have been stripped of the x— prefix) do not conflict with object names used internally by Domino.
An example of a strong x-header name is:
X-Unipraxis-MessageEncryptionRequest
X-header names cannot be longer than 125 characters. Therefore, your smart tag name is similarly restricted. That is, the name you supply when editing the Smart Tags setting cannot be longer than 125 characters.
X-header values must not exceed 2,000 characters. X-header values are appended to the x-header name.
Although an x-header value is unlikely to be constrained by this limit, it may become more relevant in future CA DataMinder releases. For example, if a future release permits users to generate x-header values from tokens or variables (such as a ‘distribution list’ variable), this could potentially result in very long text strings.
Note: These x-header name and value limits are imposed by the technologies underlying the email systems (such as Outlook or Exchange). They are not inherent restrictions in the specification of Internet Mails.
CA DataMinder Outlook endpoint agents cannot add x-headers to emails that have been encrypted or digitally signed.
Note: This limitation does not affect the Exchange server agent, though any policy triggers configured to detect email content may be unable to process encrypted emails anyway.
|
Copyright © 2014 CA.
All rights reserved.
|
|