Exchange Mailbox Agent ContentStore Mailbox

The ContentStore Mailbox provides SMTP-based journaling. Journaled messages are sent from any mail server to an external recipient using the SMTP protocol. In this case, the external recipient is a mailbox on the Commvault ContentStore Mail Server (SMTP).

The journaled messages are stored as messages on the ContentStore Mail Server (SMTP). After the messages are archived, you can run a cleanup job to delete the messages from the SMTP server. When journaled messages are restored, they are restored as .eml files.

If the CommServe computer is offline, the ContentStore Mailbox continues to receive messages. The messages are not held in a queue on the Exchange server.

Note

You must use ContentStore Mailbox and configure journaling for Exchange 2019 servers.

Benefits

  • Reduces infrastructure costs with SMTP journaling solution.

    Sends email directly into the Content Store mail server(SMTP) access node.

  • Reduces the additional cost on Microsoft exchange & Office 365 User mailbox license

    Helps in reducing costs by implementing SMTP journal solution.

  • Provides scalable architecture

    Supports multiple SMTP servers for load balancing and high availability to avoid the piling of queue on exchange server in case of failure of one node.

  • Reduces storage requirements

    Reduces the requirement of storage on the exchange server since the mails are stored on Content store mail server (SMTP) Access nodes.

  • Reduces load on the Exchange server

    Helps in reducing the load on the exchange server as the journaled messages are backed up from Content store mail server (SMTP) Access node.

  • Avoids duplicate journaled messages in all messaging environments (On-premise /Online / Hybrid)

    Helps in reducing the load on the exchange server as the journaled messages are backed up from Content store mail server (SMTP) Access node.

  • Archives journal emails

    Archives journal emails from on-premise email platforms, such as Microsoft Exchange Servers, Lotus Domino & cloud-based email services, such as Office 365 and Google Mail.

  • Captures metadata

    Captures all metadata, such as BCC, point in time distribution list membership, journal report information.

  • Search

    Compliance search and case manager are supported.

  • End User Access

    The end user can login to the end user search to access and download the deleted messages.

ContentStore Mailbox supports Envelope Journaling & Non-envelope journaling.

Envelope Journaling

Envelope journaling sends a copy of the email as an email attachment. The original email becomes an attachment, and the sender, the recipients (To/Cc/Bcc), and the message-Id move to the message body.The ContentStore Mailbox can capture BCC and distribution list information if the sending mail server has envelope journaling enabled. This information is not captured if envelope journaling is not enabled. Any type of mailing servers is supported if it provides the envelope format.

ContentStore Mailbox supports envelope journaling and non-envelope journaling.

Consult the documentation for your mail server to determine how to enable journaling for your mail server.

The ContentStore Mailbox will capture all other information if envelope journaling is not enabled.

Non-Envelope Journaling

Non-Envelope journaling sends a copy of the email as you would see in a mail client. The ContentStore Mailbox does not capture the BCC and the distribution list information.

The ContentStore Mailbox will capture all other information if envelope journaling is not enabled.

ContentStore Mailbox supports envelope journaling and non-envelope journaling.

Load Balancing and Fault Tolerance

The ContentStore Mailbox supports the following methods for load balancing:

  • Deploying a single send connector with multiple smart hosts

  • Hardware load balancers

  • Mail exchange records (MX records)

The method that you choose depends on your environment.

For more information, consult Microsoft documentation. For example, see the following Microsoft TechNet articles:

Loading...