Enterprise Vault™ Compliance Accelerator Administrator's Guide
- Introducing Compliance Accelerator
- Product documentation
- Introducing the Compliance Accelerator client
- Setting up employees and employee groups
- Assigning roles to employees
- Working with departments
- Implementing Chinese Walls security
- Managing exception employees
- Grouping departments into partitions
- Using attributes to classify departments
- Searching for items
- About searching with Compliance Accelerator
- Building Compliance Accelerator search schedules
- Defining hotwords to search for
- Manually reviewing items
- About reviewing with Compliance Accelerator
- Escalating items
- Working with research folders
- Exporting items
- Creating and viewing reports
- Available Compliance Accelerator reports
- About viewing Compliance Accelerator datasets using the OData web service
- Appendix A. Customizing Compliance Accelerator
- Setting Compliance Accelerator system configuration options
- Appendix B. Importing configuration data from an XML file
- Appendix C. Troubleshooting
- Issues with Compliance Accelerator reports
Configuring how Compliance Accelerator handles email addresses
When Enterprise Vault archives a message, it uses several methods to determine whether the email addresses of the sender and recipients are internal or external to your company. Enterprise Vault then populates the message's metadata properties with information about its direction of travel (internal, inbound, or outbound). When Compliance Accelerator later captures the message, it determines the message's direction of travel from the metadata information that Enterprise Vault has added to the message.
For those messages that an Enterprise Vault Journaling task has archived, how you configure the task determines whether it treats email addresses as internal or external addresses. So, in the case of the Exchange Journaling task, you must specify a system mailbox for the task to use when it logs on to the Exchange server. When the Journaling task encounters an email address in which the domain name matches that of an SMTP domain listed for the system mailbox account, it considers the address to be internal. For example, suppose that the following SMTP addresses are listed for the system mailbox:
Any of the following addresses are recognized as internal:
Where [*.] means that the string can be repeated, as in firstname.lastname@example.org. Other addresses are treated as external.
The SMTP Archiving task is different. For this task to set the message direction correctly, you must specify the SMTP domains that Enterprise Vault should consider internal to your company.
Use either of the following methods to specify the SMTP domains that Enterprise Vault should treat as internal. These methods work with all of the Enterprise Vault archiving tasks: the Exchange and Domino Journaling tasks, SMTP Archiving task, and so on.
In the Enterprise Vault Administration Console, in the properties for the Enterprise Vault site, configure the advanced SMTP setting that is called List of internal SMTP domains.
This is the recommended way to add internal domains. For more information, see the Enterprise Vault Administrator's Guide.
Add an additional SMTP alias address with the required domain to the user who is associated with the task. You can do this in Active Directory, Exchange Administrator, or the Domino LDAP directory, as appropriate.