Administration Guide › Mapping E-mail Addresses to Users › Which Features use Address Mapping?

Which Features use Address Mapping?

Which features use e-mail address mapping?

CA Data Protection needs to map e-mail addresses onto individual users for 'multiple participant' events. Specifically, address mapping is used by the following CA Data Protection features to associate imported e-mails and IM conversations, and e-mails captured on an Exchange server, with specific CA Data Protection users:

Policy engines

Before a policy engine can apply policy triggers to an intercepted e-mail, it needs to map the sender's e-mail address to a CA Data Protection user. The mapping identifies the e-mail owner and determines which policy to apply.

If the policy engine is unable to map an e-mail address to an existing CA Data Protection user, the DefaultUser and FallbackUser registry values on the policy engine hub determine which policy is applied.

User attribute data lookup

Before CA Data Protection can evaluate control triggers based on user attribute (userattr) lookup commands, it must map the recipients of an outgoing e-mail (or the sender of an incoming e-mail) onto CA Data Protection users. It can then evaluate the lookup command, comparing the attributes of the recipients (or the sender of an incoming e-mail) against the test criteria.

If the lookup command is unable to map a recipient onto an existing CA Data Protection user, the command typically evaluates to False so the trigger does not activate.

Event Import

Unlike in previous versions of CA Data Protection, Event Import does not assign e-mails or IM conversations directly to owners. Instead, it identifies 'event participants' and associates an e-mail address with each participant. Under normal conditions, address mapping is not required while an import job is running. Instead, it is used subsequently to associate imported events with specific CA Data Protection users during event searches.

However, address mapping is used during an import job if a 'user attribute' filter is specified. This enables import jobs to exclude or only include all e-mail or IM conversations associated with CA Data Protection users who have specific account attributes.

Import Policy

Import Policy provides a mechanism for applying policy triggers to imported e-mails directly before they are stored in the CMS. For import policy jobs, address mapping is not used during the import phase. Instead, address mapping is used by the policy engines to determine which policy to apply.

More information:

Overview