Table of Contents
The Messaging Server provides a graphical installation with sufficient tools to completely set up and configure a fully functional mail server, as well as an in-place upgrade from earlier Messaging Server releases. This chapter describes:
See also the Late News document for up-to-date information on installation issues and platform support:
Use the graphical Installer to install the Messaging Server on a local Caldera OpenLinux system. The Messaging Server Installer can be started from the autorun.sh or install.sh scripts on installation media.
To install on a local Caldera OpenLinux system:
Prepare the installation media. You must have Messaging Server distribution media or a CD you created from downloaded ISO images.
Log on as root.
Insert the installation media in the drive.
If the Automount facility is enabled (this is the default), you will see the Messaging Server Welcome screen, where you are prompted to run the installation. This will invoke autorun.sh. You can either:
Click on Yes to begin the installation immediately.
Click on No to defer installation. You can begin the installation at any time by clicking on the install.sh icon in the Konqueror file manager when it displays the contents of the distribution media.
If Automount has been disabled:
Use the mount(8) command to mount the installation media:
mount /dev/cdrom/mount_point
Run install.sh from the CD mount point:
/mount_point/install.sh
Review the licensing statement.
Review the displayed confirmation statement.
The installation script will not start if RPM packages required by the Messaging Server are not found on the system or if DNS is not configured. If this happens, install the packages, correct any errors listed, and start it again.
After displaying licensing information, install.sh analyzes the installed RPM list and installs any Messaging Server RPMs that are not listed. If any of the RPMs failed to install, try to install them manually or check the installed packages database using the rpm(1) command.
When the installation completes, you are prompted to view the installation log file, with the option to save it (the default location is /root/install.log). The log file displays the results of default component configuration conducted during the installation process, including:
verbose output of the pre- and post-install scripts
daemons started:
slapd (LDAP daemon)
Postfix master(8) daemon
Cyrus master daemon (imap_master(8) )
httpd instances for Apache and DocView
default configuration values
any installation errors
Many of the error notices at the beginning of the log file are normal and expected. If your installation fails, check the end of the log file.
As soon as installation is complete, we recommend that you change the initial admin password, set by default to "admin"; see “The admin Administrative Account”.
This completes Messaging Server installation. You can now configure mail service as described in Chapter 4 “Administering the Messaging Server”.
You can upgrade the Messaging Server to Release 1.1 using the install.sh utility. Upgrades are supported from:
Messaging Server Release 1.0
Messaging Server Release 1.0 with Maintenance Pack 1
Messaging Server Release 1.0 with Maintenance Pack 2
It is not necessary to add or remove Messaging Server maintenance packs before performing an upgrade.
The upgrade procedure runs from the command line only. Running the graphical installer on a system with the Messaging Server already installed results in an error.
The Release 1.1 upgrade cannot be removed. That is, once the upgrade has been performed, you cannot roll back to an earlier release. If you want to return to an earlier release, you must back up your data, remove the Messaging Server and reinstall with any desired maintenance packs.
To upgrade a local Caldera OpenLinux system:
Prepare the installation media. You must have Messaging Server distribution media or a CD you created from downloaded ISO images.
Log on as root.
Insert the installation media in the drive.
At the root command line prompt, enter:
cd /auto/cdrom
cd mpack-1.1.0
./install.sh
You can also install or upgrade the Messaging Server on an Open UNIX 8 system with LKP using the same install.sh script. However, before doing so, you must follow these steps as root on the Open UNIX 8 system:
Prepare the installation media. You must have Messaging Server distribution media or a CD you created from downloaded ISO images.
Log in as root. If you are installing the Messaging Server for the first time, start a terminal window from your graphical environment. The X server must be running for the Messaging Server installation, but it is not required for the Messaging Server upgrade.
Mount the Messaging Server CD-ROM on /linux/mnt/cdrom by entering:
mount `devattr cdrom1 bdevice` /linux/mnt
If you are upgrading, go to the next step.
If you are installing, ensure that the X display is available (but only to local system users) by entering:
xhost local:
Run the linux command to enter the LKP environment.
In the LKP environment, you can then change directories (cd) to /mnt/cdrom and either:
cd /mnt/cdrom
./install.sh
cd /mnt/cdrom
cd mpack-1.1.0
./install.sh
The Messaging Server then installs or upgrades on the LKP system as described in “Native Caldera OpenLinux Stand-alone Installation ” and “Native Caldera OpenLinux Upgrade”. When the installation or upgrade is complete, reboot your Open UNIX 8 system by either:
clicking the reboot button after the graphical installation completes, or
running the shutdown command from the Open UNIX 8 environment after the upgrade completes.
If this is your first Messaging Server installation, we recommend that you immediately change the initial admin password, set by default to "admin"; see “The admin Administrative Account”.
The autorun.sh script does not run under LKP.
The mailbox for the admin administrator account might not be created automatically during installation on Open UNIX 8. If not, it must be created manually or the admin user will not be able to send or receive mail. For more information, see “Known Limitations in This Release”.
The Messaging Server can be installed or upgraded without the graphical Installer using the install.sh utility with the -c option. This performs a non-interactive install that does not rely on the X server; the installation proceeds directly with no prompts or checks. This can be useful if you have an archive file of the Messaging Server media that you would like to install on a remote system.
To install or upgrade the Messaging Server in non-graphical mode, unpack the archive file and run the following command in the same directory:
./install.sh -c
When the installation or upgrade is complete, we recommend that you review the /root/install.log file to confirm that the installation was successful.
The Messaging Server can be installed on remote systems using Volution Manager. To do so, you must:
have Volution Manager installed on the local system.
have Volution Manager Client installed on the same target system as the Messaging Server.
ensure that the target system meets other Messaging Server system requirements.
Follow these instructions to install the Messaging Server on remote systems using Volution Manager.
Place the Messaging Server CD on the Volution Manager server system. If the CD mounts automatically, it will be visible in the directory /auto/cdrom. Do not install the Messaging Server if you are prompted to do so.
If automount is not configured on your system, enter the following command to mount the Messaging Server CD:
mount /dev/cdrom /mnt/cdrom
Do not use Volution Manager to install the Messaging Server on the same system as the Volution Manager Server. Doing so might disable LDAP service. Use the standard Messaging Server installation instead.
Read and accept the terms of the Messaging Server End User License Agreement before installing the Messaging Server product with Volution Manager. This agreement can be found in the file license.txt in the top directory of the CD.
Copy the RPM's from the /auto/cdrom/RPMS/ directory into the Source Repository. Enter the following commands:
cd /auto/cdrom/RPMS
cp *.rpm /opt/volution/srcfiles/rpm/Linux/IA32/Caldera/3.1/
Create two installation Profiles. The first includes some prerequisite packages that must be present for the Messaging Server to be installed. Use Volution Manager to create a Profile with the following attributes:
Constraints
OS Version: 3.1
OS Vendor: Caldera
OS Platform: Linux
OS Architecture: IA32
Package Flags
nodeps
force
Package Lists
db
libmcrypt
libtool
php
volutionmsg-vmgr
Add Links to systems on which you wish to deploy the Messaging Server, then save the Profile to commit to installation.
The second Profile must not be installed until the first has been installed succesfully. Use Volution Manager console to create this second Profile with the following parameters:
Constraints
OS Version: 3.1
OS Vendor: Caldera
OS Platform: Linux
OS Architecture: IA32
Package Flags
nodeps
force
Package Lists
cyrus-imapd
cyrus-sasl
gq
perl-Convert-ASN1
perl-IMAP-Admin
perl-Mcrypt
perl-ldap
postfix
volutionmsg
volutionmsg-doc
Scripts
Post-Install Script:
/opt/lsb-caldera.com-volution/msg/install /tmp/postinstall.log
Add Links to systems on which you wish to deploy the Messaging Server, then save the Profile to commit to installation.
You may also want to create a Volution Manager Policy to configure system monitoring and other services for the remote Messaging Server.
For more information, see “Using Volution System Management Services” in the Administrator's Guide and the Volution Manager Administration Guide.
To remove the Messaging Server from your system, enter:
cd /
/opt/lsb-caldera.com-volution/msg/bin/msguninstall
The removal script does not:
downgrade to an earlier Messaging Server version; it removes the entire product.
reinstall components that were removed at Messaging Server installation; for example, sendmail™ and imap™.
restore updated RPMs to the earlier version.
remove configuration directories that you populated or that contain files backed up by the Messaging Server. The removal script error listing identifies these directories.
remove configuration information from mail clients.
If the removal script fails for any reason, the removal might not be complete and the msguninstall utility might no longer be available. In this case, you must run the uninstall.sh script from the distribution media. To do so, ensure that the Messaging Server CD-ROM is mounted and enter:
/mount_point/uninstall.sh
For more information, see the msguninstall(8) manual page.
After removing the Messaging Server from an Open UNIX 8 system and reinstalling it after reconfiguring the system for a security level higher than the normal security setting, the /home/vscan directory is owned an incorrect system user ID. This prevents the Messaging Server from sending mail. This is because the /home/vscan directory is not removed by the msguninstall(8) utility, and under higher than normal security settings, user IDs are not recycled. Thus when the vscan user is assigned a different user ID after reinstallation, the directory is owned by the wrong user ID.
To work around this problem, do one of the following:
Remove the /home/vscan directory after removing the Messaging Server.
Run the following command after reinstalling the Messaging Server:
chown vscan /home/vscan
Messaging Server graphical interfaces provide language support for:
English
French
German
Spanish
To access the Server Manager in one of these languages, simply set the language in your browser. You should also instruct mail client users to set the appropriate language for their browser; translated Help screens for the Preferences Manager are provided.
The Messaging Server default character set is UTF-8.
Netscape Communicator 4.7 does not support automatic switching of character sets. To display Messaging Server graphical interfaces correctly, UTF-8 must be set specifically in the View->Character Set menu.
If you install the Messaging Server on a system that is not connected to the Internet -- for example, a stand-alone system with intermittent Internet connections -- additional DNS (Domain Name Service) configuration might be necessary if outgoing mail is not delivered. You can confirm this problem by running the mailq command; if errors indicate that it was not able to contact host 127.0.0.1 for queued messages, use the following procedure to modify your DNS configuration:
Verify that:
the output of the nslookup 127.0.0.1 command is localhost.domain_name.
the output of the nslookup localhost.domain_name command is 127.0.0.1 with server name localhost.domain_name.
there is no MX record for localhost. There is no such record by default, but if there is, Postfix can generate looping errors.
If these conditions are not met, you must modify your name service configuration accordingly.
Edit the /etc/postfix/main.cf file and change it so that the content_filter assignment line reads:
content_filter = smtp:localhost.$mydomain:10025
Note the following known limitations in this Messaging Server release:
In a normal installation, a Cyrus mailbox is created automatically for the admin user. However, installation errors on an Open UNIX 8 system might prevent this mailbox from being created; these errors do not appear in the installation log. You must verify that the mailbox exists and create it manually if it does not. Otherwise, the admin user will not be able to send or receive mail. To do so:
Log onto the Open UNIX 8 system as root and switch to the LKP environment by entering:
linux
Verify the existence of the admin mailbox by entering:
ls -d /var/spool/imap/user/admin
If this directory is present, you have an admin mailbox on your system; you do not need to create the mailbox manually.
If you receive a No such file or directory error, the admin mailbox was not created. You must do so manually as described in the next step.
Use the msginboxcreate utility to create the admin mailbox:
/opt/lsb-caldera.com-volution/msg/bin/msginboxcreate --name=admin
You will be prompted for the admin password.
The msgusercreate(8) manual page cautions against running this utility from the command line. That is because a user's UserID and mailbox are usually created at the same time using either the Server Manager or the msgusercreate(8) utility. However, due to an installation error, the admin UserID has been created without a corresponding mailbox, so msginboxcreate can be run safely from the command line in this case only.
Verify the existence of the admin mailbox as described in Step 2.
You can now access your admin account mailbox.
If you delete a user who is the last owner or member of an alias, the alias will be silently deleted. Before removing a user, we recommend that you check their aliases; to do so, click on Aliases in their View User display. For this reason, we also recommend that every alias have at least two owners, and that important aliases also include the admin user as an owner or member.
If you use the msgldaphost utility to configure an alternate LDAP server, do not specify the --port option; doing so will cause LDAP authentication failures. The utility automatically sets the default port. For more information, see the msgldaphost(8) manual page.
The ipurge(8) utility deletes mail from IMAP mailbox or partition based on age or size. However, it has an undocumented -f option, which you must use if you wish to use the utility on Messaging Server user mailboxes. By default, ipurge works only on public folders.
Because Caldera OpenLinux Server 3.1 is not internationalized or localized, not all localization features of Messaging Server Release 1.1 are available when it is installed on the Caldera OpenLinux 3.1 platform. If you require localized Messaging Server support, we recommend that you upgrade Caldera OpenLinux to release 3.1.1.
The Messaging Server Release 1.1 Client User's Guide is available in English, French, German and Spanish; this also ensures that Help screens for the Preferences Manager user interface are also available in these languages. However, the Messaging Server Administrator's Guide guide has not been translated for this release, hence Help screens for the Server Manager interface are available in English only. This Getting Started Guide is also available in English only.
This list includes all product limitations known at the time of publication. Unless otherwise noted, they will be corrected in product updates or future releases. For more information, we recommend that you consult the Messaging Server Late News document, which is updated regularly on the Caldera website: