Google Message Archiving Microsoft Exchange Journaling Configuration Guide For Exchange Server 2007 and 2010 - Manual (Page 12)

14 Message Archiving - Microsoft Exchange Server 2007 and 2010 Journaling Configuration Guide
Organize Mailbox Databases and Journal Rules
Journaling email messages can impact both the performance of your email server
and the amount of outbound corporate traffic on your Internet connection. If you
want to archive messages for only a specific set of users on your network, you
can use the following options:
• Standard Journaling: With Standard journaling, the Journaling agent
journals all messages sent to or received from recipients and senders
assigned to a particular mailbox database. You can delegate your users to
different mailbox databases according to whether or not you want to
implement journaling for those users. For example, messages for all users in
mailbox database A are journaled, while messages for all users in mailbox
database B are not journaled.
• Premium Journaling: With Premium journaling, the Journaling agent
journals messages according to rules you configure. Journaling rules specify
the scope of journaling (global, internal, external), and whether messages are
journaled for specific recipients (mailbox, contact, distribution group).
• Global scope covers all messages that pass through a Hub Transport
server. Messages processed at the global level may have already been
processed at the internal or external level.
• Internal scope covers all messages that are sent and received within the
Exchange 2007 or 2010 organization.
• External scope covers all messages sent and received outside the
Exchange 2007 or 2010 organization.
For example, you can create a rule to journal all internal messages, as well as
messages sent to a distribution list of customers outside your Exchange
organization.
Identify Journaled Users in Message Archiving
To ensure that all journal reports are properly archived, you need to be sure that
all the Exchange users for whom you want to archive messages are added to user
organizations in Message Archiving.
When Message Archiving receives journal reports, it compares their sender and
recipient addresses with the addresses of the users in the organizations for which
you turned on archiving in your Message Security service. Based on this
comparison, Message Archiving stores only those journal reports for users who
also belong to user organizations for which archiving is implemented.
By the same token, when you implement journaling on Exchange for users who
do not belong to Email Security user organizations, the corresponding journal
reports are sent to Message Archiving, processed, and then deleted. The
handling of nonrelevant journal reports creates needless network traffic and
unnecessary processing overhead on your Exchange Server.