The Messaging Server includes these administrative interfaces:
Server Manager | The principle graphical interface for Messaging Server administration. It provides mail server administrative screens accessible only by administrators with the login name "admin". For more information about server administration screens, see "System settings" and "Mail administration". By default, the Server Manager is served by the Apache webserver at: http://hostname/msg where hostname is the value returned by the hostname(1) on the Messaging Server system. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Preferences Manager | The Messaging Server mail client user interface. It provides client mail preference screens accessible to all users with an active Messaging Server mail account and an Internet browser. Like the Server Manager screens, it is served by the Apache webserver at: http://hostname/msg although logging in with a user mail account displays a different set of screens. For more information about client preference screens, see "Managing client preferences". | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Webmin | Webminis the browser-based system administration interface for Caldera OpenLinux Server 3.1. While it is not the principal Messaging Server administrative interface, it is the prefered utility for managing system functions used by the Messaging Server, such as:
For more information, see "Introduction to Webmin" in the Caldera OpenLinux System Administration Guide. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Command line utilities and scripts | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Although most administrative functions can be managed with the Server Manager, the following command lines utilities are also available:
|
These utilities are called from the /opt/lsb-caldera.com-volution/msg/bin directory. If you use them frequently, you might want to add /opt/lsb-caldera.com-volution/msg/bin to your PATH environment variable. For more information, see their respective manual pages.
Warning |
Many of these utilities form the back end for the administrative interface. This listing does not include those utilities in /opt/lsb-caldera.com-volution/msg/bin that should only be run by the administrative interface. Do not run the following utilities from the command line:
|
The Messaging Server has a single administrative account named admin. This is the name you use to log into the Server Manager for administering your messaging server. It is a valid mail account and can receive mail.
Note: Do not configure a local system account named admin; doing so will prevent the Messaging Server administrator from receiving mail.
The admin account is managed like other user accounts as described in "Managing Mail Users". You can also change the admin password by clicking on Admin Password under the System menu in the Server Manager.
Note: Before proceeding with Messaging Server configuration, we recommend that you change the initial admin password, set by default to "admin."
The Messaging Server enables you to migrate user data from existing UNIX system mail configurations by converting existing data files into LDAP datastores. You can import:
mailboxes
users
aliases
Note: In this Messaging Server release, user data can only be imported from UNIX and Linux systems. Future Messaging Server releases will include the capability of importing data from Microsoft® Windows and Exchange systems.
Existing mailboxes can be imported to the Messaging Server using any IMAP-capable mail client.
Use the msgusermigrate migration utility to convert UNIX system /etc/passwd entries to an LDAP datastore. To do so, copy the existing /etc/passwd and /etc/shadow files to a tmp directory on the Messaging Server system and run msgusermigrate. For more information, see the msgusermigrate(8) manual page.
Warning |
Make sure that none of the UIDs in the imported /etc/passwd file exist as system users on the Messaging Server system. Do not use the msgusermigrate utility in an attempt to create Messaging Server mailboxes for existing system users; doing so will result in failed mail delivery to the Messaging Server accounts. It you must have system users on your Messaging Server system, make sure that their Messaging Server UserID is different from their system uids. Also, be sure that the imported /etc/passwd does not contain an admin account. If you attempt to import a duplicate admin account, you might disable the Messaging Server. We recommend that you carefully review the contents of the imported /etc/passwd file before running the msgusermigrate utility. |
Use the msgaliasmigrate migration utility to convert UNIX system mail alias file entries to an LDAP datastore. To do so, run the on an imported aliases file or the local /etc/mail/aliases file. For more information, see the msgaliasmigrate(8) manual page.
You can use the Server Manager to change the password for the admin administrator account:
In the System menu, click on Admin Password.
Enter and confirm the new password value in the Change Password screen
Click on Apply to complete the change.
You can also change the admin password in the View Users but it is more direct to use this method in the System menu.
You can use the Server Manager to set global access privileges for users in all mail domains controlled by the Messaging Server.
In the System menu, click on User Access. You can grant or deny these privileges globally:
Users can change their own password | ||
Controls whether users can change the value of their mail account password via the Messaging Server admin user configuration interface. | ||
Users can change their own profile | ||
Controls whether users can change their profile parameters as described in "Managing mail users". | ||
Users can create mail aliases | ||
Controls whether users can create mail aliases within the Messaging Server directory using the Server Manager user configuration interface. |
The Server Manager allows you to view the status and perform certain actions on the Messaging Server component servers. In the System menu, click on Mail Services to view the list of configured services. Click on the service name to display its status, the PID of the active process, and the command that launched it. You can also take the following Service Actions:
cyrus IMAP/POP Server
Start/Stop | Start or stop the server |
docview - OpenLinux Documentation Server
Start/Stop | Start or stop the server | |
Restart | Stop and restart the server | |
Reload | Reload DocView configuration files |
ldap - OpenLDAP Directory Server
Restart | Stop and restart the server |
Note: Stopping the LDAP server disables the Server Manager; this can only be done manually.
postfix - Mail Transport Agent (MTA)
Start/Stop | Start or stop the MTA | |
Restart | Stop and restart the MTA | |
Reload | Reload MTA configuration files |
Mail services can also be controlled from the command line using standard init scripts:
/etc/rc.d/init.d/service [ start|stop|restart|reload ]
The Messaging Server provides Webmail service with the IMP (Internet Messaging Program) webmail client and Horde framework, which are enabled by default. At installation, the Messaging Server:
configures the mysql database engine to work with the horde database, which is used to store user information.
sets the horde database password to the value of the PW attribute, which is stored in the msg.conf(5) file. The system administrator can change this password using the utility:
/usr/libexec/horde/database/dbpasswd.sh
Note: Later versions of the horde package might store this utility in /usr/lib/horde/database/dbpasswd.sh
You will need this password if you want to make changes to your Horde or IMP configuration files.
starts the mysql daemon and sets it to run by default.
Messaging Server users can access the IMP webmail client immediately by pointing their browsers at http://hostname/horde/imp, as described in "Enabling IMP Client Users".
To disable Webmail service:
Disable default mysql daemon startup by editing the /etc/sysconfig/daemons/mysql file and changing the ONBOOT parameter to "no".
Stop the mysql daemon using either:
Webmin | In the Servers screen, click on MySQL Database Server, then click on Stop MySQL Server. | |
command line | Enter /etc/rc.d/init.d/mysql stop. |
For more information, see the Horde and IMP documentation, available from the Messaging Server webpage in DocView.
The Caldera Volution platform includes two system management and administration products that are compatible with the Messaging Server:
Volution Manager (VM) | ||
This Web-based management system enables administrators to manage the network with profiles and policies, without having to individually manage each system. Based on LDAP directory services, it can be configured to provide hardware and software inventory, software distribution, health monitoring of systems, printer configuration and scripted scheduled actions. It consists of: | ||
Volution Online | A proactive, subscription package management system. It tracks thousands of RPM packages, tracks alerts against these packages, and facilitates updates to your systems. |
Volution Manager and the Messaging Server can reside:
on the same machine | Both the Manager Server and Messaging Server Volution services can coexist on the same server, sharing the same OpenLDAP directory server. No special installation or configuration is required, simply run the Caldera installations for both products on the same system. The Manager Client and Messaging Server can also coexist together on the same machine, facilitating simple remote management of the Messaging Server platform. | |
on different machines | ||
The Manager Server and Messaging Server can also share the same OpenLDAP server but reside on different systems. In this configuration, the Messaging Server has to be configured to recognize a remote LDAP server as described in "Configuring a Remote OpenLDAP Server". |
The Volution Manager and Messaging Server can work together to provide:
For more information, see the Volution Manager Administration Guide.