Exchange 2010 has two modes of journaling available, Standard Journaling and Premium Journaling. To understand what best fits your organisations needs, please refer to the following article here
Configure SMTP Collector in the Hosted Archive Service
First you will need to setup the SMTP collector in the Archive user interface.
- Login to your Archive account as the Account Administrator and select Collectors. Admin --> Collectors.
- Select Configure SMTP collector - This screen will display your unique Journal address.
- Copy this email address for use in the Exchange 2010 Mail Enabled Contact setup. Take note of the domain used in your email address, you will need this to set up the Exchange Connector later in this process.
Add your mail server(s) public IP address(es).
- Select 'Add Trusted Network'
- Enter the IP as a range (example 255.255.255.1/32)
- Click create
Before commencing please confirm your mail server IPs are listed under “SMTP Trusted Networks” within your archive accounts SMTP collector configuration. Failure to ensure all are correct will result in mail not being archived by the Sonian Cloud Archiving service.
Create a Mail-Enabled Contact
This step configures the Journal Receiver address on your Exchange 2010 server. This is the unique address to which all mail will be sent for your archiving account.
- Open the Exchange Management Console.
- Expand Recipient Configuration, and then Mail Contact.
- Click New Mail Contact, and then choose Next.
- Choose an OU as applicable and enter the following details for your new user:
First Name: SONIAN
Last Name: ARCHIVE
Full Name: SONIAN ARCHIVE
- To set the address, click Edit next to External Email Address
- Enter the Journal Address copied when setting up the SMTP collector.
- Click New to create this contact.
We recommend hiding this contact from your Global Address list. To do so:
- Right-click and select Properties for the newly created user “SONIAN ARCHIVE”.
- Tick the option labelled Hide from Exchange address lists.
Create dedicated SMTP Connector in Exchange
To reduce the load on any up-stream services you may use we recommend setting up a separate SMTP connector for your archiving journal receiver.
- Expand Organizational Configuration and select Hub Transport within the management console
- Select the Send Connectors tab
- Right-click and select New Send connector…
- This will open the “New SMTP Send Connector” wizard.
- Enter SONIAN Archive Mail as the name for the new connector and select Custom as the intended use.
- Click the Add… button to specify an address space
- Enter the domain of your journal address and set the Cost to 1 ensuring Include all subdomains is ticked.
- Click OK, Next, Next, Next and New to create the connector.
We recommend setting TLS on this connection, to ensure your internal mail is encrypted whilst traveling over a public network.
- To configure this right-click on your newly created Send Connector and select Properties.
- Select the Network tab.
- Select “Enable Domain Security (Mutual Auth TLS)”.
- Under Organization Configuration and then Hub Transport select the Journal Rules tab.
- Right-click and select New Journal Rule.
- Enter Sonian Email Archiving as the rule name
- Click Browse to choose the Sonian Archive contact as the Send Journal Reports to: address
- Ensure the Scope is set to Global.
- If your configuration demands journaling only for specific users please check the option Journal messages for recipient and select the intended users using the Browse option.
- Ensure that the Enable Rule option is checked.
- Click New.
Your Sonian Archiving account has now been configured. If you have any questions about your setup or would like to discuss the process in more detail please contact the support team.
NOTE: The details provided in this guide is general, based upon the Microsoft Exchange documentation. It remains the responsibility of the customer to:
- Ensure the correct type of journaling option is chosen based on needs, compliance and the architecture you have deployed.
- Ensure that any changes to local infrastructure, that your journaling is still operating as expected
- Any type of mailbox/user migrations initiated, the expected journaling events are validated and operating as expected