Dear SCO Customer, The enclosed Support Level Supplement (SLS) OSS465C, the Scomail Supplement, corrects several known problems with Scomail in the SCO OpenServer Release 5 family of operating system products. SLS OSS465C is intended for use on these products: SCO OpenServer Release 5.0.0 with Release Supplement 5.0.0d (rs500d) and Networking Supplement 1.0.0 (net100) SCO OpenServer Release 5.0.2 SCO OpenServer Release 5.0.4 with Release Supplement 5.0.4c (rs504c) SCO OpenServer Internet FastStart Release 5.0.4 with Release Supplement 5.0.4c (rs504c) SCO Internet FastStart Release 1.0.0, 1.1.0 If you are installing SLS OSS465C on a system with SCO OpenServer Release 5.0.4, the SCO OpenServer Release Supplement 5.0.4c (rs504c) must be installed prior to installing SLS OSS465C. If it is not, the Software Manager may exit unexpectedly, and you will not be able to install SLS OSS465C. If you are installing SLS OSS465C on a system with SCO OpenServer Release 5.0.0, the SCO OpenServer Release Supplement 5.0.0d (rs500d) and Networking Supplement 1.0.0 (net100) must be installed prior to installing SLS OSS465C. If SLS OSS601A is to be installed on a system, it should be installed prior to installing OSS465C. If it is to be installed at a later date, SLS OSS465C should be rolled back, OSS601A should be installed, and then OSS465C should be reinstalled. The following list highlights the changes to Scomail for OSS465C: - Scomail hang Scomail hangs at startup under certain conditions. - Scomail coredump Multipart/mixed MIME messages with a single part non-text body part are not parsed correctly; scomail will coredump when you try to save the folder. - Scomail FD leak Scomail leaks a file descriptor for each text/enriched message or attachment when it parses a mail folder. If too many of these kinds of messages are present and scomail runs out of file descriptors then a core dump occurs. Typically this occurs during startup when the INBOX has approximately 128 or more of these kinds of messages. - Updated scomail app-default and message files Inclusion of updated app-default and message files for 5.0.0 and 5.0.2 systems left out in OSS465A. The missing files will cause the hotlist button to go away. Depending on your system's mail configuration setup, the installation of OSS465C may modify /usr/mmdf/mmdftailor. If it is modified and you wish to restore the previous, unmodified version, it will be saved in /usr/lib/custom/oss465c.sav/usr/mmdf/mmdftailor. I. INSTALLING SLS OSS465C 1. Prepare the media for installation. Download the OSS465C media image file (oss465c file), place the file in the /tmp directory and rename the file by typing the following command: mv /tmp/oss465c /tmp/VOL.000.000 2. Run the Software Manager with the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. For SCO OpenServer 5.0.4, pull down the "Software" menu and select "Install New". For SCO Internet FastStart 1.x, and SCO OpenServer 5.0.0 or 5.0.2, pull down the "Software" menu and select "Patch Management --> Apply Patch". 4. When prompted for the host from which to install, choose the local machine and then "Continue". 5. When prompted to select the media device: If you are installing this SLS from diskette media, select the appropriate floppy disk drive and then "Continue". Proceed to step 6. If you are installing this SLS from media images per step 1, select "Media Images", then "Continue". When prompted for the "Image Directory", enter "/tmp" (or the directory where you placed the VOL file in step 1) and then select "OK". 6. For SCO OpenServer 5.0.4, when prompted to select software to install, ensure that the "OSS465C" entry is highlighted. Choose "Install". For Internet FastStart 1.x, OpenServer 5.0.0 or 5.0.2, when prompted to select installation type, choose "Full". 7. Once the installation finishes, quit the Software Manager. Installation of SLS OSS465C is now complete. II. REMOVING SLS OSS465C Note: Patches must be rolled back in the reverse order in which they were installed on a per-component basis. The OSS465C Scomail Supplement consists of a patch to the SCO MailUA component. If this component was patched after OSS465C was installed, then you will have to roll back the later patch before you can roll back the SLS OSS465C patch. IIa. Removing SLS OSS465C from SCO OpenServer 5.0.4 1. Log in as root. 2. Execute the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. Highlight "OSS465C: Scomail Supplement for SCO OpenServer Release 5.0". 4. Pull down the "Software" menu and select "Remove Software". 5. Once the removal finishes, quit the Software Manager. Removal of SLS OSS465C is now complete. IIb. Removing SLS OSS465C from SCO OpenServer 5.0.0, 5.0.2 and Internet FastStart 1.0, 1.1 1. Log in as root. 2. Execute the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. SLS OSS465C patches the software component SCO MailUA. To roll back this patch, pull down the "Software" menu and select "Patch Management-->Rollback Patch". 4. Take these steps: a. You will see the "Begin Rollback Patch" menu and will be asked to select patched software to roll back. Select "SCO Mail User Agents" and choose "Continue". b. You will see the "Patch Selection" window. Make sure that OSS465C is selected. Choose "Continue". c. You will see the "Confirm Selected Patches" window. Choose "Rollback" to confirm removal of OSS465C. d. You will see the "Rollback Progress" window, as the system performs the rollback of the patch, and finally a "Rollback Complete" window when the rollback is finished. 7. Exit the Software Manager by choosing "Exit" from the "Host" menu. Rollback of OSS465C is now complete. III. PRESERVING CUSTOMIZED FILES OSS465C backs up the following user-configurable file, then modifies it: /usr/mmdf/mmdftailor If you have customized this file, you can restore your changes from the backed-up copy after you install the supplement. The file is backed up to: /usr/lib/custom/oss465c.sav/usr/mmdf/mmdftailor If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.