<> Trend Micro Incorporated December 17, 2024 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Trend Micro(TM) ScanMail(TM) for Domino(TM) for AIX(TM) 5.0 64-bit Patch 5 - Build 3800 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: This Readme file was current as of the date above. However, all customers are advised to check Trend Micro's website for documentation updates. GM release documentation: http://docs.trendmicro.com Patch/SP release documentation: http://www.trendmicro.com/download TIP: Register online with Trend Micro within 30 days of installation to continue downloading new pattern files and product updates from the Trend Micro website. Register during installation or online at: https://clp.trendmicro.com/FullRegistration?T=TM Contents ========================================================== 1. About ScanMail for Domino 1.1 Overview of This Release 1.2 Who Should Install This Release 2. What's New 2.1 Enhancements 2.2 Resolved Known Issues 3. Documentation Set 4. System Requirements 5. Installation 5.1 Installing 5.2 Uninstalling 6. Post-Installation Configuration 6.1 Post-Installation Configuration (from Previous Versions) 7. Known Issues 8. Release History 8.1 Patch 1 8.2 Patch 2 8.3 Patch 3 8.4 Patch 4 9. Files Included in This Release 10. Contact Information 11. About Trend Micro 12. License Agreement ========================================================== 1. About ScanMail for Domino ======================================================================== 1.1 Overview of This Release ===================================================================== This Patch consolidates all previous hotfix releases of ScanMail for Domino for AIX 5.0 64-bit. This Patch updates the product name to "ScanMail for Domino". 1.2 Who Should Install This Release ===================================================================== Install this release if you are running ScanMail for Domino for AIX 5.0 64-bit version. Note: Skip this release if you have already installed ScanMail for Domino Service Pack 1. 2. What's New ======================================================================== Note: Install the Patch/SP before completing any procedures in this section (see "Installation"). This Patch addresses the following issues and/or includes the following enhancement(s): 2.1 Enhancements ==================================================================== The following enhancements are included in this release: Enhancement 1: This Patch updates the outdated URLs in the online help. Enhancement 2: This Patch enables users to configure the number of attempts that SMDreal can check the license profile in the updated ScanMail configuration database. This allows SMDreal to retry when the first check attempt is not successful. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 2: To configure the number of attempts allowed for SMDreal to check the license profile: 1. Install this Patch (see "Installation"). 2. Log on to the Domino console and run the following command, replacing "retry_times" with a preferred number of attempts between 0 and 20: set conf SMD_CHECKCONF_RETRY=retry_times NOTES: - If "SMD_CHECKCONF_RETRY" is set to a value below "0" or above "20", the number of attempts is set to "5" by default. - If "SMD_CHECKCONF_RETRY" is not configured, the number of attempts is set to "0" by default. - The retry interval is one (1) minute. 3. Restart SMDreal. Enhancement 3: This Patch uses the communication protocol specified by "SSL_Cipher_List" in Agent.ini for communicating with Apex Central. [Hotfix 3634] Enhancement 4: This Hotfix supports adding groups to the Approved and Blocked Senders lists in anti-spam configuration. Enhancement 5: This Hotfix adds the "Remove All" button for the Approved and Blocked Senders lists in anti-spam configuration. [Hotfix 3632] Enhancement 6: This Hotfix provides the option to update $Domino_data_folder/smdtemp/Agent.ini with "SSL_Cipher_List=TLSv1.2". Notice: 1. The Hotfix adds "SSL_Cipher_List=TLSv1.2" to this Agent.ini file if the parameter does not exist, or updates the value of SSL_Cipher_List to TLSv1.2 if the parameter already exists. 2. Check the details about how to perform the update in "5. Installation". [Hotfix 3599] Enhancement 7: This Hotfix allows users to enable the Database Scan History Deletion feature. [Hotfix 3586] Enhancement 1: Hotfix 3574 replaces VSAPI API (VSDecompress) with AFI, but "Virus Scan" should be enabled for the "Enable attachment filtering by file type" to work. This Hotfix removes this requirement. [Hotfix 3557] Enhancement 1: This Hotfix enables ScanMail for IBM Domino to support the "VSDT_MSI" and "VSDT_LNK" true file types. Enhancement 2: When an email attachment triggers any of the following filters that have been configured to perform the specified actions, the original attachment will be replaced by the configured replaced attachment. - the Virus Scan filter, and the action is configured as "Delete" or "Quarantine" - the Scan Restrictions filter, and the action is configured as "Delete" or "Quarantine" - the Attachment filter, and the action is configured as "Delete attachment" or "Quarantine" - the Content filter, and the action is configured as "Delete attachments" or "Quarantine" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 2: To configure this option: 1. Install this Hotfix (see "Installation"). 2. Open the ScanMail Configuration Database. 3. In the "Configurations > Server Settings > Misc > Customize the replaced attachment file name and content", specify the replaced attachment filename and content. [Hotfix 3496] Enhancement 1: The total size of notification email messages is limited to four kilobytes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 1: To extend the total size limitation for notification email messages to 32 kilobytes: 1. Install this Hotfix (see "Installation"). 2. Open "notes.ini" using a text editor. 3. Add the following hidden key in "notes.ini". SMD_LARGE_NOTIFICATION_CONTENT=1 NOTE: To revert to the old behavior, set its value to "0". 4. Save the changes and close "notes.ini". 5. Restart SMDreal. 2.2 Resolved Known Issues ===================================================================== NOTE: Please install the release before completing any procedures in this section (see "Installation"). This release resolves the following issue(s): Issue 1: A compatibility issue related to HCL Domino 11 in Hotfix B3642 may prevent SMDCM from registering to Apex Central and cause the system to be unresponsive when SMDCM stops. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Patch upgrades AgentSDK to build 5.0.0.2615 to resolve this issue. [Hotfix 3642] Issue 1: A flaw was found in some versions of OpenSSL. It is possible to trigger an infinite loop by crafting a certificate that has invalid elliptic curve parameters. Trend Micro ActiveUpdate and MCP AgentSDK modules used OpenSSL with the flaw. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This hotfix updates the Trend Micro ActiveUpdate and MCP AgentSDK modules to resolve this issue. [Hotfix 3626] Issue 1: The OpenSSL version used by Trend Micro ActiveUpdate has a flaw that can trigger an infinite loop by crafting a certificate that has invalid elliptic curve parameters. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This hotfix updates the Trend Micro ActiveUpdate modules to resolve this issue. Issue 2: After Advanced File Information (AFI) is applied, the Attachment Filter sometimes incorrectly detect the true file type of files extracted from compressed packages as "DOS COM". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: This hotfix resolves the issue. Issue 3: For Virus Scan and Scan Restrictions, when the action is set to "quarantine" and the hidden key "SMDAttQuarMail=1" is set in "notes.ini", the message remains in MAIL.BOX after being quarantined. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 3: This hotfix resolves the issue. [Hotfix 3608] Issue 1: After Hotfix B3574 is applied and under certain conditions, the "X_ATT_NAMETRIGGERFILE" or "X_ATT_TYPETRIGGERFILE" header may remain in database documents. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Hotfix enables ScanMail to remove "X_ATT_NAMETRIGGERFILE" and "X_ATT_TYPETRIGGERFILE" headers from database documents. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 1: To enable ScanMail to remove "X_ATT_NAMETRIGGERFILE" and "X_ATT_TYPETRIGGERFILE" headers from database documents: 1. Install this Hotfix (see "Installation"). 2. Open "notes.ini" using a text editor. 3. Add the following hidden key. SMDAttHeadRemove=1 4. Save the changes and close the file. 5. Run a manual database scan specifying the target database in "ScanMail Configuration console > Actions > Manual scan > Databases to scan > Specify database" and clicking "Save > Scan Now". 6. Check whether the "X_ATT_NAMETRIGGERFILE" and "X_ATT_TYPETRIGGERFILE" headers exist on the database. [Hotfix 3604] Issue 1: The Spam stamp is not added to the subject header of an email message that triggered the Spam filter and is quarantined to the Quarantine Database. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Hotfix updates the quarantine process to ensure that the Spam stamp is added to the subject prefix of these email messages. [Hotfix 3603] Issue 1: Multiple Spam headers may display under the Spam Details column of scan logs. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Hotfix updates the initialization process to ensure that Spam headers display correctly in scan logs. [Hotfix 3586] Issue 1: The database design cannot be updated if the build number of "smmsg.nsf" is higher than the hotfix to be installed. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Hotfix resolves this issue. [Hotfix 3574] Issue 1: When "SMDAttQuarMail=1" is set in "notes.ini" and the "virus scan" filter (that contains a "Scan Restriction") is triggered, the "final action" in notifications always appear as "Quarantined" even when the "Final Action" setting is set to a different action. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Hotfix updates the ScanMail program to ensure that the correct "Final Action" appears in notifications. Issue 2: The VSAPI/ATSE API (VSDecompress) is affected by a potential vulnerability. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: This Hotfix replaces VSAPI/ATSE API (VSDecompress) with AFI. [Hotfix 3552] Issue 1: A directory traversal vulnerability occurs when ScanMail downloads engine files or pattern files from the local ActiveUpdate (AU) server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Hotfix updates the Trend Micro ActiveUpdate module to prevent the vulnerability. [Hotfix 3509] Issue 1: An email in rich text format will lose its mail history content if it meets the following two conditions: * the "SMD_SPLITMAIL_RECALL_ENABLED" hidden key is enabled * the email partially matches a ScanMail rule ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This hotfix resolves the issue by enabling ScanMail to open mail notes using the "OPEN_RAW_MIME" parameter. [Hotfix 3485] Issue 1: ScanMail does not replace the notification mail text with the text from the "Internal recipients" notification field of the triggered filter when the size of the text exceeds 1024 bytes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This hotfix resolves the issue by enabling the notification field of each filter to support up to 4095 bytes of text. [CP 3573] Issue 1: In certain environments, an issue prevents ScanMail for IBM Domino 5.0 for AIX from checking digital signatures successfully during an engine or pattern update. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: This Critical Patch updates the AU module to resolve this issue. 3. Documentation Set ======================================================================== To download or view electronic versions of the documentation set for this product, go to http://docs.trendmicro.com In addition to this Readme file, the documentation set for this product includes the following: - Online Help: The Online Help contains an overview of features and key concepts, and information on configuring and maintaining . To access the Online Help, go to http://docs.trendmicro.com - Installation Guide (IG): The Installation Guide contains information on requirements and procedures for installing and deploying . - Administrator's Guide (AG): The Administrator's Guide contains an overview of features and key concepts, and information on configuring and maintaining . - Getting Started Guide (GSG): The Getting Started Guide contains product overview, installation planning, installation and configuration instructions, and basic information intended to get "up and running". - Support Portal: The Support Portal contains information on troubleshooting and resolving known issues. To access the Support Portal, go to http://esupport.trendmicro.com 4. System Requirements ======================================================================== Install this Patch only on machines running ScanMail for Domino for AIX 5.0 64-bit. Note: Skip this Patch if you have already installed ScanMail for Domino Service Pack 1. ScanMail for Domino requires the following hardware and software specifications on the servers where it is installed: - Lotus(TM) Domino(TM) R8.0.1/R8.0.2/R8.5/R8.5.1/R8.5.2 64-bit - IBM(TM) Domino(TM) 9.0, 9.0.1 64-bit - HCL(TM) Domino(TM) 11.0, 11.0.1, 12.0.1, 12.0.2, 14.0 64-bit - IBM AIX 5.3 (64-bit kernel), minimum patch level of TL7, 0815 (5300-07-04-0815) - IBM AIX 6.1 (64-bit kernel), Service Pack 4, APAR IZ10223, APAR IZ09961, APAR IZ10284, APAR IZ08022 - IBM AIX 7.1 (64-bit kernel), 7.2 (64-bit kernel), 7.2 service pack numbers 7200-05-03-2148 - Power4 and higher processor - 1-GB Memory - 500-MB available disk space for program files, 100-MB available disk space on each partition, 400-MB available disk space for /tmp file system - Internet access (for components download) 5. Installation ======================================================================== This section explains key steps for installing ScanMail for Domino. Refer to the "Administrator's Guide" for detailed information. 5.1 Installing ===================================================================== To install the Patch and update $Domino_data_folder/smdtemp/Agent.ini with "SSL_Cipher_List=TLSv1.2": 1. Copy the "smd_50_aix64_en_patch5_b3800.tar.gz" installation file to a local folder. 2. Extract the contents of the installation file to a local folder by running the following commands: gunzip smd_50_aix64_en_patch5_b3800.tar.gz tar -vxf smd_50_aix64_en_patch5_b3800.tar 3. Go to the "smd_50_aix64_en_patch5_b3800" folder. 4. Run the following command: ./UPDSilent /ua To install the Patch without updating $Domino_data_folder/smdtemp/Agent.ini: 1. Copy the "smd_50_aix64_en_patch5_b3800.tar.gz" installation file to a local folder. 2. Extract the contents of the installation file to a local folder by running the following commands: gunzip smd_50_aix64_en_patch5_b3800.tar.gz tar -vxf smd_50_aix64_en_patch5_b3800.tar 3. Go to the "smd_50_aix64_en_patch5_b3800" folder. 4. Run the following command: ./UPDSilent 5.2 Uninstalling ======================================================= To roll back to the previous build: 1. Go to the "$SMLD_Binary_Folder/hotfix" directory. 2. Run the following command ./UPDSilent /u B3800 6. Post-Installation Configuration ======================================================================== No post-installation steps are required. Note: Trend Micro recommends that you update your scan engine and virus pattern files immediately after installing this Patch. 7. Known Issues ======================================================================== There are no known issues in this release. 8. Release History ======================================================================== For more information about updates to this product, go to: http://www.trendmicro.com/download 8.1 Patch 1 ==================================================================== 8.1.1 Enhancements ==================================================================== ScanMail for Domino for AIX 5.0 Patch 1 contains the following enhancements: Enhancement 1: Filter Customization, Actions, and Notifications - Users can now customize filters, the corresponding actions, and notifications for specific email messages. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 1: To customize filters, actions, and/or notifications for specific email messages, perform the applicable steps listed below: a. Open the "notes.ini" file using a text editor. b. Enable the feature by adding the following hidden key and setting its value to "1": Enable_SMLD_Customize_Action=1 Note: By default this key is disabled and is set to "0". To disable, re-set its value to "0". c. Set the number of customized rules by adding the following hidden key and setting an appropriate value: Customized_SMLD_Rule_Number=x Where "x" is the number of customized rules that you are going to create. d. Define the customized rules by adding the following hidden key/s and setting the appropriate value/s: Customized_SMLD_Rule1=rule1 Customized_SMLD_Rule2=rule2 Notes: - The number following "Customized_SMLD_Rule" should always begin with "1". For example: Customized_SMLD_Rule1=Exist(&FieldName) AND Content(&FieldName)="XXX" AND Content(&FieldName) Like "*@YYY" Action(Q,N1) - Literal strings have to be enclosed by double quotation marks (""). The string after "=" is case-sensitive while the string after "Like" is case-insensitive. - Functions, operators, and keyword names are case-insensitive. - "Exist" is a function that checks whether a corresponding field exists or not while "Content" is a function that returns the value of a corresponding field - "=" is an "equal" operator, which means precise string match while "Like" is an operator which means wild string match and currently only supports the asterisk (*) operator. - The "=" and "Like" functions do not work on non-text fields (fields that are not of the "TEXT" type). - "AND" is a keyword. The current version only supports the "AND" relationship. - "Action" is a keyword, which means if the rule is triggered, the following corresponding actions will be taken. - "B" means "Block" - "Q" means "Quarantine" - "N" means "Notification", the number following "N" means the notification template index - "F" means "Redirect mail to approver". For example: Action(B,N1,N2) means block and use notification template 1 and template 2. Actions can be combined according to the following rules: - If the "Block", "Quarantine", and "Forward" actions are set, only the "Block" action takes effect. - If the "Quarantine" and "Forward" actions are set, only the "Quarantine" action takes effect. - If the "Block" and "Forward" actions are set, only the "Block" action takes effect. e. Set the number of notification templates by adding the following hidden key and setting an appropriate value: Customized_SMLD_Notification_Number=y Where "y" is the number of customized templates. f. Define the customized notification templates: i. Add the following hidden key/s and set the value/s to the email address of receiver or group: Customized_SMLD_Notification_To1=emailaddress1 Customized_SMLD_Notification_To2=emailaddress2 Notes: - The number following "Customized_SMLD_Notification_To" should begin with "1". - For multiple receivers, use a semicolon (;) or comma (,) to separate each email address. For example: Customized_SMLD_Notification_To1=admin/ company or Customized_SMLD_Notification_To1= admin@domain.com ii. Add the following hidden key/s and set the appropriate value/s: Customized_SMLD_Notification_Subject1=subject1 Customized_SMLD_Notification_Subject2=subject2 Note: The number following "Customized_SMLD_Notification_Subject" should begin with "1". For example: Customized_SMLD_Notification_Subject1= ScanMail Notification iii. Add the following hidden key/s and set the appropriate value/s: Customized_SMLD_Notification_Body1=body1 Customized_SMLD_Notification_Body2=body2 Notes: - The number following "Customized_SMLD_Notification_Body" should begin with "1". - You must enter the parameters of the body on the same line with the line break symbol "\r\n". For example: customized_SMLD_Notification_Body1= At %SCAN_TIME%, on server %SERVER%:\r\n The message from %SENDER% to %RECIPIENTS% is filtered by %MATCHING_FILTER%,rule number: %RULENUMBER%,Take action: %FINAL_ACTION%.\r\n SMLD %PRODUCTVERSION%, Pattern %PATTERNVERSION%, engine %SCANENGINEVERSION%. g. Redirect email messages to customized email addresses by adding the following hidden key and setting its value to the email addresses of approvers separating multiple email addresses using a semicolon (;) or a comma (,). Customized_SMLD_Forward_Address=email1,email2,... h. Customize the subject of redirected email messages by adding the following hidden keys and setting the appropriate values: Customized_SMLD_Approved_Reason=reason for approval Customized_SMLD_Rejected_Reason=reason for rejection For example: Customized_SMLD_Approved_Reason=The mail has been approved by %APPROVER%. Customized_SMLD_Rejected_Reason=The mail has been Rejected and not delivered to the recipients. i. Run the following commands in the Domino console to restart SMDreal. >tell smdreal q >load smdreal Notes: - Because there is a 256-byte limit for "notes.ini" entries, the length of value for the hidden keys specified above cannot exceed this limit. - The current version does not support fields with the same field names which means that when the first field triggers the rule, the second field with the same name will not be scanned. Enhancement 2: Sending Logs to the Control Manager Server - Users can now set a time limit for ScanMail for Lotus Domino for AIX 5.0 to send logs for malicious email contents to the Control Manager server after generating the logs. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 2: To set a time limit for ScanMail for Domino for AIX 5.0 to send logs for malicious email contents to the Control Manager server after generating the logs:. a. Open "notes.ini" using a text editor. b. Add the "SMDCMLogInterval" hidden key to "notes.ini" and set its value to the preferred interval period in seconds. You can set this value between 1 and 3600. c. Save the changes and close "notes.ini". d. Run the following command in the Domino console to restart "SMDcm". >tell smdcm q >load smdcm Enhancement 3: Quarantined Email Messages - Users can now prevent ScanMail for Domino for AIX from scanning email messages that were resent from the quarantine database after the email message triggers a Scan Restriction. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 3: To prevent ScanMail for Domino for AIX from scanning email messages that were resent from the quarantine database after the email message triggers a Scan Restriction. a. Open "notes.ini" using a text editor. b. Add the "BYPASS_RESEND_UNSCANNABLE_ATTACHMENT" key and set its value to "1". c. Save the changes and close "notes.ini". d. Run the following commands in the Domino console to restart SMDreal. >tell smdreal q >load smdreal Enhancement 4: Log Generation - An archived file may contain several archived files with the same file name but in different archive levels. When the archived files with the same file name trigger the "Exceed maximum compression level" rule under the ScanMail for Domino for AIX configuration database, several log entries with the same file name are generated in the ScanMail for Domino log database and notification mail. Users can now prevent the generation of multiple log entries with the same file name in the ScanMail for Lotus Domino for AIX log database and notification mail in this situation. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 4: To prevent the generation of multiple log entries with the same file name in the ScanMail for Lotus Domino for AIX log database and notification mail: a. Open "notes.ini" using a text editor. b. Add the "SMLD_SUPPRESS_DUPLICATE_LOG" hidden key and set its value to "1". c. Save the changes and close "notes.ini". d. Run the following commands in the Domino console to restart SMDreal. >tell smdreal q >load smdreal 8.1.2 Resolved Known Issues ==================================================================== ScanMail for Domino for AIX 5.0 Patch 1 resolves the following issues: Issue 1: ScanMail for Domino for AIX debug logs may occupy a large amount of disk space after the Domino server stops unexpectedly. This issue occurs because the ScanMail for Domino for AIX debug log is enabled automatically after the Domino server recovers from stopping unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: The ScanMail for Domino for AIX debug log is no longer enabled automatically after the Domino server recovers from stopping unexpectedly. This is the default behavior, however users can still set it to the original behavior. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 1: To set ScanMail for Domino for AIX debug log to be automatically enabled after the Domino server recovers from stopping unexpectedly, perform any of the following procedures: Option 1: a. Open the "notes.ini" file using a text editor. b. Add the following key and set its value to "1". SMDAutoDebug=1 c. Save the changes and close the file. d. Run the following commands in the Domino console to restart SMDreal. >tell smdreal q >load smdreal Option 2: a. Open a Domino console. b. Run the following command: set configuration SMDAutoDebug =1 Issue 2: An issue in the TmMsg module can cause the ScanMail for Lotus Domino for AIX server to stop unexpectedly while running a manual scan on the database. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: The TmMsg module has been updated to resolve the issue and enable the module to run manual scans on the database successfully. Issue 3: An issue in the MCP Agent module prevents ScanMail for Lotus Domino for AIX from sending complete log information to the Control Manager server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 3: The MCP Agent module has been updated to resolve the issue and ensure that ScanMail for Domino for AIX always sends the complete log information to Control Manager. Issue 4: ScanMail for Domino for AIX searches for recipient email addresses by "Full name then local part" even after users set it to scan by "fullname only" in the Domino "SMTP configuration settings" page. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 4: ScanMail for Domino for AIX now checks the Domino SMTP configuration settings for recipient email addresses to enable it to search according to the correct settings. 8.2 Patch 2 =================================================================== 8.2.1 Enhancements ==================================================================== ScanMail for Domino for AIX 5.0 Patch 2 adds the following enhancements: Enhancement 1: Domino Platform Support - ScanMail for Domino for AIX 5.0 now supports version 9 of the Domino platform. Enhancement 2: Quarantined Email Messages - A "Forward" button has been added to enable users to forward quarantined email messages to specific email addresses. ScanMail for Domino for AIX no longer scans these email messages which ensures that these can be forwarded without triggering an alarm. Note: Use a comma to separate multiple email addresses. 8.2.2 Resolved Known Issues ==================================================================== ScanMail for Domino for AIX 5.0 Patch 2 resolves the following issues: Issue 1: When the Virus Scan "Action on cleanable virus" setting of Real-time Mail Scanning is set to "Quarantine", the "BYPASS_RESEND_UNSCANNABLE_ATTACHMENT" key in "notes.ini" does not work when enabled. The key should prevent ScanMail for Domino for AIX from scanning email messages that were resent from the quarantine database after being filtered by a Scan Restriction. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: [Hotfix 3131] The "BYPASS_RESEND_UNSCANNABLE_ATTACHMENT" key now works normally when the Virus Scan "Action on cleanable virus" setting is set to "Quarantine". Issue 2: An issue in the eManager common module may cause the ScanMail for Domino "CVsapiWrapper" function to stop unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: [Hotfix 3134] The eManager common module has been upgraded to prevent the "CVsapiWrapper" function from stopping unexpectedly. Issue 3: When ScanMail for Domino for AIX runs any eManager version from 6.7.0.1057 or above, the Content Filter may cause the Domino Server or the SMDReal process to stop responding while ScanMail for Lotus Domino for AIX shuts down or restarts. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 3: [Hotfix 3147] ScanMail for Domino for AIX can now successfully shut down and restart while running any eManager version. Issue 4: When the "Macros in Microsoft Office files" option under "Advanced Options" is enabled, ScanMail for Lotus Domino for AIX treats clean macro files as virus detections. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 4: [Hotfix 3159] ScanMail for Domino for AIX no longer handles clean macro files when the "Macros in Microsoft Office files" option is enabled. In addition, this hot fix sets the heuristic level during macro file scans but this does not affect ScanMail for Lotus Domino for AIX's ability to detect macro files that contain viruses. Note: "SMLD_HEURISTIC_LEVEL" can function when ScanMail for Domino for AIX does not handle clean macro files. Setting the value of "SMLD_HEURISTIC_LEVEL" to "4" generates the maximum number of false positives. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 4: To prevent ScanMail for Domino for AIX from handling clean macro files when "Macros in Microsoft Office files" is selected: a. Open "notes.ini" using a text editor. b. Add the "SMLD_DISABLE_STRIP_MACRO" parameter to "notes.ini" and set its value to "1". c. Save the changes and close "notes.ini". To set the heuristic level during macro file scans: a. Open "notes.ini" using a text editor. b. Add the "SMLD_HEURISTIC_LEVEL" parameter to "notes.ini" and set its value. The value can be from 1 to 4, and the default value is 2. c. Save the changes and close "notes.ini". Issue 5: SMDreal processes may stop unexpectedly during pattern updates. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 5: [Hotfix 3163] Users can now enable ScanMail for Domino for AIX 5.0 to automatically restart all SMDreal processes after a pattern update in normal and debug modes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 5: To enable ScanMail for Domino for AIX 5.0 to automatically restart all SMDreal processes after a pattern update in normal mode: a. Open "notes.ini" using a text editor. b. Add the "SMD_UPD_START_NEW_SCANNER" parameter to "notes.ini" and set its value to "1". Note: To disable this option, set "SMD_UPD_START_NEW_SCANNER=0" c. Save the changes and close "notes.ini". To enable ScanMail for Domino for AIX 5.0 to restart all SMDreal processes after a pattern update in debug mode: a. Open "notes.ini" using a text editor. b. Add the "SMDRTSCANDEBUG" parameter to "notes.ini" and set its value to "1". Note: To disable this option, set "SMDRTSCANDEBUG=0" c. Save the changes and close "notes.ini". 8.3 Patch 3 =================================================================== 8.3.1 Enhancements ==================================================================== The following enhancements are included in this release: Enhancement 1: [Hotfix 3210] Quarantined Email Messages - This Patch enables ScanMail for Domino for AIX 5.0 to pack all attachments into the "TM_Sample_with_pwd[trendsmd].zip" file and protect the file using "trendsmd" as the password when forwarding quarantined email messages to specific email addresses. This can prevent the attachments from triggering other antivirus products. Enhancement 2: [Hotfix 3278] Scheduled Database Scans - This Patch enables the scheduled database scan function to allow users to create a rule for a special server or a list of special servers. Enhancement 3: [Hotfix 3298] Temporary Folder Cleanup - This Patch enables ScanMail for Domino for AIX 5.0 to promptly delete files that are older than 12 hours from the temporary folder. This can help prevent files that may have been left in the folder after the Domino Server stops unexpectedly, from causing issues. Enhancement 4: Scan Macro Settings - This Patch adds the following reminder for the macro settings of real-time email scans, real-time database scans, scheduled database scans, and manual database scans on the configuration database. "This setting will apply to all Microsoft Office files containing macros, even if they are not malicious." Enhancement 5: [Hotfix 3130] Install Log File - After installing this Patch, the install log file "updsmd_xxxx.dbg" will no longer be generated by default after a patch or a hot fix is installed. Users can configure ScanMail for Lotus Domino for AIX to generate the file and save it in the "$domino_data_folder\smdtemp\" folder instead of in the "\var\log" folder. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 5: To enable ScanMail for Domino to automatically generate the "updsmd_xxxx.dbg" file in the "$domino_data_folder\smdtemp\" folder: a. Install this Patch (see "Installation"). b. Add the "SMD_ENABLE_SMENCY_LOG" hidden key in the "notes.ini" file and set its value to "1". c. Save the changes and close the file. d. Restart "SMDreal". Enhancement 6: TMASE Engine - This Patch allows users to enable the TMASE engine logging function. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 6: To enable TMASE engine logging function: a. Install this Patch (see "Installation"). b. Add the "SMDSPAMLog" hidden key in the "notes.ini" file and set its value to "1". c. Save the changes and close the file. d. Restart "SMDreal". Enhancement 7: API for Extracting and Passing Headers/Entities - This Patch enables ScanMail for Domino for AIX to use an SMTP style API instead of the Notes format API to extract and pass all headers/entities to TMASE, which can enhance the anti-spam efficiency. Enhancement 8: [Hotfix 3062] Virus Filter - This hot fix enables users to set ScanMail for Domino for AIX to quarantine entire email messages instead of only the attachments when email messages trigger the content, attachment, or virus filter's "Quarantine" action. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 8: To enable ScanMail for Domino for AIX to quarantine entire email messages instead of only the attachment when such email messages trigger a content filter: a. Install this Patch (see "Installation"). b. Open "notes.ini" using a text editor. c. Add the "SMDAttQuarMail" hidden key to "notes.ini" and set its value to "1". d. Save the changes and close the file. e. Restart "SMDreal". 8.3.2 Resolved Known Issues ==================================================================== The following known issues are resolved in this release: Issue 1: Sometimes, ScanMail for Domino cannot register to a Trend Micro Control Manager(TM) 6.0 server through HTTPS. This happens because some OpenSSL modules in the MCPAgentSDK common module do not support the TLSv1.1 protocol. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: [Hotfix 3194] This hot fix enables the MCPAgentSDK common module to use the TLSv1.0 protocol only. This ensures that ScanMail for Domino can register to Control Manager 6.0 servers through HTTPS. Issue 2: ScanMail for Domino refreshes all policies every minute. As a result, it could use up almost half of the CPU resources when there is a large number of policies in "smconf.nsf". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: [Hotfix 3230] This hot fix enables ScanMail for Domino to refresh only those policies that have changed since the last refresh task instead of refreshing all policies every minute. This can help minimize its usage of CPU resources. Issue 3: A memory issue in the CMAgent module can trigger the SMDcm process to stop unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 3: [Hotfix 3240 and 3310] These hot fixes update the CMAgent module to resolve the memory issue and prevent it from triggering the SMDcm process to stop unexpectedly. Issue 4: ScanMail for Domino may not be able to download new pattern or scan engine files from the Trend Micro official update source. This happens because the ScanMail for Domino Automatic Update (AU) module is using an old digital certificate while downloading pattern updates which prevents the AU module from passing the integrity check for the update. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 4: [Critical Patch 3274] This critical patch resolves this issue by replacing the expired certification database file with the latest one. Issue 5: When scan restrictions are enabled and ScanMail encounters a "multiple same compressed files inside one compressed file" condition, it triggers the action set for the "Unknown reason(s) why attachments could not be scanned" option. This occurs even when the triggering compressed file has reached the "Exceed Maximum Compression Level" setting in the "Scan Restriction" tab. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 5: [Hotfix 3322] This hot fix ensures that "the multiple same compressed files inside one compressed file" condition does not trigger actions set for the "Unknown reason(s) why attachments could not be scanned" condition when users enable "Scan Restriction" settings for mail scans and database scans. Issue 6: If the spam score of a message is higher than or equal to the threshold, the message should be classified as spam. However, ScanMail for Lotus Domino for AIX classifies the message as spam only when the spam score is higher than the threshold. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 6: This Patch enables ScanMail for Domino for AIX to classify a message as spam when the spam score of the message is equal to or higher than the threshold. SBM253791 no Hot Fix Issue 7: The Domino server stops unexpectedly while ScanMail for Lotus Domino for AIX calls a Domino API to check the digital signature of MIME-encoded email messages. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 7: This Patch prevents ScanMail for Domino for AIX from checking the digital signature of MIME-encoded email messages. Issue 8: The "Download components for AIX 64-bit" function does not work in ScanMail for Domino for AIX. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 8: This Patch enables ScanMail for Domino for AIX to support the "Download components for AIX 64-bit" function. Issue 9: ScanMail for Domino for AIX cannot display the version number of the VSAPI pattern. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 9: This Patch enables ScanMail for Domino for AIX to display the VSAPI pattern version in the right format. Issue 10: The ActiveUpdate root certificate in the current ActiveUpdate module is out-of-date. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 10: This Patch updates the ActiveUpdate module to the latest build. Issue 11: The user's firewall policy blocks HTTP requests for online updates of the Product Registration module because the default content of the "User-Agent string" in these HTTP requests includes "Windows 98". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 11: [Hotfix 3081] This hot fix updates the Product Registration module and sets the default value of the "User-Agent" string of HTTP requests for Product Registration module online updates to the following: "Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; Media Center PC 4.0; SLCC1; .NET CLR 3.0.04320)" Users can also customize the default "User-Agent" string through the following procedure. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 11: To customize the default "User-Agent string" of HTTP requests for Product Registration module online updates: a. Install this Patch (see "Installation"). b. Open the "notes.ini" file using a text editor. c. Add the "PrUserAgent" key and set its value to the preferred default "User-Agent" string. d. Restart the task "SMDreal". Issue 12: When ScanMail for Domino for AIX detects more than five viruses in an email attachment, it cleans only the first five viruses and delivers the email message with the rest of the viruses. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 12: [Critical Patch 3203] This critical patch enables ScanMail for Lotus Domino for AIX to remove the attachment from the email message before sending the message if it detects more than five viruses in the attachment. In addition, ScanMail for Domino for AIX will keep a copy of the email message in the Quarantine database. Issue 13: When Control Manager notifies ScanMail for Lotus Domino for AIX to update its pattern files and it already has the latest pattern files, the corresponding "command detail" field in the Control Manager console displays "failed". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 13: [Hotfix 3042] After installing this hot fix, ScanMail for Lotus Domino for AIX no longer responds with a "failed" status under this situation to ensure that Control Manager displays the correct command status. Issue 14: Control Manager cannot send notification email messages because ScanMail for Domino for AIX 5.0 does not send event logs to the Control Manager server and Control Manager sends out notifications based on event logs. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 14: [Hotfix 3084] After installing this hot fix , ScanMail for Lotus Domino for AIX sends event logs to the Control Manager server after VSAPI engine and pattern updates which enables Control Manager to send out the corresponding notifications. Issue 15: Since a user's important files are stored in the "\log" folder, and this folder is also used by the CMAgent common module, the CMAgent may delete some of these important files when it stops. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 15: [Hotfix 3126] This hot fix transfers the following four folders used by CMAgent to the "\smdtemp" folder to prevent ScanMail for Domino for AIX from deleting important user files from the "log" folder by accident. - journal - command - log - offhour Issue 16: Database scans stop unexpectedly when the string containing the list of all database names in the database list with absolute paths exceeds 511 bytes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 16: [Hotfix 3153] This hot fix removes the length limit on the string to ensure that database scans can run successfully. Issue 17: ScanMail for Domino for AIX 5.0 cannot run a manual scan on the Lotus Quickr database because it uses the SMTP format to scan. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 17: [Hotfix 3177] This hot fix enables ScanMail for Domino for AIX 5.0 to use the Lotus Notes(TM) format instead of the SMTP format to scan the Lotus Quickr database. This ensures that ScanMail for Domino for AIX 5.0 can successfully scan the Lotus Quickr database. Issue 18: When users enable the "enable attachment filtering by file type" option under the attachment filter settings and select the "Executables" category, the attachment filter also filters out some VDX file attachments. VDX files are files created using the Microsoft(TM) Visio(TM) software. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 18: [Hotfix 3192] This hot fix modifies the "smftypes.nsf" file in the database to transfer all six subtypes of the "VBScript/HTML/JavaScript" file type, including VDX files, from the "Executables" category to the "Other" category. This ensures that VDX file attachments are not filtered out when users select the "Executables" category under the "enable attachment filtering by file type" option of the attachment filter. Issue 19: Domino 8.5.3 servers and higher Domino server versions stop unexpectedly whenever any Domino task closes abnormally. When the ScanMail for Domino for AIX "SMDreal" task closes unexpectedly, it could also cause Domino 8.5.3 servers to stop unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 19: [Hotfix 3221] This hot fix improves the attachment filter initialization process to make scan threads more stable. This can help prevent the "SMDreal" task from closing unexpectedly and causing the Domino server to stop unexpectedly. Issue 20: When users collect logs using the "load SMDsupp" command, the logs are first collected in the "smdtemp" folder and then compressed into a ZIP file. However, the logs remain in the "smdtemp" folder after ScanMail for Domino for AIX 5.0 has successfully compressed the logs into a ZIP file. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 20: [Hotfix 3247] This hot fix enables ScanMail for Domino for AIX 5.0 to delete the logs from the "smdtemp" folder after it has successfully compressed the logs into a ZIP file. Issue 21: An "Invalid universal ID" error message appears when users attempt to add an existing keyword to a content filter. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 21: [Hotfix 3250] This hot fix enables ScanMail for Domino for AIX 5.0 to successfully add existing keywords to any content filter. Issue 22: Notification email messages get stuck in "mail1.box" when "Mail_Enable_Mailbox_Compatibility=1" is set in "notes.ini". This occurs because ScanMail for Lotus Domino for AIX 5.0 uses "mail1.box" by default to send notification email messages when Domino has several mail boxes, and when "Mail_Enable_Mailbox_Compatibility" is set to "1", "mail1.box" will not be initialized. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 22: [Hotfix 3256] This hot fix enables ScanMail for Domino for AIX 5.0 to send notification email messages successfully regardless of whether the "Mail_Enable_Mailbox_Compatibility" parameter is set in "notes.ini" or not. Issue 23: ScanMail for Domino 5.0 prioritizes the spam filter's "Blocked Senders List" over the "Approved Senders List" while ScanMail for Domino 3.0 prioritizes the "Approved Senders List" over the "Blocked Senders List". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 23: [Hotfix 3277] This hot fix enables users to configure ScanMail for Lotus Domino for AIX 5.0 to prioritize the spam filter's "Approved Senders List" over the "Blocked Senders List". However, ScanMail for Domino 5.0 will still prioritize the spam filter's "Blocked Senders List" over the "Approved Senders List" by default. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 23: To enable ScanMail for Domino for AIX 5.0 to prioritize the spam filter's "Approved Senders List" over the "Blocked Senders List": a. Install this Patch (see "Installation"). b. Open the Lotus Domino console. c. Run the "set config SMLD_APPROVED_SENDER_FIRST=1" command. Issue 24: Sometimes, an incremental TMASE pattern update fails because the local TMASE pattern file disappears from the "\smdtemp\au\pattern\tmase" directory or becomes corrupted. When this happens, "SMDreal" will not be able to load the TMASE pattern. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 24: [Hotfix 3284] This hot fix enables ScanMail for Domino for AIX 5.0 to use the old TMASE pattern file in its binary folder if "SMDreal" cannot load the latest TMASE pattern version. When this happens, ScanMail for Lotus Domino for AIX 5.0 automatically deletes the TMASE pattern version from "smency.nsf" and the TMASE pattern file from the "\smdtemp\au\pattern\tmase" folder to trigger a full pattern update on the next TMASE pattern update. Issue 25: ScanMail for Domino for AIX may use up all available CPU resources when multiple "SMDreal" processes run at the same time. This issue more likely affects 32-bit AIX systems running on computers with a single CPU. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 25: [Hotfix 3285] This hot fix prevents multiple "SMDreal" processes from using all available CPU resources when these processes are running at the same time. Issue 26: After users migrate ScanMail for Domino for AIX from one Control Manager server to another using the "AgentMigrateTool.exe" tool, the Control Manager server information in the default CMAgent setting of the ScanMail Configuration Database does not update automatically. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 26: [Hotfix 3308] This hot fix ensures that the Control Manager server information in the default CMAgent setting is updated promptly after the "AgentMigrateTool.exe" tool migrates ScanMail for Domino for AIX to another Control Manager server. Issue 27: ScanMail for Domino for AIX tasks can stop responding during startup. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 27: [Hotfix 3024] This hot fix ensures that ScanMail for Domino for AIX tasks no longer stop responding during startup. Issue 28: "SMDreal" stops unexpectedly whenever ScanMail for Lotus Domino for AIX scans a large email with a C++ runtime exception error in the call stack. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 28: [Hotfix 3025] This hot fix updates the code for handling attachments in situations where there is not enough memory to allot for the task to prevent "SMDreal" from stopping unexpectedly under this situation. Issue 29: The approved and blocked sender's list does not work on certain email messages that contain "TEXT" data instead of RFC text in the "From" field. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 29: [Hotfix 3028] This hot fix enables ScanMail for Domino for AIX to retrieve the "TEXT" type of the sender's address in email messages, which ensures that the approved and blocked sender's lists work on these email messages. Issue 30: Sometimes, "SMDreal" tasks do not restart automatically after a pattern file update on a multiply-partitioned Domino environment. This issue occurs because the fixed timeout value for "SMDreal" tasks is 300 seconds only and may be too short. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 30: [Hotfix 3050] This hot fix enables "SMDreal" to simultaneously load pattern files on multiple partitions with read/write locks and extends the timeout value for "SMDreal" tasks. Issue 31: "SMDreal" tasks stop unexpectedly while the eManager(TM) module allocates memory. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 31: [Hotfix 3051] This hot fix updates the eManager module to fix a memory allocation issue that causes unexpected results when handling a specific sample that is over 83MB in size. Note: If you are running any eManager version after version 6.7.0.1042, you must install Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update and promptly restart your computer before the changes can take effect. Issue 32: A missing field in the CMAgent update document causes the SMDupd task to stop unexpectedly while performing engine updates from the Control Manager server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 32: [Hotfix 3052] This hot fix enables SMDupd to check if the "OS" field is missing from the CMAgent update document while loading SMDupd to prevent SMDupd from stopping unexpectedly. Issue 33: Duplicate CMAgent settings documents cannot be deleted because these documents are default policy. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 33: [Hotfix 3066] This hot fix enables ScanMail for Domino for AIX to check all CMAgent settings documents and the "default policy" setting according to the document IDs. This ensures that the default CMAgent settings are unique. Issue 34: Some email messages that are resent from the quarantine folder have the same Message ID as the original email messages. This causes some third-party applications to treat such email messages as spam. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 34: [Hotfix 3067] This hot fix enables users to change the Message ID of email messages that are re-sent from the quarantine database. Issue 35: "SMDreal" closes unexpectedly if it cannot load the engine or pattern file. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 35: [Hotfix 3095] This hot fix enables SMDmon to monitor the status of "SMDreal" processes and to load another "SMDreal" process if the first "SMDreal" process closes unexpectedly while loading the engine or pattern file. Note: The "SMDreal" debug log is automatically enabled when SMDmon loads the "SMDreal" process. Issue 36: The following error message appears when users run the agent "Delete log files (Auto)" function on the ScanMail Quarantine Database and the number of documents in the database exceeds 32767: "AMgr: Agent ('Delete log files (Auto)' in 'smd\smquar.nsf') error message: Overflow." ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 36: [Hotfix 3121] The maximum number of documents that the agent "Delete log files (Auto)" function can delete from the ScanMail Quarantine Database in a single run has been raised. Issue 37: When users set ScanMail for Domino for AIX to quarantine entire email messages instead of only the attachments when email messages trigger the virus filter's "Quarantine" action by "SMDAttQuarMail" hidden key, the virus filter quarantines the entire email message as expected. However, the corresponding notification states that the action performed on the entire email message is "Deliver" instead of "Quarantine". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 37: [Hotfix 3127] This hot fix ensures that the virus filter notification correctly indicates that the action taken for the entire email message in this case is "Quarantine". Issue 38: Office 2007 files belong to a special type of compressed files. ScanMail for Domino for AIX blocks compressed Office 2007 files that contain any file that is in the blocked attachments list of attachment filters. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 38: [Hotfix 3129] This hot fix enables ScanMail for Domino for AIX to skip compressed files during scans if the file type is Office 2007. Issue 39: Office 2007 files belong to a special type of compressed files. ScanMail for Domino for AIX blocks compressed Office 2007 files that contain any file that is in the blocked attachments list of attachment filters. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 39: [Hotfix 3133] ScanMail for Domino no longer scans compressed files that contain only Office 2007 files with any of the following extension names which are also in the blocked attachments list of attachment filters: - *.docm - *.docx - *.dotm - *.dotx - *.potm - *.potx - *.pptm - *.xlam - *.xlsb - *.xlsm - *.xlsx - *.xltm - *.xltx Issue 40: ScanMail for Domino for AIX may stop unexpectedly while scanning an email message if Domino perceives the size of the attachment to be "-1". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 40: [Hotfix 3136] This hot fix enhances the error-handling mechanism of ScanMail for Domino for AIX to enable it to handle such email messages. Issue 41: ScanMail for Domino for AIX may stop unexpectedly while trying to insert a disclaimer in some MIME message bodies. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 41: [Hotfix 3146] This hot fix enhances the error-handling mechanism of ScanMail for Domino for AIX to prevent the unexpected service interruption. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 41: To enable this error-handling mechanism: a. Install this Patch (see "Installation"). b. Add the "SMD_CATCH_EXCEPTION" hidden key to the "notes.ini" file and set its value to "1". c. Save the changes and close the file. d. Restart "SMDreal". Issue 42: Domino 8.5.3 servers and higher Domino server versions stop unexpectedly whenever any Domino task closes abnormally. When the ScanMail for Domino for AIX "SMDreal" task closes unexpectedly, it could also cause Domino 8.5.3 servers to stop unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 42: [Hotfix 3216] This hot fix improves the compatibility between ScanMail for Domino for AIX 5.0 and the scan engine to make scan threads more stable. This can help prevent the "SMDreal" task from closing unexpectedly and causing the Domino server to stop unexpectedly. 8.4 Patch 4 ==================================================================== 8.4.1 Enhancements ==================================================================== The following enhancements are included in this release: Enhancement 1: [Hotfix 3362] This hot fix enables users to sort documents in the "Database Scan History" page according to the data in any of the columns. Enhancement 2: [Hotfix 3362] This hot fix enables users to configure ScanMail to package and encrypt viruses before quarantining these viruses to the quarantine database. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 2: To configure ScanMail to package and encrypt viruses before quarantining these viruses to the quarantine database: a. Install this hot fix (see "Installation"). b. Log on to the Domino console and run the following command: set conf SMD_PACKAGE_QUARANTINED_VIRUS=1 Enhancement 3: [Hotfix 3413] This hotfix adds true file type exceptions in attachment filter. When an attachment matches the true file type exception list, it will not be scanned by the attachment filter. 8.4.2 Resolved Known Issues ===================================================================== NOTE: Please install the release before completing any procedures in this section (see "Installation"). This release resolves the following issue(s): Issue 1: ScanMail for Domino for AIX 5.0 cannot recall messages that were sent to multiple recipients when at least two of the recipients trigger different rules. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 1: [Hotfix 3335] This hot fix allows users to enable ScanMail for Lotus Domino for AIX 5.0 to recall messages that were sent to multiple recipients when at least two of the recipients trigger different rules. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 1: To enable ScanMail for Domino for AIX 5.0 to recall messages that were sent to multiple recipients and at least two of the recipients trigger different rules: a. Install this hot fix (see "Installation"). b. Open the "notes.ini" file in the Domino data directory. c. Add the "SMD_SPLITMAIL_RECALL_ENABLED" hidden key to the "notes.ini" file and set its value to "1". d. Save the changes and close the file. e. Restart SMDreal by running the following commands in the Domino server console: tell smdreal quit load smdreal Issue 2: When the ScanMail for Domino for AIX 5.0 binary file is shared among several Domino servers or partition servers, several SMDupd processes may run at the same time. Once the first SMDupd process runs, it locks the binary file and blocks all other SMDupd processes from accessing the file which may eventually corrupt the file. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: [Hotfix 3362] This hot fix enables other SMDupd processes to quit instantly after the first SMDupd process locks the binary file instead of waiting for the first process to unlock the file. Once the first SMDupd process completes, it notifies all SMDReal processes to reload the latest engine and pattern files. Users can also set the following: - the frequency at which the SMDReal process should check for engine and pattern updates and to reload the engine and pattern files if there are any updates. - the frequency at which the smdcm process should check for engine and pattern updates and upload the updates to the Trend Micro Control Manager(TM) server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 2: To enable other SMDupd processes to quit instantly after the first SMDupd process: a. Install this hot fix (see "Installation"). b. Log on to the Domino console and run the following command: set conf SMD_UPDATE_REALTIME_RELOAD=1 To configure the frequency at which the SMDReal process should check for engine and pattern updates and to reload the engine and pattern files if there are any updates: a. Install this hot fix (see "Installation"). b. Log on to the Domino console and run the following command, replacing "interval_value" with the preferred interval in seconds: set conf SMD_UPDATE_SMDREAL_CHECK_INTERVAL=interval_value c. Restart SMDreal To configure the frequency at which the smdcm process should check for engine and pattern updates and upload the updates to the Control Manager server: a. Install this hot fix (see "Installation"). b. Log on to the Domino console and run the following command, replacing "interval_value" with the preferred interval in seconds: set conf SMD_TMCM_CHECKSTATUS_INTERVAL=interval_value c. Restart SMDcm. Issue 3: When ScanMail for Domino for AIX 5.0 runs a scheduled database scan on a large number of databases and a large number of files have been updated, some files may not be scanned. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 2: [Hotfix 3362] This hot fix enables users to configure smddbs to scan databases that have not been scanned during the previous database scan and to skip databases that have already been scanned in the previous scan until all databases have been scanned. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 2: To enable this feature: a. Install this hot fix (see "Installation"). b. Log on to the Domino console and run the following command: set conf SMD_CYCLIC_SCHEDULE_DBSCAN=1 Issue 4: Each Scheduled Scan rule can only be configured to run one scheduled database scan which makes it impossible for multiple scheduled database scans to share the target databases. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 4: [Hotfix 3362] This hot fix enables Scheduled Scan rules to support multiple scheduled database scans. All the database scans scheduled by a rule share the same target databases. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 4: To enable this feature: a. Install this hot fix (see "Installation"). Issue 5: An email message may be delivered to a restricted group that the email sender cannot access because ScanMail for Lotus Domino for AIX needs to expand the restricted group and display its members before it can match rules correctly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 5: [Hotfix 3369] This hot fix resolves the issue by enabling ScanMail for Lotus Domino for AIX to skip restricted groups and match rules for unrestricted groups only. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure 5: To enable this feature: a. Install this hot fix (see "Installation"). b. Run the following command on the Domino console: set config SMDFilterUnexpandedGroup=1 Issue 6: When a mail is forwarded from Quarantine database while attachments are stored inside on archive, virus scanner may hang in a never ending loop. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 6: [Hotfix 3389] This hot fix resolves the issue by making sure that virus scanner switch to next element of MIME mail inside the working loop when the mail is forwarded from Quarantine database. Issue 7: An issue related to the APR module of the Trend Micro Management Communication Protocol (MCP) AgentSDK may trigger the SMDcm task to stop unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 7: [Hotfix 3410] This hotfix resolves the issue by upgrading the MCP AgentSDK. Issue 8: When Scheduled Scan is enabled in "smconf.nsf", the SMDsch task cannot trigger the SMDdbs task to run a database scan. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 8: [Hotfix 3413] This hotfix resolves the issue by ensuring that the SMDsch task triggers the SMDdbs task correctly to run a database scan while Scheduled Database Scan is enabled. Issue 9: When content filter is enabled, SMDreal task stops delivering email messages at random times from mail(x).box. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 9: [Hotfix 3419] This is caused by synchronization issues between ScanMail, eManager and VSAPI Scan engine. This hotfix enhances synchronization among SMLD, eManager and VSAPI Scan engine, and adds a common global lock between the SMLD components, eManager callback function and VSAPI scan engine. This makes sure that critical action inside Scan Engine functions VSInit(), VSQuit(), VSReadPattern() are executed during the whole process. A synchronization is done inside SMLD and eManager independently, before this change is made. Issue 10: SMDreal task stops randomly when content filter is enabled. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 10: [Hotfix 3421] This hotfix fixes potential memory issue in eManager and SMD, and updates the eManager to 6.7.1073. Issue 11: Office 2007 files belong to a special type of compressed files. ScanMail for Domino for AIX 5.0 blocks compressed Office 2007 files that contain any file that is in the blocked attachments list of attachment filters. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Solution 11: [Hotfix 3447] This hotfix allows ScanMail for Domino for AIX 5.0 to skip compressed files that contain only Office 2007 files with any of the following extension names even when the files contain any file that is in the blocked attachments list of attachment filters. - *.docm - *.docx - *.dotm - *.dotx - *.potm - *.potx - *.pptm - *.xlam - *.xlsb - *.xlsm - *.xlsx - *.xltm - *.xltx - *.ppam - *.ppsm - *.ppsx - *.pptx 9. Files Included in This Release ======================================================================== Filename Build No. ------------------------------------------------------------------- libsmdreal.a 5.0.1.3800 libsmddbs.a 5.0.1.3800 libsmdemf.a 5.0.1.3800 libsmdmon.a 5.0.1.3800 libsmdsch.a 5.0.1.3800 libsmdupd.a 5.0.1.3800 libsmdcm.a 5.0.1.3800 libsmdsupp.a 5.0.1.3800 libsmdext.a 5.0.1.3800 loader 5.0.1.3800 unregcm 5.0.1.3800 libunreg.so 5.0.1.3800 nBIFSender 5.0.1.3800 libProductLib.so 5.0.1.3800 ProductUI.zip 5.0.1.3800 libupdsmd.a 5.0.1.3800 smconf.ntf 5.0.1.3800 smdapproved.ntf 5.0.1.3800 smency.ntf 5.0.1.3800 smftypes.nsf 5.0.1.3800 smmsg.nsf 5.0.1.3800 smquar.ntf 5.0.1.3800 smtime.ntf 5.0.1.3800 smvlog.ntf 5.0.1.3800 smhelp.nsf 5.0.1.3800 AU module 2.86.0.4040 AuPatch libciuas64.so libpatch.so libtmactupdate.so cert5.db x500.db AgentSDK module 5.0.0.2615 libapr-1.so libcrypto.so libcurl.so libEn_I18N.so libEn_Utility.so libiconv.a libssl.so libTrendAprWrapper.a libuuid.so libz.so TMASE Engine 8.20.1013 libtmaseng.so VSAPI Engine 11.000.1006 libvsapi.o eManager module 6.7.0.1073 libem_helpr.so 10. Contact Information ======================================================================== A license to Trend Micro software usually includes the right to product updates, pattern file updates, and basic technical support for one (1) year from the date of purchase only. After the first year, you must renew Maintenance on an annual basis at Trend Micro's then-current Maintenance fees. Contact Trend Micro via fax, phone, and email, or visit our website to download evaluation copies of Trend Micro products. http://www.trendmicro.com/us/about-us/contact/index.html NOTE: This information is subject to change without notice. 11. About Trend Micro ======================================================================== Smart, simple, security that fits As a global leader in IT security, Trend Micro develops innovative security solutions that make the world safe for businesses and consumers to exchange digital information. Copyright 2024, Trend Micro Incorporated. All rights reserved. Trend Micro,ScanMail, Control Manager, eManager, Data Loss Prevention, and the t-ball logo are trademarks of Trend Micro Incorporated and are registered in some jurisdictions. All other marks are the trademarks or registered trademarks of their respective companies. 12. License Agreement ======================================================================== View information about your license agreement with Trend Micro at: www.trendmicro.com/us/about-us/legal-policies/license-agreements Third-party licensing agreements can be viewed: - By selecting the "About" option in the application user interface - By referring to the "Legal" page of the Administrator's Guide