Message-only journaling is enabled
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2007-01-10
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine whether the msExchMessageJournalRecipient attribute has been configured to copy mail to a recipient mailbox. The msExchMessageJournalRecipient attribute is an attribute of mailbox store objects in Active Directory. By default, the msExchMessageJournalRecipient attribute is not configured. If the Exchange Server Analyzer finds that the msExchMessageJournalRecipient attribute is configured, the Exchange Server Analyzer displays a non-default configuration message. The Exchange Server Analyzer also displays the database name and server name where message-only journaling is enabled.
Exchange Server 2003 Message-only journaling or Exchange Server 2007 Standard journaling creates a copy of all messages and the corresponding P2 message header data to and from users on a mailbox database and sends the message copy to a specified mailbox. The P2 message header contains only the message recipient data that the sender declared to the recipients. If an external message is received from the Internet, Exchange Server journals the P1 message headers. The P1 message header is the address information that is used by message transfer agents (MTAs) to route mail. By default, when message-only journaling is enabled, Exchange Server does not account for blind carbon copy (Bcc) recipients, recipients from transport forwarding rules, or recipients from distribution group expansions. Also, Exchange Server does not archive MAPI report messages, such as read receipts, and out-of-office notifications.
Journaling messages can consume many disk, network, and CPU resources. Therefore, journaling requires thorough deployment planning. Journaling should be enabled only in the context of an overall journaling solution framework.
Ignore this non-default configuration message if the following conditions are true:
Your business requires journaling.
You have deployed a journaling solution framework.
Otherwise, you should turn off journaling functionality.
To turn off message-only journaling on a database in Exchange 2000 Server and Exchange Server 2003
In Exchange System Manager, expand Servers, expand <your Exchange server>, expand <storage group>, and then right-click the mailbox store.
On the General tab, clear the check box Archive all messages sent or received by mailboxes on this store.
Wait 15 minutes for the Exchange store to apply changes. You do not have to restart the Microsoft Exchange Information Store service.
To turn off standard journaling on a database Exchange Server 2007
- Follow the guidance in the Exchange Server 2007 product documentation How to Disable Per-Mailbox Database Journaling (http://go.microsoft.com/fwlink/?LinkId=80889).
For more information about how to deploy a journaling solution with Exchange Server 2003, see Journaling with Exchange Server 2003 (http://go.microsoft.com/fwlink/?LinkId=47581).
For more information about how to deploy a journaling solution with Exchange Server 2007, see Overview of Journaling (http://go.microsoft.com/fwlink/?LinkId=80820).