When you upgrade the Messaging Security Agent from Client Server Messaging Security Suite 2.0 to Client Server Messaging Security 3.5, Client Server Messaging Security 3.5 automatically removes Client Server Messaging Security Suite 2.0 ScanMail and replaces it with Client Server Messaging Security 3.5 Messaging Security Agent.
When you upgrade Client Server Messaging Security Suite 2.0 ScanMail to Client Server Messaging Security 3.5 and the Messaging Security Agent has configuration settings similar to the previous versions, then the upgraded version maintains these customized configurations. However, when the Client Server Messaging Security 3.5 Messaging Security Agent has no equivalent configuration settings, it uses the Trend Micro default configurations.
Client Server Messaging Security Installation Overview
Note: Client Server Messaging Security 3.5 will not upgrade Messaging Security Agents that are running on Exchange server 5.5.
Upgrade Effect On Logs and Folders
Upgrading to the Client Server Messaging Security 3.5 Messaging Security Agent has the following effects on logs and folders:
• Logs are retained and can be queried in the upgraded version.
Tip: Before upgrading, check the size of your log files. If the log file is very large, Trend Micro recommends that you run maintenance using your current version before you upgrade. This will greatly reduce the amount of time required for upgrade.
• The quarantine and backup folders are retained during upgrading; however, you will no longer be able to query the quarantined log or resend the quarantined items from the previous version from the Security Dashboard of the upgraded version.
• If the previous version of Client Server Messaging Security used eManager, then Client Server Messaging Security 3.5 retains the anti-spam logs from that version.
Upgrade Effect on Messaging Security Agent Scan Settings
Upgrading to Client Server Messaging Security 3.5 from Client/Server/Messaging Suite 2.0 has the following effects on the Messaging Security Agent scan settings:
Manual Scan – receives Trend Micro default settings
Scheduled Scan – receives Client/Server/Messaging Suite 2.0 Antivirus, Content Filtering, and Attachment Blocking settings
Real-time Scan – Antivirus, Attachment Blocking, Content Filtering, and Anti-spam settings are all migrated from Client/Server/Messaging Suite 2.0.
Upgrade Effect on the Messaging Security Agent Scheduled Scan Tasks
Upgrading to Client Server Messaging Security 3.5 from Client/Server/Messaging Suite 2.0 has the following effects on the Messaging Security Agent Scheduled Scan Tasks:
Only the first Scheduled Scan task from Client/Server/Messaging Suite 2.0 will be migrated to Client Server Messaging Security 3.5, and only if that task was created using the Client/Server/Messaging Suite 2.0 Win32 console.
Upgrade Effect on the Messaging Security Agent Scheduled Scan Enabled/Disabled
If Scheduled Scan is enabled in Client/Server/Messaging Suite 2.0, it will also be enabled in Client Server Messaging Security 3.5. However, only the Antivirus filter will be enabled.
Upgrade Effect on Configurations
Upgrading to Client Server Messaging Security 3.5 has the following effects on old configurations:
• End User Quarantine (EUQ).
The approved sender lists are maintained in the upgraded version.
• eManager.
Previous versions of Client Server Messaging Security used eManager anti-spam rules to block email messages that matched specified keywords. In Client Server Messaging Security 3.5, this function is provided by Content Filtering rules. The anti-spam rule name from the previous version is imported to Client Server Messaging Security 3.5. For detailed information about how Client Server Messaging Security 3.5 upgrades anti-spam rules from eManager see Table 4-3.
TABLE 4-3. Effect of Upgrading eManager Anti-spam Rules
The old anti-spam rule CSM 3.5 imports the rule as a Content Filtering rule
Exactly matching keywords By default, CSM 3.5 uses exact matches on all keywords to filter content.
Partially matching keywords CSM 3.5 uses regular expressions with the specified keywords.
Global exception CSM 3.5 sets the rule to trigger a Pass action so that CSM 3.5 takes no action against messages configured with global exceptions rules. CSM 3.5 assigns this imported rule the lowest rule order number so that it is always filtered first.
Client Server Messaging Security Installation Overview
Client Server Messaging Security 3.5 supports all eManager message blocking actions described in the following table:
TABLE 4-4. Effect of Upgrading eManager Anti-spam Actions
Upgrade Effect on Messaging Security Agent Actions
Actions from previous versions of Client Server Messaging Security 3.5 are changed when you upgrade. Consult the following table for each action.
TABLE 4-5. Effect of Upgrading on Actions
Notifications CSM 3.5 retains the notification settings.
Old anti-spam action Upgraded Content Filtering action Quarantine
Archive
Quarantine Archive
Delete Quarantine
Before Upgrade Action After Upgrade Action
Clean Clean
Quarantine
ScanMail 6.x used Quarantine to move infected messages to a quarantine directory, replace the infected files, and deliver the remaining message to the original recipient.
Quarantine entire message
In Client Server Messaging Security 3.5 Quarantine entire message copies the original infected message into a quarantine folder and does not deliver the message to the original recipient.
After upgrading, the old Quarantine action is replaced with the new Quarantine entire message action.
Delete
ScanMail 6.x used Delete to remove the contents of a message and replace it with a warning text.
Replace with text/file
The behavior of the Replace with text/file action is the same as the behavior of delete in ScanMail 6.x. Client Server Messaging Security 3.5 converts this action to replace with text/file.
Pass Pass
The old anti-spam rule CSM 3.5 imports the rule as a Content Filtering rule