Enterprise Vault™ Setting up SMTP Archiving
- About this guide
- Introducing Enterprise Vault SMTP Archiving
- Installing SMTP Archiving
- Configuring SMTP Archiving
- Steps to configure SMTP Archiving
- Planning your configuration
- Configuring the Enterprise Vault SMTP Servers in the site
- Adding an SMTP Archiving task and holding folder
- Configuring retention categories and retention plans
- Creating SMTP policies
- Configuring archives for SMTP messages
- Adding SMTP routing addresses
- Checking settings for SMTP Journaling
- Additional configuration for Compliance Accelerator
- Provisioning users for SMTP Group or SMTP Mailbox Journaling
- About SMTP provisioning groups
- Adding an SMTP Group Journaling provisioning group
- Adding an SMTP Mailbox Journaling provisioning group
- Changing the order of the SMTP provisioning groups
- Deleting an SMTP provisioning group
- Adding or deleting an SMTP Provisioning task
- SMTP Provisioning task summary reports
- Configuring the SMTP site setting, Selective Journal Archiving
- Adding SMTP target addresses manually
- Using the SMTP dashboard
- PowerShell cmdlets
- Appendix A. Configuring target address rewriting
About SMTP Journaling
Typically within an organization, SMTP messages are delivered to user mailboxes by one or more MTAs. The MTAs are usually Exchange Servers, or SMTP servers. You configure these MTAs to journal or BCC a copy of each message to an Enterprise Vault SMTP routing address, for example, journal1@ev.example.com.
In Enterprise Vault, you configure the routing addresses as manual SMTP targets, and associate each target address with one or more archives. In the manual target properties, ensure that the target address is enabled for archiving. The check box, , must be selected to enable a target address for archiving. When you add a new manual target, the check box is selected by default. Note that you cannot use SMTP Provisioning groups to add the routing addresses.
The Enterprise Vault SMTP server checks that the recipient address in an incoming message is an SMTP target, and adds this routing address to the message as an X-RCPT-TO header. The SMTP server then places the message as an .eml file in the SMTP holding folder.
The SMTP Archiving task then processes the message file in the holding folder. As you enabled the target address for archiving, the task stores the message in one of the archives associated with the target routing address. The archive types that you can use for journal archiving are SMTP, Shared, Exchange Journal, or Domino Journal archives. In archive types that contain folders, such as SMTP archives, the SMTP Archiving task stores all messages in the Inbox. Other journal archive types, such as Shared and Exchange Journal archives, do not contain folders. In these archives, the task stores all messages in the root of the archive.
In SMTP Journaling, the SMTP Archiving task only needs to examine the X-RCPT-TO field in each message in the holding folder. The advanced SMTP site setting, , configures the archiving task to search all of the sender and recipient fields (X-RCPT-TO, To, CC, BCC, From, Sender) in each message. If you are not using SMTP Journaling in combination with another type of SMTP archiving, this advanced site setting should be set to , the default value. This optimizes performance.
Figure: Example of SMTP Journaling shows a simple environment with one Enterprise Vault SMTP server. (Production environments typically include several Enterprise Vault SMTP servers.) As there could be a large volume of messages for journaling, it is advisable to spread the archiving load over several Enterprise Vault storage servers. You can do this by creating several journal archives in different vault stores. A different Enterprise Vault storage service should manage each of the vault stores. If you use a single SMTP routing address, we recommend that you associate the routing address with multiple archives in different vault stores hosted on different Enterprise Vault storage servers. Enterprise Vault automatically performs load-balancing to spread the archiving load over several Enterprise Vault storage servers. Alternatively you can implement target address rewriting on the SMTP servers.
If the relay MTA is Exchange Server, you can create journal rules to select the appropriate routing address for the Enterprise Vault SMTP server.
See Journaling messages to Enterprise Vault from Exchange Server or Office 365.