Google Message Archiving Microsoft Exchange Journaling Configuration Guide For Exchange Server 2000 and 2003 User Manual
Page 36
40
Message Archiving - Microsoft Exchange Journaling Configuration Guide
In addition to the recommendations from Microsoft, we offer the following
guidelines to ensure that your Exchange journaling environment is fully
compatible with Message Archiving:
1.
Route mail coming from the internet to an Exchange 2003 server first.
Why? Having Exchange 2003 process the messages first cuts down on
creating duplicate journal reports.
Note: If you use Postini for inbound mail, use the Exchange 2003 server as
the inbound server, or create two email configs and distinguish between
Exchange 2003 and Exchange 2007 users if required.
2.
Place the journal recipient on the Exchange 2003 server only until all users
have been moved to Exchange 2007. Do not split the traffic between
Exchange 2003 and Exchange 2007 journal recipients.
Why? This is a best practice from Microsoft as there are pitfalls with locating
the journal user on Exchange 2007 in a mixed environment.
3.
Use only standard journaling during the migration from Exchange 2003 to
Exchange 2007.
Why? There is a problem with duplication issues when using premium
journaling in this configuration. All mail sent from Exchange 2003 users to
Exchange 2007 users is duplicated.
Note: This problem is amplified when Exchange 2007 is the initial server to
receive external mail.
4.
Follow the instructions in the Message Archiving Microsoft Exchange
Journaling Configuration Guide for Exchange Server 2007 for setting up
journaling:
Pay particular attention to:
•
Step 1: Create SMTP Contact, where you configure the message format
settings for the SMTP contact (set Use MAPI rich text format to Never).
•
Step 5: Enable Automatic Forwarding, where you allow automatic
forwarding to the Postini domain (set Exchange rich-text format to Never
use)
These two settings ensure that journaled messages are sent in MIME format.