ExpertGlossary

Journaling is enabled at the mailbox store level. To enable journaling, you must enter a mailbox where the journalized messages are sent. When the message is delivered to the journal recipient mailbox and journalized, the format of the message is MAPI. Depending on the requirements of your compliance solution framework, MAPI format may be acceptable. However, most of the time, Multipurpose Internet Mail Extensions (MIME) is the preferred format, because it is standardized, widely understood, structured, and able to be streamed.

Sometimes, when a third party provides the storing and sorting functions of the compliance solution framework, sending Exchange data in the MIME format over Simple Mail Transfer Protocol (SMTP) is preferred. This is done by forwarding the messages from the journal recipient mailbox to the SMTP address by using a Microsoft Office Outlook® server-side rule.

In other cases, journalized messages can be retrieved from the journal recipient mailbox by using Post Office Protocol version 3 (POP3) or Internet Message Access Protocol version 4rev1 (IMAP4). This also provides a MIME format for the message.

The reason you cannot forward journalized messages directly from the mailbox database where journaling is enabled is because some of the envelope data (for example, Bcc recipients and expanded distribution list recipients) is added by the Exchange Information Store service upon delivery to the journaling mailbox. Therefore, if you journal all mail directly to SMTP, Bcc and expanded distribution list recipient data is lost.

the ability to record all communications in an organization. E-mail communications are one of many different communication mechanisms that you may be required to journal. Therefore, journaling in Exchange has been developed to enable the messaging administrator to feed messaging data into a larger journaling solution, while using minimum overhead.

It is important to understand the difference between journaling and archiving. Journaling is the ability to record all communications; alternatively, archiving refers to reducing the strain of storing data by backing it up, removing it from its native environment, and storing it elsewhere. That said, you may use Exchange journaling as a tool in your e-mail retention or archival strategy.

When journaling is enabled in a mailbox database and a user who has a mailbox on that mailbox database sends a message, the server generates two messages: one for the recipients and one for the journal recipient. When a message is submitted to a journalized mailbox database, the mailbox database processes the message as it typically would to deliver it, but it also creates a message for the journaling recipient. When a journalized mailbox database receives a message, most of the time, the message has been journalized already. In the receive case, extra processing (beyond reading the journaling property) is required only when the receiving server is the expansion server for the distribution list or when the distribution list is hidden or query-based.

Therefore, you can estimate the effect of journaling on a mailbox database by assuming that the enabled mailbox database can process approximately half of the messages being sent, as long as all other conditions, such as CPU power, bandwidth, storage space, and disk speed, remain constant.

• The journal recipient for the sender's mailbox database will receive a complete record of all recipients who receive a copy of a message sent by that sender. The record may arrive through multiple journal reports, but all recipients will be covered. This is because the sender is always at the root of the distribution tree.
• The journal recipient for a recipient's mailbox database will receive at least a partial record that mentions every recipient in that mailbox database for all messages received by recipients in that mailbox database. That record may arrive through multiple separate journal reports.