

Policy Guide › How Policy Works › Policy Processing › Applying Triggers to Emails
Applying Triggers to Emails
When CA Data Protection applies a trigger to an email, it does the following:
- It analyzes the event metadata, including sender and recipient details. For example, is the email being sent to an authorized recipient?
- It performs any Message Attribute or XML Attribute data lookups. These lookups can quickly tell CA Data Protection whether to fire a trigger. For example, a trigger may be configured to always fire if an email has more than 10 recipients.
- It analyzes the text content of the email, starting with the subject and then the body text (if required).
- If CA Data Protection is unable to determine whether to fire the trigger, it performs any 'remote' data lookups, that is, User Attribute lookups and Address Book lookups. These are 'remote' lookups because CA Data Protection must retrieve the information respectively from your CMS or your preferred LDAP server (typically your Active Directory host).
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|