Veritas Enterprise Vault™ Setting up SMTP Archiving
- About this guide
- Introducing Enterprise Vault SMTP Archiving
- Installing SMTP Archiving
- Configuring SMTP Archiving
- Configuring target address rewriting
- PowerShell cmdlets
About Enterprise Vault SMTP Archiving
Enterprise Vault SMTP Archiving enables Enterprise Vault to archive data that is sent to the Enterprise Vault server using the SMTP protocol.
SMTP Archiving can be used to provide journaling for any application that can send messages over SMTP. Journal report messages (P1 messages) that are sent to Enterprise Vault SMTP servers must comply with the envelope journal report format that is described in the article, http://technet.microsoft.com/library/bb331962.aspx. The journal report messages are processed by Enterprise Vault, and available for searching using an eDiscovery application, such as Veritas Discovery Accelerator.
Note that SMTP Archiving does not currently process the journal report information in messages that are journaled by Domino Server.
Figure: SMTP Archiving overview shows an example of a simple SMTP Archiving environment:
An MTA receives an SMTP message from some application.
The MTA could be an Exchange Server, or some other server that can route SMTP messages.
The MTA sends the message to the destination mailbox.
In addition, the MTA is configured to copy or journal the message to the SMTP routing address for the Enterprise Vault SMTP server. The domain used in the routing address could just be an MX record alias that you create in DNS to point to the Enterprise Vault SMTP server, for example, ev.example.com.
In Enterprise Vault, you must configure the routing address as an SMTP target address.
The Enterprise Vault SMTP server receives the message, and adds the routing address to the message as an X-RCPT-TO header.
The SMTP server then places the message as an email (.eml) file in the folder that you assign as the SMTP holding folder.
The SMTP Archiving task processes the message file in the holding folder, and archives it in the archive specified for the target address. During processing, the task applies the retention category that is specified in the target properties, and ensures that Enterprise Vault indexes any X-Headers that are listed in the policy.
An Enterprise Vault SMTP server is an Enterprise Vault server that hosts the Enterprise Vault SMTP Archiving components. The components include an SMTP server and an Enterprise Vault SMTP Archiving task. Table: Overview of SMTP Archiving components provides an overview of the main components of SMTP Archiving. An Enterprise Vault SMTP server can host only one SMTP server and one SMTP Archiving task. However, there can be multiple Enterprise Vault SMTP servers in a site. When you configure SMTP Archiving, the Enterprise Vault SMTP server settings and target configuration information are shared with all the Enterprise Vault SMTP servers in the site. This means that any Enterprise Vault SMTP server in the site can archive messages sent to any SMTP target in the site. You can use a load balancing solution to distribute the SMTP traffic evenly across the SMTP servers in the site.
A simple load balancing solution is to configure a DNS MX record for each of the Enterprise Vault SMTP servers, and give each record equal preference. If you use a single address for journaling, for example SMTPjournal@example.com, and the volume of traffic is more than one Enterprise Vault SMTP server can manage, you can also implement address rewriting on the SMTP servers. Address rewriting enables you to spread the archiving load over several Enterprise Vault storage servers.
See About target address rewriting.
You can configure SMTP Archiving in different ways depending on whether you want to archive all messages that are sent to the Enterprise Vault SMTP servers, or just selected messages. Table: SMTP Archiving configurations provides a summary of the different journaling configurations that you can implement. These configurations are explained in more detail in the sections indicated.
Table: SMTP Archiving configurations
SMTP Archiving configuration | Description |
---|---|
SMTP Journaling | All messages that are sent to the Enterprise Vault SMTP servers are stored in one or more journal archives. |
Selective SMTP Journaling | You configure the Enterprise Vault SMTP servers to archive only messages to or from specific addresses. Enterprise Vault can store all the messages in the same archive, or in several different archives. |
SMTP Mailbox Journaling | This is similar to Selective SMTP Journaling. Enterprise Vault stores all messages to and from a specific address in a journal archive that is exclusive to that address. |
You can configure SMTP Archiving to perform the following combinations of journaling:
SMTP Journaling and SMTP Mailbox Journaling.
See Configuring SMTP Journaling and SMTP Mailbox Journaling.
Selective SMTP Journaling and SMTP Mailbox Journaling.
See Configuring Selective SMTP Journaling and SMTP Mailbox Journaling.
With Selective SMTP Journaling, SMTP Mailbox Journaling, or the above combinations, a copy of a message may be stored in multiple archives. Enterprise Vault implements single-instance storage as permitted by the vault store configuration.
If a message contains multiple target addresses that have the same destination archive, and the same retention category and policy are applied to the target addresses, only one copy of the message is stored in the archive.
To implement SMTP Archiving, you install the Enterprise Vault SMTP Archiving components and the Enterprise Vault server components on the computers that you want to perform SMTP Archiving. Table: Overview of SMTP Archiving components provides an overview of the main components of SMTP Archiving. You can configure SMTP Archiving using the Enterprise Vault Administration Console, or Enterprise Vault PowerShell cmdlets.
Table: Overview of SMTP Archiving components