Message journaling terminology
Bifurcation In the bifurcation process, the categorizer generates a copy of
an original message to the journal recipient or to the object that is specified
in Exchange System Manager to receive copies of the archived message.
XEXCH50 The XEXCH50 extension is an Extension to SMTP (ESMTP) extension
that is used for relay of certain properties, such as envelope properties,
message properties, and recipient properties. The
PR_CONTENT_IDENTIFIER identifier in an XEXCH50 binary large object (BLOB) is set to the
ExJournalData string. The ExJournalData string enables journal messages to be
recognized as they move from server to server on the delivery path to the
journal recipient. If the XEXCH50 binary large object is not propagated between
Exchange Server computers, duplicate messages may result.
Journal Recipient The journal recipient is the mailbox or the recipient that all
journaled messages are destined for. The journal recipient is the distinguished
name (DN) in the
msExchMessageJournalRecipient attribute of the journaled stores.
Types of message journaling
The three types of message journaling are standard journaling,
BCC journaling, and envelope journaling. Standard journaling is the simplest
type of journaling. Envelope journaling is the most complex type of journaling.
It has the most features. For all three types of journaling, you must enable
the
Archive all messages sent or received by mailboxes on this
store setting on each mailbox store that you want to archive.
Standard journaling
Standard journaling bifurcates a copy of the original message to
a journal recipient that you select by using the object picker. (Standard
journaling is also known as message-only journaling.)
With standard
journaling, you cannot journal MAPI reports. Examples of MAPI reports are
delivery receipts of the Report.ipm.note.dr message class, read receipts, and non-delivery notifications (NDRs) of the Report.ipm.note.ndr message
class.
By default, standard journaling does not capture the expansion
of distribution groups, does not journal BCC recipients, and does not journal
alternate recipients.
Note In Exchange 2000 Server and in Exchange Server 2003, message
journaling is enabled only on individual mailbox stores. It is not enabled
organization-wide. Additionally, message journaling cannot be enabled on public
folder store databases. Public folder posts cannot be journaled.
To
enable standard journaling, follow these steps:
- In Exchange System Manager, click
Servers.
- Click Storage Group, right-click the
mailbox store object that you want to turn on message journaling for, and then
click Properties.
- On the General tab, click to select the
Archive all messages sent or received by mailboxes on this
store check box, and then click Browse to select an
account for the archived messages.
- Repeat steps 1 through 3 for each mailbox store object
where you want to turn on standard journaling. If you want to archive all
messages in your Exchange organization, you must enable standard journaling on
every mailbox store on every Exchange Server 2003 computer and on every
Exchange 2000 Server computer in your Exchange organization.
Note Additionally, you can create a Mailbox System Policy that has
message journaling enabled. You can add specific mailbox stores to the system
policy.
For
more information, visit the following Microsoft Web site:
Additionally,
you
can add a BCC
feature to standard journaling. It captures BCC recipients on a
message.
To turn on BCC journaling, follow these
steps.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
- Enable standard journaling, as described earlier in this
article.
- Start Registry Editor.
- Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeTransport\Parameters
- Create a Reg_DWORD key that is named JournalBCC, and then set the value to 1.
- Restart the SMTP service.
Note Do not use the
JournalBCC registry key when you use envelope journaling. The
JournalBCC key will break envelope journaling.
For more information about the JournalBCC
registry key, click the following article number to view the article in the Microsoft Knowledge Base:
810999
Bcc information is lost for journaled messages in Exchange 2000
Envelope journaling
Envelope journaling involves capturing all the available RFC2821
recipients and all the RFC2822 recipients, including CC recipients and BCC
recipients. Envelope journaling embeds the original message in a message with
the list of all those final recipients that received or will receive the
message.
Envelope journaling capabilities include the following:
- Capturing all final RFC2821 recipients and RFC2822
recipients of a message.
- Capturing all members of a distribution group
expansion.
- Capturing reports that include delivery receipts, NDRs,
read receipts, and out-of-office notifications.
Envelope journaling does not support the
JournalBCC registry key, because the BCC recipients are included in the
journaled message envelope already.
Note Envelope journaling does not work with the
JournalBCC registry key.
Do not enable this key while you use envelope journaling.The following is part of an envelope journal report:
Sender: "External E-mail Support" <smtp:Administrator@contoso.com>
Message-ID: <72F2A6CEB90C7F4C8D051364BF4A9FA41A89@lag.contoso.com
<mailto:72F2A6CEB90C7F4C8D051364BF4A9FA41A89@lag.contoso.com>>
Recipients:
"External E-mail Support" <smtp:Administrator@contoso.com>,
"Lene Aalling" <smtp:lenea@contoso.com>,
"Katja Heidemann" <smtp:katjaheidemann@contoso.com>,
"Doug Hite" <smtp:doughite@contoso.com>,
"Chris" <smtp:chris@contoso.com>,
"Katja folder" <smtp:Katjafolder@contoso.com>,
"Wide World Importers Folder" <smtp:WWIFolder@contoso.com>,
"Jeff Low" <smtp:JLow@contoso.com>
To turn on envelope journaling, follow these steps:
- Turn on standard journaling.
- Run the exejcfg -e command.
Note Envelope journaling first became available in Exchange 2000
Server with an Exchange 2000 Server post-Service Pack 3 (SP3) hotfix. That
hotfix is contained in the August 2004 Exchange 2000 Server post-Service Pack 3
update rollup.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870540
Availability of the August 2004 Exchange 2000 Server post-Service Pack 3 update rollup
The E-mail Journaling Advanced Configuration
tool, or Exejcfg.exe, turns on envelope journaling.
Note You can also turn on envelope journaling manually. To do this,
set the decimal value 512 on the
heuristics property of the Exchange organization object in the Active
Directory directory service Configuration container. When you clear the 512
value on the
heuristics property, Exchange 2000 post-SP3 and Exchange 2003 SP1 return to
the default, standard journaling.
The following file is available for
download from the Microsoft Download Center:
Exejcfg.exe
Download
the Exejcfg.exe package now. For additional information about how
to download Microsoft Support files, click the following article number to view
the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most
current virus-detection software that was available on the date that the file
was posted. The file is stored on security-enhanced servers that help to
prevent any unauthorized changes to the file.
Note The Exejcfg.exe tool is also available in Exchange Server 2003
SP1. The Exejcfg.exe tool is located in the i386\RTW folder. Although the
Exejcfg.exe tool is listed as an Exchange Server 2003 tool, it works for both
Exchange 2000 Server post-SP3 and Exchange Server 2003 SP1.
Envelope
journaling became available in Exchange Server 2003 with Exchange Server 2003
SP1, and it is implemented the same way in Exchange Server 2003 SP1 that it is
implemented in Exchange 2000 post-SP3. To implement envelope journaling in
Exchange Server 2003, you must install Exchange 2003 SP1.
How message journaling works
Message journaling is handled by the transport component
categorizer. The transport component categorizer is named Phatcat.dll. The
first step in the journal process occurs on the first server to categorize the
message, such as a mailbox server that a user is homed on or an Internet-facing
bridgehead that receives mail from the Internet.
Specifically, if a
user sends mail to and from a mailbox store where message journaling is turned
on, the categorizer generates an additional copy of the message and then sends
the copy to the journal recipient. The journal recipient could be a mailbox or
a contact. This process is named bifurcation and is defined earlier in this
article. For inbound Internet mail, the bridgehead server categorizes the
message and then sends a separate copy of the incoming message to the journal
recipient because the bridgehead determines that the recipient's store has been
marked for message journaling. The attribute that the categorizer uses to
determine if the recipient's store has been marked for message journaling is
the
msExchMessageJournalRecipient attribute on the mailbox store of the user. The
msExchMessageJournalRecipient attribute is set to the DN of the user account object under which
the messages for this store are archived.
Note Mailbox-enabled users are the recommended journal recipients in
the organization. Do not use contacts or public folders. If you have to journal
to an outside recipient, create a server-side rule to forward mail that
is delivered to the designated journal mailbox to the
contact that is specified in the server-side rule.
Also, do not use
distribution groups as the journal recipient. If you do this, extra bifurcation
occurs and an extra volume of messages is generated because of the topology
that is involved when messages are sent to a distribution group. For example, a
copy of each message is journaled to each member of the distribution group.
This process may eventually cause a large extra load on the Exchange Server
infrastructure. This extra load could cause mail flow stoppage.