Configuring Remote (SMTP) Journaling for Exchange 2013/2016

These instructions are for the current archive service, not the legacy archive.

Journaling In Exchange 2013/2016

Exchange 2013/2016 provides several methods for journaling, including:

Option 1: Remote (SMTP) journaling
- A copy of all email sent or received by the entire organization or members of a defined security group to an external SMTP address. Proofpoint Essentials provides you with the SMTP address to use for this configuration.
Option 2: Journaling via IMAP
- A copy of all email sent to received by the entire organization or members of a defined security group to a local mailbox. Proofpoint Essentials can connect to the mailbox via an IMAP connection.

While the Essentials Email Archive supports both methods, remote (SMTP) journaling is the preferred configuration method.

You can choose one of the following options:

Enable journaling for the entire enterprise by creating a journaling rule to send messages from the Hub Transport Server to Proofpoint Essentials SMTP Contact. Hub Transport-level journaling is only supported in the Enterprise version of Exchange 2010.
Configure your mailbox databases to point to a Proofpoint Essentials SMTP Contact. Enabling journaling for individual mailbox databases also requires you to configure the mailbox databases to point to the Proofpoint Essentials SMTP Contact.

Note: Remote Journaling should be enabled directly to Proofpoint Essentials SMTP contact, not by using the forwarding rule.

In the Exchange Admin Center, navigate to Recipients, and select Contacts.
Click the "+" icon followed by Mail Contact.
Enter a first name (SMTP), last name (Connection), display name (SMTP Connection), name (SMTP Connection), and alias (Journaling).
in the External email address field enter the email address of the SMTP address provided when you created a connection in Proofpoint Essentials (e.g. uniqueaddress@us.earchive.cloud).
Click Browse and select the desired Organization unit.
Click Save.

In the Exchange Admin Center, navigate to mail flow, and select Send Connectors.
Add a send connector (click the "+" sign)
Enter a descriptive Name for the connector.
For Type, select Custom.
Click Next.
Under Network settings select MX record associated with recipient domain.
Click Next.
Click "+" to edit Address space.
Set Type to SMTP.
For Full Qualified domain name (FQDN): enter "*.earchive.cloud".
Set Cost field to 1.
Click Save.
Click Next.
Click "+" to edit Source server.
Select the transport server(s) that will be associated with the connector.
Click Add.
Click OK.
Click Finish.

In the Exchange Admin Center, navigate to servers, and select databases.
Select a database value and click the pencil (edit) icon.
Click maintenance.
Click Browse and choose the contact created in the previous procedure, then click OK.
Click Save.

Repeat these steps for the other mailbox databases.

In the Exchange Admin Center, click compliance management (in the list of the left)
Click the journal rules tab.
Add a new journal rule (click the “+” sign).
In the Send journal reports to field, enter the email address of the journaling mailbox (e.g. uniqueaddress@earchive.cloud) created when you added an SMTP connection on Proofpoint Essentials.
Enter a descriptive Name for the rule.
From the If the message it sent to or received from... list, choose Apply to all messages.
From the Journal the following messages... list, choose All messages.
Click Save.

It is recommended that you specify an alternate journaling mailbox in case the SMTP connection stops accepting traffic. You can then create an IMAP connection to collect any messages that were not sent via SMTP.

In the Exchange Admin Center, click compliance management (in the list of the left)
Click the journal rules tab.
Click Select Address next to Send undeliverable journal reports to.
In the NDR for undeliverable journal reports window that opens, click Browse.
Select a mailbox in the dialog box and click OK.
Click Save.

*The information in this article is correct as of Oct, 2017*

Choose files or drag and drop files

Tags:

Was this article helpful?

Yes