Enterprise Vault™ Introduction and Planning
- About this guide
- Overview of Enterprise Vault
- How Enterprise Vault works
- About Enterprise Vault indexing
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Archive Discovery Search Service
- About the Enterprise Vault Outlook Add-In
- About Enterprise Vault Search
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server archiving
- About Exchange Server archiving and user mailboxes
- Exchange Server and journal mailbox archiving
- Exchange Public Folder archiving
- File System Archiving
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Skype for Business Archiving
- Enterprise Vault Accelerators
- About Compliance Accelerator
- The Compliance Accelerator client application
- About Discovery Accelerator
- Discovery Accelerator client application
- Building in resilience
- About Enterprise Vault and VCS
- About Enterprise Vault and Windows Server Failover Clustering
- About Enterprise Vault building blocks
- Planning component installation
- Where to set up the Enterprise Vault Services and Tasks
- Installation planning for client components
- Planning your archiving strategy
- How to define your archiving policy for user mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan settings for retention categories
- How to plan vault stores and partitions
- About Enterprise Vault reports
About Enterprise Vault SMTP Archiving
Enterprise Vault SMTP Archiving lets Enterprise Vault archive data that is sent to the Enterprise Vault server using SMTP protocol. Any application that can send information to an SMTP server can send data to Enterprise Vault.
Enterprise Vault SMTP Archiving enables you to do the following:
Archive Exchange journal email directly into an archive using SMTP. You could use this functionality instead of Exchange journaling with Enterprise Vault Exchange journal archiving.
Archive email from other messaging platforms that can send to an SMTP server, for example Office 365, Google Apps, Zimbra, and Sun Mail System.
Archive data from any application that is capable of sending email to an SMTP server.
Archive data from physical devices such as printers, fax machines, or scanners. This provides opportunities for electronic mailroom automation and records management workflow.
Populate user mailbox archives from the SMTP journal feed. All email that is sent from or received by the user can be stored in the user's mailbox archive. There is no folder synchronization with SMTP Archiving.
Figure: SMTP Archiving overview shows an example of a simple SMTP Archiving environment:
A Message Transfer Agent (MTA) receives an SMTP message from an application such as an Exchange Server.
The MTA sends the message to the destination mailbox, and also copies or journals the message to the SMTP routing address for the Enterprise Vault SMTP server.
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 SMTP holding folder.
The SMTP Archiving task processes the message file in the holding folder, and archives it in the archive that is specified for the target address. During processing, the task applies the retention category that is specified in the target properties. It ensures that Enterprise Vault indexes any X-Headers that are listed in the policy.
Enterprise Vault SMTP Archiving provides the following benefits:
Simplified architecture and reduced infrastructure costs for journaling, with no dependency on MAPI or the need to manage large journal mailboxes. The journal feed can be sent directly to Enterprise Vault instead of maintaining multiple journal mailboxes on dedicated Exchange servers.
Single Instance Storage. Enterprise Vault uses single instance storage to deduplicate messages.
Provisioning groups. You can provision multiple users for SMTP Archiving at the same time. Target users that you add to the groups can be Active Directory users or SMTP addresses that are not associated with an Active Directory account. Depending on the type of provisioning group, the members' messages are all stored in the same archives, or each member is provisioned with their own archive.
Enterprise Vault can capture and index metadata, such as BCC addresses, and journal report information.
You can add X-Headers to messages that are sent to Enterprise Vault to override the default retention category or destination archive. You can also use X-Headers to add information to the Enterprise Vault index.
Messages can be stored in existing archives, or in dedicated SMTP archives.
Scalable architecture. Enterprise Vault can support multiple SMTP servers.
You can enable message tracking to log the details of messages that each SMTP server receives.