Document created by user.oxriBaJeN4 Employee on Sep 11, 2015Last modified by user.oxriBaJeN4 Employee on Apr 2, 2019
Version 21Show Document
  • View in full screen mode

Mimecast automatically archives all inbound and outbound emails as they pass through the Mimecast cloud. Mimecast can also be configured to capture internal emails between users (which normally would not traverse the internet). This is done using a process called Journaling. In this way, internal email communication can also be added to your organization’s Mimecast Archive.


Records retention is a legal requirement for many businesses, which makes Archiving essential for email data. Although the external email communications (inbound or outbound) for a business are automatically Archived based on the organization’s policies, internal email communication should also be retained.  This can be achieved through the use of a Journal connector, which facilitates the upload of internal email communication to Mimecast so that it is stored in a single Archive. It is then very simple to use Mimecast to search across all internal and external email data when required. Users are also able to search through all their emails in a single archive view.



How Does Journaling Work?

Journal messages older than 30 days will not be processed and archived. If you require older messages to be part of your archive, contact your customer success manager for ingestion.

Journaling requires configuration in the customer environment and on Mimecast. Journaling needs to be enabled, which then allows the internal mail server to send a copy of all emails to a journal mailbox. Once Journaling is configured on Mimecast, all emails will periodically be delivered/retrieved using either SMTP or POP3 (or POP3S). These emails will then be archived in the customer’s Mimecast account so that ultimately a full archive of all internal and external emails is available.


Depending on whether POP3 (POP3S) or SMTP is used, will cause a slight variation in how the emails are retrieved/delivered to Mimecast:


SMTPThe customer’s mail server will deliver the journal messages to Mimecast using real-time SMTP push technology.
POP3Mimecast will regularly log into the journal mailbox and extract up to 100 emails at a time. At the time of logging out, if there are no more messages in the journal mailbox, Mimecast will wait a few minutes before reconnecting.

It's important to configure the correct journal type on your Journal connector, to match the type of journal traffic sent from your email environment. Incorrectly configured journal types can cause unexpected issues to occur. 

Journaling Systems


The table below lists supported and unsupported Journaling Systems. Select the appropriate article to learn more about configuring Journaling for Mimecast.


Supported by MimecastUnsupported
Exchange 2016 & 2013

Exchange 2016 / 2013 Standard / Premium Journaling (Premium requires Enterprise Cals)


Send Mail

MAC Mail Server

Squirrel Mail

Exchange 2010 & 2007

Exchange 2010 / 2007 Standard / Premium Journaling (Premium requires Enterprise Cals)

Office 365Configuring Office 365 Journaling. Check your Office 365 plan on the Microsoft site.
G SuiteConfiguring Journaling for G Suite 

Unsupported systems can still communicate with Mimecast using SMTP or POP3, but are not supported by our Mimecast Support teams. 

Journaling Reference



Troubleshooting Journaling



Unsupported Journal Servers


2 people found this helpful