Table of Contents
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”. 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:
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.
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.
If you have configured the Messaging Server to use a remote LDAP server, you must provide the LDAP Server Name to users when they set up their mail clients. The Preferences Manager does not correctly list the remote LDAP server in Client Setup screens of the Preferences menu. This only affects Netscape, Eudora, and KMail clients; the Outlook Configuration Tool correctly adds the remote LDAP server for Outlook clients, and IMP webmail clients do not need to provide this information.
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 for the Sun iPlanet and Novell eDirectory directory servers are installed in the /etc/ldap/schema/netscape and /etc/ldap/schema/nds subdirectories.
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.
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:
Specifies the list of alias databases used by the local delivery agent. For the Messaging Server, this is defined to look up aliases stored in the LDAP directory. Normal Postfix alias files cannot be used with the Messaging Server, because Postfix has been altered for the Messaging Server to look up the entire address instead of just the local part. For example, if mail were to be sent to "alias@foo.com", the entire address "aliasname@foo.com" would be looked up in the aliases databases instead of just "aliasname". This is controlled by the postfix domain_in_alias parameter, which must be set to the value "yes" for correct operation of the Messaging Server.
Specify the recipient for postmaster notices for the various errors that Postfix can report, based upon the notify_classes parameter configuration. Although Postfix assigns a default value of "postmaster" to these parameters if they are not configured, these parameters must be explicitly set for the operation of the Messaging Server. The Server Manager configures these parameters.
We recommend that you not edit these parameters directly.
Specifies the optional transport agent to use for recipients that are not found in the Linux passwd database. The Messaging Server sets this parameter to the Cyrus delivery agent, so that the local delivery agent first attempts to deliver mail to a Linux system account mailbox; if this fails, then it attempts to deliver mail via the Cyrus delivery agent to a Messaging Server mail account. This also means that if a Linux account user and Messaging Server mail account user are created with the same uid, then mail will always go to the Linux account user. See mailbox_transport parameter below for more information.
Do not change the fallback_transport parameter; doing so might disable the mail server, and mail may fail to be delivered to Messaging Server mail accounts.
Specifies optional lookup tables that define all addresses for which the machine will accept mail with respect to the values of the mydestination and inet_interfaces parameters. If this parameter is defined, then the SMTP server will reject mail for any addresses not found in the databases specified in local_recipient_maps. The Messaging Server sets this parameter to $alias_maps. To turn off this facility, comment out the local_recipient_maps parameter in the /etc/postfix/main.cf configuration file.
This Postfix parameter specifies the optional transport in the master.cf file to use for local delivery after processing aliases and .forward files. Because this parameter has precedence over the fallback_transport parameter, it is not used by the Messaging Server and should not be set manually.
If you set this to the Cyrus delivery agent, mail will not be delivered to any Linux system accounts. If you set this to anything else, mail will fail to be delivered to Messaging Server mail accounts.
Specifies what domains the machine will accept mail for and deliver locally, instead of forwarding to another machine. The Server Manager updates this parameter automatically when you create a new mail domain.
We recommend that you not edit this parameter directly.
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
Postfix includes built-in limits to the size of email messages and mailboxes. If either of these limits is exceeded, mail will not be delivered to the intended destination.
To control the size of email messages and mailboxes, you must set the parameters message_size_limit and mailbox_size_limit in the Postfix main.cf file to higher values. These parameters must be adjusted together; the value of mailbox_size_limit must be greater than or equal to the value of message_size_limit. When you have completed these adjustments, you must reload Postfix using the Server Manager Mail Services menu or using the /etc/rc.d/init.d/postfix reload command.
For more information about the/etc/postfix/main.cf file, see "Postfix Configuration - Basics" in the Wietse's Postfix Project documentation.
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:
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.
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.
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
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.