SCOoffice Mail Server 2.0.0 Maintenance Pack 3 Coverletter and Installation instructions. KEYWORDS: scooffice volution messaging mail server mpack maintenance pack fixes bug patch supplement latest security 200 2.0.0 2.0.3 mpack3 office vms oms RELEASE: SCOoffice Mail Server 2.0.0 PROBLEM: Where do I find the latest fixes for the SCOoffice Mail Server? SOLUTION: Install the latest Maintenance Pack available from: ftp://ftp.sco.com/pub/office/mail_server/2.0/ -------------------------------------------------------------------------------- Dear Customer, This package contains the SCOoffice Mail Server 2.0.0 Maintenance Pack 3. This Maintenance Pack contains important fixes to your system and should be applied at the time of your next maintenance period. This Maintenance Pack is the Minimum Recommended Patch and should be applied prior to submitting problem reports to SCO Support. -------------------------------------------------------------------------------- I. Software Notes and Recommendations 1. This Maintenance Pack is intended for use with: SCOoffice Mail Server 2.0.0 2. This maintenance pack includes all the fixes in the previous maintenance packs plus new fixes. 3. If you have not already installed the earlier Maintenance Packs, it is not necessary to do so before installing this Maintenance Pack. 4. Removing the Maintenance Pack is possible, but not recommended. The Maintenance Pack mostly removes itself but a few things are left. These things will not interfere with future versions of a Maintenance pack or SCOOffice Mail Server. The following changes are not removed when the Maintenance pack is removed: 1. The freebusy user is not reset to the incorrect user in /etc/passwd. 2. The primary domain is left in /etc/postfix/main.cf in the mydestinations parameter. The scripts that edit this field are removed however so the mydestinations parameter will not be updated when virtual domains are created or deleted. 3. All Public Folders permissions are not reset to the previous invalid ones. 4. Roots crontab is left alone with the correct path to msgsievebuild. 5. The file slapd.conf is left in the "fixed" state, suffix, rootdn, and rootpw. 6. The ldap database is updated after an upgrade scenario, they are not downgraded after removal. 5. If you have questions regarding this supplement, or the product on which it is installed, please contact your software supplier or Technical Support representative. -------------------------------------------------------------------------------- II. Installation instructions: The maintenance pack is a single file: scomsg-mpack-2.0.3*.i586.rpm 1. To install use the following command: # rpm -ivh scomsg-mpack-2.0.3*.rpm or if a previous maintenance pack is installed: # rpm -Uvh scomsg-mpack-2.0.3*.rpm -------------------------------------------------------------------------------- III. Removal Instructions 1. To remove This Maintenance Pack use the command: # rpm -e scomsg-mpack NOTE: Removal of the Maintenance Pack is not recommended -------------------------------------------------------------------------------- IV. Bugs fixed by this Maintenance Pack: Bugs fixed in Maintenance pack 2.0.3: 1. GUI shows cyrus and postfix services as DOWN (SCO Linux 4 only). fz527736 2. After a full re-installation of OMS, free/busy posting doesn't work. fz527835 3. Improved punctuation in vacation message. fz527031 4. Increased vacation "memory" (period in which addresses are kept and are not responded to) to 7 days. 5. Cyrus, postfix, slapd logging level are too verbose, causing log files to fill up. fz527608 6. OMS starts inetd unnecessarily (SCO Linux). SCO Linux already uses xinetd. fz527337 7. E-mail to users with different uid and e-mail ID bounces. fz527577 8. Webmail (Horde/IMP) not working on OpenLinux after upgrade to OMS2. fz527318 9. Webmail (Horde/IMP) not showing attachment icon on OMS2. fz527856 10. Folders (admin, All Public Folders) missing under LKP (OpenUNIX/Unixware). fz527876 11. Webmail (Horde/IMP) not sorting read/unread messages together. fz527857 12. Mysql not starting under LKP. 13. The "Add yourself" to an alias option was broken when uid!=email. fz527951 14. The command msgsievebuild fails with the message: "Cannot find tag for: " fz528026 ------------------------------------ Bugs previously fixed in Maintenance pack 2.0.2 (included in 2.0.3): 1. This maintenance pack includes all the fixes in the previous maintenance pack 2. Polish and Italian message catalogs for the command line programs in /opt/msg/bin have had numerous errors removed from them. 3. IMP now creates 8-bit mailboxes with the correct encoding so it will inter-operate properly with Outlook and other IMAP clients. The downside is that old folders created by IMP with 8-bit characters in them will have to be renamed after the maintenance pack is installed. 4. Virus scanning was broken on SCO Linux 4.0 due to some missing perl modules, the modules are now included in the mpack. 5. /opt/msg/bin/msgadminresetpw is a new utility that will reset the admin password back to the default for users who have forgotten their admin password. 6. the ldap root pw was left in plain text, we fixed this on Open Linux but neglected it on SCO Linux 4, it is now fixed on both platforms by this Maintenance pack. 7. timsieved could not accept SASL authentication so websieve was broken among other things, this did not affect OMS 2.0 itself, only add-on attempts. ------------------------------------ Bugs fixes in Maintenance pack 2.0.1 (included in 2.0.2): 1. Outlook was getting a permissions error when trying to post freebusy information when the server was based on UnitedLinux. 2. The IMP address book link (from the compose screen which is really accessing the contacts list) got an error. 3. mysql daemon was not starting on United Linux which prevents IMP logins with a database access error message. 4. The root shared folder: All Public Folders was created with the wrong permissions so that users could not post to it. 5. The number of file descriptors has been raised so that it is possible to have 5,000 clients connect. Additional configuration is needed by the system administrator to support 5,000 clients: the memory_limit parameter needs to be manually raised in /etc/httpd/php.ini (default is 8mb, 32mb will suffice). 6. machines on external networks were not able to send mail to the oms server and were getting relay access denied. 7. dracd was not starting after a reboot causing clients to get relay access denied when sending mail if they were not on the same subnet as the server. 8. case bug if machine is in DNS with a .COM instead of a .com, and the machine is locally configured to have a lowercase com in its name. While this fixes a compare statement that was causing problems it is not recommended to mix case with the OMS server because we have not done exhaustive testing in this area. 9. The crontab for root is fixed up to call msgsievebuild in the right path in the case of an upgrade from volution messaging server 1.1.1 to SCO Office Mail server 2.0. 10. The version number is changed to 2.0.2 on the web login screen. 11. imapcp has been fixed to handle the new cyrus namespace. 12. msgdomainmove has been fixed to properly update the MsgDrop attribute. This could prevent mail to a newly renamed domain in oms 2.0. 13. address book in IMP did not support non-english characters correctly. 14. msguninstall now automatically removes the mpack if it is installed. Several bugs created by upgrading from 1.1.1 are fixed here: 1. In slapd.conf (in /etc/ldap) several items could be incorrect after an upgrade which would cause the ldap server to be inaccessible: 1. Suffix was wrong if a non-default one was used for oms 111. 2. Rootdn was wrong if a non-default one was used for oms 111. 3. A plain text password was left around in rootpw. 2. The command msgipu was not run correctly which would leave some attributes populated incorrectly in the ldap database, notably MsgDrop. This has the potential to stop mail from being delivered to those users.