Exchange Journaling: Literacy issues
When you implement Exchange journaling, the content-identifer (PR_CONTENT_IDENTIFIER) of the journal messages are expected to be "ExjournalData", or with envelope journaled messages "ExjournalReport"
This header "Content-Identifier" is misspelled in Exchange to "Content-Identifer". Notice the missing "i"
Received: from server.foo.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 15 Jun 2005 14:01:33 -0500
Subject: FW: Testing 123
Date: Wed, 15 Jun 2005 14:01:29 -0500
Message-ID: 4B30D54FD6FB64FBF3A8F0B07C88D1DD0A1@server.foo.com
Content-Identifer: ExJournalReport
This content-identifier header is popularly used by some 3rd party journaling and compliance vendors to "truly" identify a journal copy of a message. This sometimes causes issues where some 3rd party vendor applications fail to process journaled messages. You will only experience this, if your 3rd party archival vendor of choice relies on this header. Typically, all messages sent to them should be archived anyway.
To mitigate this issue on Exchange 2003, download the Exchange 2003 service pack ( SP2), to put your store and other binaries at 6.5.7638. We fixed this literacy issue that can potentially put your off track on your email compliancy.
Download SP2 here:
