| Revision History | |
|---|---|
| Revision Release 2.0 | 24 February 2003 |
|
First posting |
|
Table of Contents
Late News provides critical information you need to know before and just after installing the SCOoffice Mail Server Release 2.0.
This document assumes you have already read the SCOoffice Mail Server Cover Letter included with your distribution media. You should also familiarize yourself with Late News before:
installing and configuring SCOoffice Mail Server
using the SCOoffice Mail Server Getting Started Guide, which is available:
in a printed book included with your SCOoffice Mail Server distribution
using the DocView online documentation system after the SCOoffice Mail Server is installed
in HTML and PDF format in the /doc/getstart directory on the distribution media or ISO images
This document provides information about:
CA InoculateIT (http://www.cai.com/)
Sophos Anti-Virus (http://www.sophos.com/)
Sophos MailMonitor (http://www.sophos.com/)
Arkeia Backup Solution (http://www.arkeia.com/)
BakBone NetVault (http://www.bakbone.com/)
Lone Star Software Lone-Tar (http://www.cactus.com/)
Microlite BackupEDGE SS (http://www.microlite.com/)
SCOoffice Mail Connector for Microsoft Outlook (separately licensed product included with SCOoffice Mail Server)
Faximum Messaging Server (http://www.faximum.com/)
VSI-FAX (http://www.esker.com/)
SCOoffice Mail Server Maintenance Pack 2.01 is available from http://www.sco.com/support/download.htmloffice20.html. This maintenance pack fixes the following known limitations:
Microsoft Outlook was getting a permissions error when trying to post free/busy information on UnitedLinux-based servers.
The IMP address book link (from the compose screen which is accessing the contacts list) got an error.
The mysql daemon was not starting on UnitedLinux, which prevented IMP logins with a `database access error message.
The root shared folder, All Public Folders, was created with the wrong permissions so that users could not post to it.
The number of file descriptors has been raised so that it is possible to have 5,000 clients connect. Additional configuration is needed to support 5,000 clients: the memory_limit parameter needs to be manually raised in /etc/httpd/php.ini (default is 8MB, 32MB is recommended).
Machines on external networks were not able to send mail to the oms server and were getting a "relay access denied" message.
The dracd daemon 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.
There is a case bug if a system name is in DNS with an upper-case .COM instead of a lower-case.com, and the machine is locally configured to have a lowercase .com in its name. While this fixes a compare statement that was causing a problem, it is not recommended to mix case with the OMS server. More testing is required.
The crontab for root is fixed to call msgsievebuild in the right path in the case of an upgrade from Volution Messaging Server 1.1.1 to SCOoffice Mail Server Release 2.0.
The version number is changed to 2.0.1 on the web login screen.
imapcp has been fixed to handle the new Cyrus namespace.
msgdomainmove has been fixed to properly update the MsgDrop attribute. This could prevent mail to a newly renamed domain in oms 2.0.
Several bugs created by upgrading from OMS 1.1.1 are fixed:
In /etc/ldap/slapd.conf several items could be incorrect following an upgrade, which would cause the ldap server to be inaccessible:
The suffix was wrong if a non-default suffix was used for OMS 111.
rootdn was wrong if a non-default one was used for OMS 111.
a plain text password was left in rootpw.
msgipu did not run correctly, which would leave some attributes incorrectly populated in the ldap database, notably MsgDrop. This had the potential to stop mail from being delivered to those users.
By default, SCOoffice Mail Server Release 2.0 uses a domain name that does not contain the local machine name. If you perform an in-place-upgrade from Volution Messaging Server 1.1.1, domains are not renamed to match the new default. Manually renaming the domain names can be time consuming if you have a lot of users because you have to reconfigure user's return addresses on every client machine.
SCOoffice Mail Server Release 2.0 supports the Cyrus alternate namespace configuration. Enabling the alternate namespace changes how mailboxes are presented to the user: mailboxes are no longer forced to be under inbox.
The problem caused by enabling altnamespace for an in-place-upgrade is that mailfolders appear to move from under the inbox to become its peer. Shared folders cease to be peers of inbox, and move down into the Shared Folders directory.
Moving folders can confuse mail clients. For an IMAP client you have to manually flush the localb cache of mail folders and messages, and reload the host. This is not necessary for a POP client.
To enable the alternate namespace feature:
Enable the alternate namespace in Cyrus by changing the altnamespace parameter to "yes" in /etc/imapd.conf.
Stop cyrus and postfix.
/etc/rc.d/init.d/cyrus stop
/etc/rc.d/init.d/postfix stop
Choose a new domain name, and rename your old primary domain to the new domain name (don't include the machine name in the new domain name).
/opt/msg/bin/msgdomainmove --olddomain=<oldname> --newdomain=<newname> --exists
This command will move every user and alias object in the domain, one at a time, over the LDAP protocol. This can take a long time if you have a lot of users.
To enable the alternate namespace in postfix, add a line to /etc/postfix/transport.
<machinename> local:
For example, if your machine name is stellar.sco.com, append the following line:
stellar.sco.com local:
Adding this line enables the alternate namespace feature so that mail to the users at the machine name goes to system user's mailboxes in /var/spool/mail, and mail to users in all SCOoffice Mail Server domains go to those users imap/pop mailboxes.
Don't forget, you also have to flush client caches in the case of IMAP clients. Methods for flushing client cache data vary and are not discussed here.
By default IMP has a maximum message size of about 2MB. The following is an example of how to reconfigure IMP to support a larger message size:
Edit the file /etc/httpd/php.ini (for OpenLinux), or /etc/php.ini (for UnitedLinux), and change the following values as shown (in this example, we are increasing the message size to 10MB):
upload_max_filesize = 10M
memory_limit = 64M
post_max_size = 10M
For a message size greater than 10MB, you also have to edit /etc/postfix/main.cf and change the mailbox_size_limit and message_size_limit parameters to the new value. For example, to set a 50 MB maximum:
mailbox_size_limit = 50000000
message_size_limit = 50000000
These changes are necessary because postfix has a 10Mb maximum message size by default.
Mail Servers often reside behind firewalls. The following port needs to be open in order to send and receive mail through the firewall.
| Portname | Normal Port Number | SSL Port Number |
|---|---|---|
| SMTP | 25 | 465 |
The following are ports to open if you want clients to be able to access the mail server from outside the firewall:
| Portname | Normal Port Number | SSL Port Number |
|---|---|---|
| IMAP | 143 | 993 |
| POP | 110 | 995 |
| LDAP | 389 | 636 |
| HTTP | 80 | 443 |
It is possible to open only the SSL ports for remote client access, but SMTP requires port 25 as most mail servers do not default to port 465.
You can use the standard shared calendar feature of the SCOoffice Mail Server, which works via ftp or WebDAV rather than the IMAP protocol used by SCOoffice Mail Connector for Microsoft Outlook (which is a separate product).
Microsoft Outlook Express is not supported for shared calendaring.
To configure shared calendaring with Outlook on SCOoffice Mail Server Release 2.0:
Set up the shared calendar directory. This will be ftp (for Outlook 98-2000 clients) or WebDAV (for Outlook XP clients).
Outlook 98-2000 clients
Make sure that ftpd is running and you can ftp into the system. If SCOoffice Mail Server is running on SCO Linux but ftpd is not running, see Enabling ftp on SCO Linux 4.0. If SCOoffice Mail Server is running on OpenLinux then make sure that /etc/inet.d/wuftpd is uncommented. Verify that the /srv/ftp/pub/calendar directory is set up so that:
Anonymous ftp is enabled for READ for the calendar directory.
Owner must have write permission for the calendar directory so that they can re-publish their free/busy files (.vfb).
Outlook XP clients
The httpd.conf file must have WebDAV enabled for this directory accordingly (only for XP). To do this edit the file /etc/httpd/httpd.conf and change the text:
to:
Then run:
/usr/sbin/apachectl restart
On your Windows client start MS Outlook and click Tools > Options > Calendar Options > Free/Busy Options. Tick "Publish my free/busy information" and set the following MS Outlook free/busy URL's:
If SCOoffice Mail Server is running on OpenLinux:
Outlook 98-2000 clients
Outlook XP clients
If SCOoffice Mail Server is running on OpenLinux:
The ftp user must have the same uid as httpd
ftp:ftp (check for uid equivalencies in /etc/passwd)
If SCOoffice Mail Server is running on SCOLinux:
The free/busy user must have the same uid as ftp
freebusy:users (check for uid equivalencies in /etc/passwd)
Enter meeting attendees in Outlook:
Outlook must be able to resolve the email address of the name that you type in as a meeting attendee. This is denoted by the attendee being underlined. If this does not happen the email address is not resolved via the address book and the free/busy data may not be displayed.
To avoid name resolution problems add attendees by using the "Invite Others" or the "Add Others" button in the meeting dialog. This will bring up the address book from which the attendees can be selected.
Avoid problems:
Be sure that the SCOoffice Address Book is the first address book searched when resolving email addresses from the Outlook Address Book List of searchable address books. Intermittent difficulties resolving email addresses for manually entered names can arise when an Outlook Address book is searched before the SCOoffice Address Book.
ftpd is configured by default by OMS 2.0, but if you find that ftp is not enabled, you can use the following instructions to enable it.
On SCO Linux 4.0 the inetd super-server is xinetd. Its configuration file, /etc/xinetd.conf, contains:
service ftp
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/in.ftpd
# server_args = -a
instances = UNLIMITED
}
to:server = /usr/sbin/in.ftpd
and then restart xinetd with:server = /usr/sbin/vsftpd
kill -SIGHUP `pidof xinetd`
If you want particular users, such as root, to be able to ftp to the machine then edit the file /etc/ftpusers and comment-out the user's names if they exist in that file. The missing /usr/sbin/in.ftpd has been bug-reported to SCO Engineering.
"Licensing" in the Getting Started Guide describes some of mail server configurations available for the SCOoffice Mail Server, although others might also be available in your area. Contact your SCO representative to design a mail service solution that fits your needs.
The Server Manager includes Help screens that connect to individual topics in the Administrator's Guide. In addition to describing the Server Manager, the Administrator's Guide also includes detailed information about advanced administrative procedures and SCOoffice Mail Server components. We recommend using the DocView documentation server to browse this information; some of the Administrator's Guide hotlinks cannot be displayed in the Server Manager Help screens. For more information about DocView, see "Viewing OpenLinux Documentation" in the Getting Started Guide.