Platform Deployment Guide › Mapping Events to Users › Mapping Email Addresses to Users › Mapping Addresses - Synchronizing Email Accounts Addresses

Mapping Addresses - Synchronizing Email Accounts Addresses

Important! For the CA DataMinder features that use email address mapping to operate successfully, good synchronization is critical between your e‑mail user accounts and your CA DataMinder user accounts!

Ideally, each e‑mail or IM address processed by CA DataMinder maps directly to a CA DataMinder user. This ensures that each e‑mail or IM event is correctly associated with CA DataMinder users who sent or received the e‑mail, or who participated in the IM conversation.

In practice, things are not so simple. The continual changes to your workforce are mirrored in the endless changes to your e‑mail accounts. New accounts are created, redundant accounts are deleted and existing accounts are modified. To accommodate these ongoing changes on your e‑mail server, you need a strategy to maximize account synchronization with CA DataMinder and to minimize anomalous accounts (existing in one system but not the other). Listed below are some guidelines for synchronizing these accounts:

• Account Import: Make regular use of Account Import to import user accounts, including their email addresses, into the CA DataMinder database, from an external directory (for example Active Directory). Account Import can synchronize the CA DataMinder hierarchical user structure with that of an LDAP directory and lets you specify how to handle unknown users.
• Policy engine hub registry values: Even if you run Account Import regularly, anomalous e‑mail accounts can still arise during the intervals between import runs (for example, staff joining or leaving your organization). However, careful use of the Unknown Internal Sender and External Sender policy settings on the policy engine will ensure that policy is applied to anomalous e‑mails in a manner that allows fast remedial action.

More information:

Synchronizing Email Addresses

IM Import

Configure the Local Machine Policy