Caldera Volution Messaging Server: Administrator's Guide | ||
---|---|---|
Prev |
The Messaging Server installation sets initial configuration parameters for Messaging Server components. For most simple mail configurations, it is not necessary to alter these initial values or to configure Messaging Server components directly. The Server Manager enables you to manage most of the basic Messaging Server functionality, including mail administration of mail domains, mail accounts, mail aliases, and other general Messaging Server system settings as discussed in "System settings" and "Mail administration". In addition to its ease of use, we recommend using the Server Manager whenever possible because it is less error-prone than editing files directly.
Nonetheless, the Messaging Server supports advanced component configuration for customized installations. To configure the many features available for OpenLDAP, Postfix, and Cyrus, consult the individual documentation available for each configurable component. The following sections cover only those features directly managed by the Messaging Server and any integration issues which affect the operation of the Messaging Server:
For more information, see their respective documentation, available from the Messaging Server webpage in DocView.
This section discusses:
Caution |
These are advanced configuration procedures that require extensive LDAP knowledge and experience. |
The configuration file for OpenLDAP is /etc/ldap/slapd.conf. It is configured for operation with the Messaging Server upon installation. We recommend that you do not alter this configuration. In particular, changing the access directives defined for the Messaging Server database might disable the Messaging Server and the Server Manager. For more information, see the slapd.conf(5) manual page.
Note: The /etc/ldap.conf file is the configuration file for the LDAP PAM module and is configured for use with the Messaging Server. Do not change the settings in this file.
By default, OpenLDAP is installed with its database in the directory /var/ldap/openldap-ldbm. You can relocate the queue to a different filesystem, although we recommend that you do so before configuring the Messaging Server and enabling mail delivery.
To relocate the OpenLDAP database before the Messaging Server is enabled:
Shut down the LDAP directory server:
/etc/rc.d/init.d/ldap stop
Copy the existing database to the new location. Use the cp -p flag to maintain the proper permissions and ownership of files and directories. For example:
mkdir -p /new/location cp -pR /var/ldap/openldap-ldbm /new/location
Set the directory parameter in /etc/ldap/slapd.conf to the new path for the database and comment out the old path. For example:
# relocated OpenLDAP database for Messaging Server use # directory /var/ldap/openldap-ldbm directory /new/location
Start OpenLDAP:
/etc/rc.d/init.d/ldap start
To configure a remote LDAP server:
Install the Messaging Server on the remote server.
On the remote server, run the command:
/opt/lsb-caldera.com-volution/msg/bin/msgldaphost
This will provide information about server passwords and user entities specific to the remote server.
On the local system, run the same msgldaphost command to set the system to point to the remote host, and to specify passwords and user entities.
For more information, see the msgldaphost(8) manual page.
The Messaging Server can be configured to use a directory server other than OpenLDAP; for example, the Sun® iPlanet and Novell® eDirectory directory servers. To do so, you will need information contained in:
schema files | Schema files for the Sun iPlanet and Novell eDirectory directory servers are installed in the /etc/ldap/schema/netscape and /etc/ldap/schema/nds subdirectories. | |
LDIF files | An LDIF (LDAP Data Interchange Format) file containing additional information about the required directory content and structure is stored on installed systems as /etc/opt/lsb-caldera.com/volution/msg/ldif.base. See also the ldif(5) manual page. | |
slapd.conf | The /etc/ldap/slapd.conf file contains useful information on the ACL's (Access Control Lists) enforced by the Messaging Server. See also the slapd.conf(5) manual page. |
When you have assembled the required information, run the msgldaphost command as described in "Configuring a Remote OpenLDAP Server". For more information, see the msgldaphost(8) manual page.
This section discusses:
Postfix configuration is controlled by parameters in the/etc/postfix/main.cf file. Although there are around 100 parameters, they are set to reasonable defaults (by default or by the Messaging Server installation) and do not require modification. The Messaging Server supports advanced Postscript configuration, but note the constraints on the following parameters:
For more information about the/etc/postfix/main.cf file, see "Postfix Configuration - Basics" in the Wietse's Postfix Project documentation.
By default, Postfix is installed with its message queue in the directory /var/spool/postfix. You can relocate the queue to a different filesystem, although we recommend that you do so before configuring the Messaging Server and enabling mail delivery.
To relocate the Postfix message queue before the Messaging Server is enabled:
Stop Postfix:
/etc/rc.d/init.d/postfix stop
Set the queue_directory parameter in /etc/postfix/main.cf to the new path for the queue and comment out the old path. For example:
# relocated Postfix message queue for Messaging Server use # queue_directory = /var/spool/postfix queue_directory = /new/location/postfix
Create the new directory for the Postfix message queue using the same directory name. For example:
mkdir /new/location/postfix
chown postfix:postfix /new/location/postfix
chmod 755 /new/location/postfix
Start Postfix:
/etc/rc.d/init.d/postfix start
This section discusses:
Cyrus configuration is controlled by parameters in the/etc/imapd.conf file. Although there are around 100 parameters, they are set to reasonable defaults (by default or by Messaging Server installation) and do not require modification. The Messaging Server supports advanced Cyrus configuration, but note the constraints on the following parameters:
admins | Configures the list of user ids with administrative rights for Cyrus inboxes. For the Messaging Server this is configured to include the administrative user "admin". This user is necessary for proper operation of the Messaging Server Manager; do not delete "admin" from the the admins parameter. | |
sasl_pwcheck_method | Defines the mechanism used by the Cyrus IMAP and POP servers to verify plain text passwords. For the Messaging Server, this parameter is set to the value "PAM" to allow Cyrus servers to authenticate via PAM (Pluggable Authentication Modules), which in turn is configured for these servers to use LDAP authentication. Do not change this parameter. |
For more information, see the imapd.conf(5) manual page.
You can set quotas on the size of Cyrus mailboxes using the cyradm(1) administrative client. This utility can be invoked as a script or interactively, and it can be used to administer local or remote Cyrus servers.
To use cyradm interactively, you must login as the admin user; the LDAP password is the same as the admin password. For example, to log into cyradm, enter:
cyradm -user admin hostname
After entering your admin password for cyradm and LDAP, you see the cyradm command prompt with your system name.Quota manipulation commands operate on quota roots, which can refer to a single mailbox or group of mailboxes. For example, the user susan might have a quota root of user.susan that includes the mailboxes name user.susan, user.susan.saved, and user.susan.todo. Quota roots are created automatically when they are designated in the cyradm setquota command.
The following cyradm commands can be used to manipulate quotas:
lm | Lists mailboxes. INBOX is the admin account mailbox. | |
setquota | Sets or removes storage limits for the specified quota root. | |
listquota | Lists storage limits for root and mailboxes in the specified quota root. | |
listquotaroot | Lists storage limits for a given mailbox in the specified quota root. | |
help or ? | Lists cyradm commands. |
For more information, see "Quotas" in Cyrus IMAP Server: Overview and Concepts and the cyradm(1) manual page.
By default, Cyrus is installed with its message store in the directory /var/spool/imap. You can relocate the queue to a different filesystem, although we recommend that you do so before configuring the Messaging Server and enabling mail delivery.
To relocate the Cyrus message queue before the Messaging Server is enabled:
Shut down the Cyrus master daemon to stop all IMAP/POP access:
/etc/rc.d/init.d/cyrus stop
Stop Postfix to halt all email delivery:
/etc/rc.d/init.d/postfix stop
Copy the existing message store to the new location. Using the cp -p flag will maintain the proper permissions and ownership of files and directories. For example:
mkdir -p /new/location
cp -pR /var/spool/imap /new/location/imap
If you are on an Open UNIX 8 system, go to the next step.
On an OpenLinux system, set the S attribute on the new message store hierarchy. When the S attribute is set on Linux ext2fs file systems, changes are written synchronously to the disk (this is equivalent to the sync mount option applied to a subset of the files). For example:
chattr -R +S /new/location/imap
Set the partition-default parameter in /etc/imapd.conf to the new path for the message store and comment out the old path. For example:
# relocated Cyrus message store for Messaging Server use # partition-default: /var/spool/imap partition-default: /new/location/imap
Start Cyrus:
/etc/rc.d/init.d/cyrus start
Start Postfix:
/etc/rc.d/init.d/postfix start
Note: The /etc/pam.d/imap and /etc/pam.d/pop files define the PAM modules that will perform authentication for IMAP and POP services, respectively. For the Messaging Server, these are set to use the LDAP PAM module and should not be altered.