Article ID: 973040 - View products that this article applies to.
In a mixed Microsoft Exchange Server 2003 and Microsoft Exchange Server 2007 environment, you enable blind carbon copy (Bcc) Journaling or you enable Envelope Journaling on your Exchange Server 2003 stores. Additionally, you type in an Exchange Server 2007 mailbox on which the journalized messages are sent. In this situation, the Bcc information is lost when the Exchange Server 2007 server receives the journalized messages. Therefore, the journalized message appears like a copy of the original message to be journalized, instead of the expected Bcc journal report or Envelope journal report.
This problem occurs because Exchange Server 2003 and Exchange Server 2007 uses various mechanisms to generate journalized messages.
To resolve this problem, install the following update rollup:
2279665After you apply this hotfix on all transport servers, use the Set-TransportConfig cmdlet together with the LegacyJournalingMigrationEnabled parameter. This determines whether journalized messages from Exchange Server 2003 is reformatted by Exchange Server 2007.
(http://support.microsoft.com/kb/2279665/ )Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
Note The default value for the LegacyJournalingMigrationEnabled parameter is False. If the value is False, Exchange Server 2007 keeps the same behavior as it was before you apply this hotfix. If you set the value for the LegacyJournalingMigrationEnabled parameter to True, the journalized messages are reformatted by Exchange Server 2007.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about Exchange Server 2003 Journaling, visit the following Microsoft Website:
General information about Exchange Server 2003 JournalingFor more information about the Set-TransportConfig cmdlet, visit the following Microsoft Website:
General information about the Set-TransportConfig cmdlet
Article ID: 973040 - Last Review: September 9, 2010 - Revision: 3.0
Contact us for more help