SMTP Journaling - Migrate POP3 to SMTP

This article is intended to provide assistance when migrating from POP3 to SMTP Journaling, while ensuring that no emails are lost. Once you are ready to migrate your journaling solution from POP3 to SMTP journaling, you will need to complete the initial steps for configuring SMTP Journaling. All of these steps are explained in more detail for all Exchange Server versions in the Journaling article.

For more information on extracting internal emails in SMIME environments, please see the Configure Journaling with SMIME article.

Preparation Steps

1. Log into your Microsoft Exchange Server and create an external SMTP contact. This will be used as your journaling email address e.g. [e-mail]

2. Log into the Mimecast Administration console to create a Journal sub-domain and Journal Service mailbox which will ensure that emails will be accepted once the actual journaling process has been enabled for each message store.

   Note:

   See the "Adding an Internal Sub-Domain" section of Configuring Internal Domain / Subdomains here Configuring Internal Domain / Subdomains.

3. Create an additional Journal Connector.

Migration

Note:

Mimecast recommends making these changes after normal working hours. Stopping the SMTP service will prevent your Exchange server from sending and receiving emails whilst you make the necessary changes to the journaling rules on your Exchange server.

The steps below should be followed to ensure that no emails are lost during the migration progress:

1. Stop the SMTP service on your Exchange server using either the Exchange Management Console or the Exchange server shell.
2. Disable the existing journal rule and modify the rule to no longer journal to the local journal mailbox but to the external contact created previously.
3. Enable the journal rule.
4. Restart the SMTP service.
5. Confirm emails are being journaled to the new contact address.
6. Log in to the Mimecast Administration Console, and navigate to Administration | Services | Journaling.
7. Delete the POP3 Journal Connector.

Note:

This should only be deleted once the queue for this journal connector is empty.