his article is intended to provide assistance when migrating from POP3 to SMTP Journaling, whilst 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 first few 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.
- Log onto your Microsoft Exchange Server, and create an external SMTP contact. This will be used as your journaling email address e.g. email@example.com
- Provide Mimecast Support with the external SMTP recipient address. Mimecast will add this domain to your account, which will ensure that emails will be accepted once the actual journaling process has been enabled for each message store.
- Log into the Mimecast Administration Console, and create an additional Journal Connector
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:
- Stop the SMTP service on your Exchange server, using either the Exchange Management Console or the Exchange server shell
- 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
- Enable the journal rule
- Restart the SMTP service
- Confirm emails are being journaled to the new contact address
- Login to the Mimecast Administration Console, and navigate to Administration | Services | Journaling
- Delete the POP3 Journal Connector.This should only be deleted once the queue for this journal connector is empty.