Chapter 2 Installing Messaging Server 4.1

This chapter describes how to install Messaging Server 4.1. It assumes that you have completed the previous steps:

• Gathering Your Installation Information


• Transferring the Messaging Server Installation Files


• Configuring an Existing Directory Server (if applicable)

• Using Express Installation


• Using Typical Installation


• Using Custom Installation


• Silent Installation


• Running the Setup Program


• Uninstalling Messaging Server Components

At this point, you can install only the Netscape Console, which would run as a stand-alone Java application, or you can install both the Administration Server and Messaging Server which also include the Netscape Console:

• Choose option 1 if you want to host the Messaging Server on this machine.
• Choose option 2 to if you only want to administer a server installed on a remote machine. For example, if you are using a Windows NT machine and want to administer a Messaging Server hosted on another machine (Unix or NT), you need to install only the Netscape Console.

Determine the installation level you want to use: Express, Typical, or Custom.

Determine the name and path of the directory in which you want the server(s) to be installed. For example, /usr/netscape/server4/default. Be sure that this is a different directory than the Directory Server 3.x server-root, if installed on the same machine.

Choose one or more of the following:

• Netscape Server Family Core Server Components


• Netscape Directory Suite


• Netscape Administration Suite


• Netscape Messaging Suite

If you selected the Netscape Directory Suite, the installation program asks you to supply an administrator for the Configuration Server. The recommended value is:

For more information, see the Directory Server 4.0 documentation and following sections in this document.

• Configuration Server Administrator


• Choosing a Configuration Directory Server

If you selected the Netscape Directory Suite, the installation program asks you to supply an the DN (distinguished name) of the account who has write access to the Configuration Sever Directory. The default is:

It is recommended that you use the value as you entered previously for the Netscape Configuration Directory Server Administrator ID.

A fully qualified host name has the following syntax: host.domainname. For example:

Where msghome is the machine host name and airius.com is the domain name.

This is the user ID or distinguished name of the administrator who has access privileges to modify the LDAP configuration of various Netscape servers. See Netscape Administrator User for additional information.

For example:

(Unix only) The Netscape Server User and Group Account

This is the Unix user and group account under which Messaging Server will run. The default user ID for both User and Group is nobody because that user and group is assumed to exist on all Unix systems. Netscape recommends that rather than using the nobody default, you create a new user ID and group for running your servers, for example, nsuser and nsgroup.

This is the entry in the Configuration Server Directory where management information for your servers is to be stored. You supply this information when you prepare a Directory Server 3.x for a Messaging Server 4.1 installation or when you install Directory Server 4.0. You must grant the Configuration Administrator write access to the to this domain before you can install the Administration Server and Messaging Server.

This is the address to which system-generated messages regarding Messaging Server will be sent. See Postmaster account for additional information. This address uses the following syntax:

For example: JSmith@airius.com

The Webmail end user admin account resides on the Users and Groups directory server and has privileges to manage the Webmail preferences of any Messaging Server user. Be sure to enter a user ID (uid) and not a DN (distinguished name).

• It creates an account for the specified user ID immediately under the User and Groups base DN (User and Groups suffix).
• It adds access control information (ACI) to the Users and Groups base DN that allows the Webmail End User Admin write access to the Webmail attributes of all users.

When you install the Netscape Core Package, you can specify one or all of the following subcomponents:

• Netscape Server Family Core Components


• Netscape Core Java classes


• Java Runtime Environment

If you have elected to install the Administration Suite, you can specify one or both of the following subcomponents:

• Netscape Administration Server


• Netscape Console

If you have elected to install the Messaging Suite, you can specify one or more of the following subcomponents:

• Netscape Messaging Server


• Netscape Messaging Multiplexor


• Netscape Messaging Server Mailstone Tools

If you selected the Netscape Directory Suite, the installation program asks you to supply the following information in addition to options described in the Express Installation Checklist:

• Do you want to register this software with an existing Netscape configuration directory server?


• Do you want to use another directory to store your data?


• Directory server network port


• Directory server identifier: Suffix [o=suffix]


• Administration Domain [domainname]

• Configuration Server Administrator


• Choosing a Configuration Directory Server

Select a port number that is currently available — one that is not being used by any other process. (The Administration Server must listen on a reserved port not used by any of your other Netscape servers or other applications.) Netscape recommends that you select a port number with a value between 1024 and 65535.

(Unix only) This is the user under which that the Administration Server runs. The default and recommended value is root.

• IP address that the Administration Server binds to
• Server Administrator ID [admin]


• Server Administrator password


• Messaging Server Domain


• Messaging Server Hostname


• Messaging Server Identifier


• Messaging Server User Account [mailsrv]


• Messaging Server SMTP network port [25]


• Messaging Server POP3 network port [110]


• Messaging Server IMAP4 network port [143]


• Webmail port


• Message Queue [server-root/msg-instance/queue]


• Message Store [server-root//msg-instance/store]


• Postmaster's DN

If you selected the Netscape Directory Suite, the installation program asks you to supply the following information in addition to options described in the Express Installation Checklist and Typical Installation Checklist:

• Whether to configure this directory server to use replication


• Whether to install the sample entries and in what location


• Whether to disable schema checking

• Configuration Server Administrator


• Choosing a Configuration Directory Server

This is asked if you chose to install the Administration Server. The default is admin. This value should be the same value you entered for the Configuration Server Administrator. For more information, see Configuration Server Administrator.

This is the domain name associated with the Messaging Server. This entry ensures that messages sent to this domain are routed properly. The domain name must be a fully qualified domain name (FQDN). For example, airius.com.

This is the name of the machine on which the Server resides and executes commands. If you are installing Messaging Server on a machine that has multiple host names, you should select the Custom Installation option to specify which host name you want to use. For details, see Using Custom Installation.

This is the user ID under which Messaging Server 4.1 will run. The default is mailsrv. See Messaging Server User for additional information.

This is the name that identifies this instance of the Messaging Server. Each instance of the Messaging Server must have a unique identifier, called a serverID. The installation program automatically adds the prefix msg- to the name you supply. For example, if you name the server instance tango, the installation program creates the serverID, msg-tango.

• tango-primary


• tango-airius


• tango_airius-mkt

• tango.primary


• tango.airius.com


• tango$arius>mkt

This is the network port on which the Messaging Server listens for SMTP connections. The default port is 25.

This is the network port on which the Messaging Server listens for POP3 connections. The default port is 110.

This is the network port on which the Messaging Server listens for IMAP4 connections. The default is port 143.

This is the path to the temporary holding area (message queue) for receiving incoming messages before they are stored in the targeted mail folder or mailbox. You must specify the absolute path name.

This is the path to the message storage area to which messages will be written and from which they will be retrieved. You must specify the absolute path name for this directory.

This is the distinguished name (DN) of the group account to which system-generated messages regarding Messaging Server will be sent. By default the postmaster account is created as cn=postmaster under the User and Groups suffix. See Postmaster account for additional information.

In this example, note that:

• If ou=mygroup does not exist in your directory, the installation program will create it.
• If you specify a DN component other than "ou", the component you specify must exist in your directory under that base DN. Otherwise, the installation program will fail when it attempts to set up the Postmaster account.

This is the network port on which the Messaging Server listens for Webmail connections. The default port is 80.

• On Unix, the installation program prompts you to save or delete the cache file. Choose save if you want to run a silent installation at a later time.
• On Windows NT, by default, the installation program does not save the cache file. To save the cache file on Windows NT, you must run the installation program with the -k command line option.

For example:

Choose Run and enter setup -k

or, on a DOS command line, type setup -k

To use the cache file for a fast installation of another Messaging Server 4.1 instance, follow these steps:

1. Copy the install.inf cache file to the installation directory that you are using for the new installation.
2. Review and edit the install.inf cache file as necessary.

You will probably want to change some of the parameters and specifications in the cache file. For example, the host name for this installation will likely be different than the host name recorded in the cache file. Remember that the parameters listed in the cache file will be automatically applied to this installation.

3. Run setup with the -s -f filename options.

The filename is the full path identifying the cache file you wish to use. For example:

setup -s -f /usr/netscape/server4b/setup/install.inf

1. Review the contents of the licence.txt text file.

As part of the installation process, you will be asked if you agree to the terms listed in this file.

2. Login as or setuid to root (Unix) or administrator (Windows NT).

You must have superuser privileges (that is, be logged in as root or administrator) to run the installation program.

3. Be sure to make your current directory the installation directory. For example:

cd /tmp/msg4install

4. To run the setup program from the command line, type:

setup

(On Windows NT you can also double-click setup.exe.)

The installation program displays a Welcome Message.

5. Press Enter (or on NT Windows, click Next) to continue. The license agreement is displayed.
6. Read the license agreement and type y to accept it and continue.

Note: You have to actually enter y because the default is no. (If you answer no, the installation program will stop.)

7. Select the software that you want to install.

The default is to install Messaging Server and Netscape Console.

Or, you can install just the Netscape Console without Messaging Server if you only want to administer a server installed on a remote machine. For example, if you are using a Windows NT machine and want to administer a Messaging Server hosted on another machine (Unix or NT), you need to install only the Netscape Console.

(The following instructions assume that you install both Messaging Server and Netscape Console.)

8. Select the type of installation you wish to use.

The same software is installed with each type of installation. The difference between the types of installations is the number of choices you have to make during the installation process. The three levels are:

• Express Installation. This level is the simplest to run, but provides the fewest configuration options. For a complete list of these options, see Using Express Installation.


• Typical Installation. This level provides a balance between configuration options that you are asked to specify and those that are supplied automatically. This is the default level. For a complete list of these options, see Using Typical Installation.


• Custom Installation. This level provides the greatest amount of configuration options and is intended for expert users. For a complete list of these options, see Using Custom Installation.



After you select the installation level, you enter your installation and configuration information, according to the type of installation you selected. For more detailed descriptions of what to enter for each prompt, refer to the appropriate installation checklist starting on page 36.

9. Specify the directory where you want to install the Messaging Administration Server software:

usr/netscape/server4

or

c:\netscape\server4

Do not specify the same server-root that is used by Directory Server 3.x if it is installed on this machine.

Note: (Unix only) You can create multiple server-roots by installing into multiple directories on the same machine.

10. Specify the components that you wish to install.

Netscape Server Family components:

The choices are:

Netscape Server Family Core Components. These are the shared server libraries, Netscape Core Java classes, and the Java Runtime Environment. Both Administration and Messaging Server require installation of these libraries.

Netscape Directory Suite. Includes Directory Server 4.0 Server and bundled components. See the Directory Server 4.0 Installation Guide for details.

Note: A Directory Server is required to run Messaging Server 4.1. The Messaging Server 4.1 installation program includes Netscape Directory Server 4.0. If you do not already have a Directory Server installed, you should install Netscape Directory Server 4.0 during the Messaging Server installation process.

Administration Services. Includes the Administration Server and Netscape Console. Messaging Server requires installation of Administration Services.

Netscape Messaging Suite. Includes Messaging Server and two optional packages that you can also select which are the Netscape Messaging Multiplexor and Netscape Messaging Server Mailstone Tool. If you choose Netscape Messaging Suite (or "All"), you are asked if you wish to install the two optional packages.

Note: The next options you see will vary according to the choices you make. For example, if you choose to install Netscape Directory Suite, you will be prompted by the Netscape Directory 4.0 installation program.

11. If you chose to install the Netscape Server Family Core Components, choose from the following options:
• Netscape Server Family Core Components


• Netscape Core Java classes


• Java Runtime Environment


12. If you chose to install the Netscape Directory Suite components, choose from the following options:
• Netscape Directory Server


• Netscape Directory Server Console



See the Directory Server 4.0 Installation Guide for details.

13. If you chose to install the Administration Services components, choose from the following options:
• Netscape Administration Server


• Netscape Console


14. If you chose to install the Netscape Messaging Suite components, choose from the following options:

Netscape Messaging Server. Installs Netscape Messaging Server 4.1.

Netscape Messaging Multiplexor (optional). Lets you set up a server to forward mail. This is a Messaging router with no users that can be used as backup server in case of a problem with your primary Messaging Server.

Netscape Messaging Server Mailstone Tool (optional). A utility that lets you monitor and benchmark Messaging Server system performance.

15. Specify the fully qualified domain name of the machine where the Messaging Server is to be installed.

For example: msghome.airius.com

16. (Unix only) Choose the Unix user and group accounts under which Messaging Server will run:
• System User [nobody]:


• System Group [nobody]:



Netscape recommends that rather than using the nobody default, you create a new system user ID and system group to run Messaging Server. For example, mailsrv for the user and nsgroup for the group. See Messaging Server User for additional information.

The group should be same as the one used for the Directory Server so that Messaging Server has access to the configuration and security data in the server-root of the Messaging Server instance you are installing. For security reasons, Netscape recommends that this user ID not be given any privileges elsewhere on the system. See Netscape User and Group for additional information.

17. If you chose to install the Netscape Directory Suite, the Netscape Directory Server 4.0 installation program will be invoked and will ask you to supply some or all of the following information (for details, see the Directory Server 4.0 Installation Guide):
• To register this software with an existing Netscape configuration directory server (requires host name and port number, suffix, and administrator ID and password)


• To store user and group information on the directory (requires host name and port number, suffix, and administrator ID and password)


• DN to use for that directory server Directory Manager DN


• Administration Domain


• Directory server identifier


• Configure the directory server for replication


• Install sample entries and install location


• Turn off schema checking


18. Enter the non-secured LDAP URL of the Configuration Server Directory.

This is the URL of the Configuration Directory that this instance of Messaging Server will use. This value must be entered in the form:

ldap://hostname.domain:port

For example:

ldap://msghome.airius.com:389

19. Specify the Administration Domain of the Configuration Server Directory where your server configuration information is to be stored. This is the domain of your organization, for example: airius.com. You should use the same domain name that you used for your Configuration Server.

You need to grant write access to this domain to the Configuration Server Administrator. (If you ran the dssetup utility, write access to this domain was granted for you automatically. See Configuring an Existing Directory Server.)

Netscape recommends that you accept the proposed default value.

20. Enter the user ID or Distinguished Name of the administrator who is authorized to access the Server Configuration Directory at:
[ldap://hostname.domain.com:port/]

to accept the default name (admin). You must supply a password.

Note: If you ran dssetup (see Configuring an Existing Directory Server), this is the Configuration Administrator ID that you entered. See Configuration Server Administrator for additional information.

21. Enter the user ID or Distinguished Name of the administrator who has write access to the User and Group Server directory at:

ldap://hostname.domain.com:port/o=domain

This is the Users and Groups administrator. This administrator must have write access to the Users and Groups Directory Server. See User Directory Administrator for additional information. The corresponding default and recommended value for this account is:

cn=Directory Manager

You must supply a password.

22. Supply the port that the Administration Server listens to. The Administration Server is separate from any of your application servers since it listens to a different port.

This is the port that the Administration Server is to use. It must be a unique port that no other application uses. Netscape recommends that you choose a port number between 1024 and 65535 on which to run your Administration Server. Do not specify a port number on which you plan to run an application server.

After you select a port number which will not be used for anything else, make a note of it because you will to need to refer to it later.

23. Enter a specific IP address to bind the Administration Server to or press Enter to accept the default address.

If the host machine has multiple IP addresses, you can specify which address the Administration Server listens to.

24. Enter user ID of the Server Administrator or press Enter to accept the default name (admin). You should use the same value that you used for the Configuration Server Administrator. You must also supply and confirm a password.

Server administration is restricted to people who know the Server Administrator user ID and password, and to people who access the server from a host you specify. When you open the Netscape Console, it will prompt you for the Server Administrator user ID and password.

25. (Unix only) Supply the user ID under which the Administration Server is to run:

This user ID should be different than the ID used to run Messaging Server and other servers. Netscape recommends that you run the Administration Server as root so that you will be able to use Netscape Console to start and stop the servers. See Administration Server User for additional information.

26. This step is necessary only if the installation program detects a previous Messaging Server 3.x or 4.x installation on this machine and you chose to install the new server into a different directory than the existing 4.x server-root. In this case, the installation program asks if you want to migrate server configuration parameters from the existing 3.x or 4.x server to your new server instance in the new server-root.

If you answer yes:

• For 4.x servers: The configuration information from an existing 4.x Messaging Server will be applied to the server you are now installing. Messages stored on the existing server will not be migrated to the new server. You can, however, use the same mail store used in a previous Messaging Server installation.
• For 3.x servers: You will be asked if you wish to migrate just configuration information, or also mailboxes and message queues from the existing 3.x server to your new 4.1 server. If you choose to migrate the mailboxes and message queue, the process could take a long time. You do not need to migrate at this time, however, because you can do so at a later time using the command line upgrade utility as explained in Using the Installation Program to Migrate 3.x Mailboxes to 4.1. (Keep in mind that if you migrate mailboxes and messages, no mailbox will be created for users that have never been sent any messages. By sending them a welcome message, you can force creation of their mailboxes.)

Note: If your 3.x server uses non-default directories to store mailboxes and message queues, do not migrate them at this time. Instead, wait until the installation is complete, and then run the upgrade utility from the command line as explained in Using the Installation Program to Migrate 3.x Mailboxes to 4.1.

27. Create a new server instance. You will need to have the following information handy:

• The account under which the Administration Server is to run (the default is mailsrv on Unix, or system on Windows NT.)
• The user account to be notified of messages sent to postmaster.

You must create server instance before you can run Messaging Server. To continue, type y or press Enter.

28. Supply a specific domain name to use when performing functions such as routing and serving mail to and from messaging client applications, or press Enter to accept the default name:

For example: airius.com

Note: If you are installing Messaging Server on a machine with multiple domain names, the default value may not be what you want.

29. Supply a default host name. Enter a host name in the form:

hostname.domain

For example:

msghome.airius.com

Note: If you are installing Messaging Server on a machine with multiple host names, select the one of the host names listed. (The default value may not be the host name you want.)

30. Supply a serverID for the server instance you are creating now in the current server root.

For example, if you enter tango, the installation program creates a serverID for this Messaging Server instance named msg-tango. The server configuration and administration utilities depend on this information and you will refer to it later in the installation process.

31. Supply a user ID that Messaging Server will run under. The default is mailsrv.

This is the user ID that Messaging Server will run under. This should be a different user ID than the IDs entered for Netscape User (nobody) and the Administration Server (root). To prevent possible security problems, Netscape recommends that this user be a member of the Netscape Group that you specified earlier. See Messaging Server User for additional information.

On Unix, this user ID must already exist.

On Windows NT, if you use an existing Messaging Server User account (system is recommended), to ensure that Messaging Server will start when the installation program has completed:

• Open the User Properties window from the NT User Manager.


• Check "Password never expires"


• Uncheck "User Must Change Password at Next Logon"


32. If a valid postmaster account does not already exist, the installation program asks you to supply an email address.

This is the email address that serves as the postmaster account:

• If the account you specify is stored on the directory server used by this Messaging Server, you need only enter the user ID. For example, mailmaster.
• If the account resides on a different Directory Server or in a different domain, then you must enter a fully-qualified email address. For example, mailman@airius.com.

The user ID listed for the postmaster account does not yet have to already exist. See Postmaster account for additional information.

33. Enter a port number for SMTP to use.

The port number specified here must be a unique port that no other application is using. If the port is in use, you can either enter a different port, or accept the proposed default in which case you must kill whatever process is currently using that port before starting up Messaging Server.

If you choose (or accept) a port that is already in use, the installation procedure will warn you and ask if you wish to continue:

• You can use Control-B (Unix) or click Back (NT) to go back and select a different port.
• If you continue, you will not be able to start up this Messaging Server instance until the application using the port you specified has been shut down.

Note: When performing a Typical installation, this prompt is only displayed if the default port (25) is already in use.

34. Enter the port number for IMAP to use.

The port number specified here must be a unique port that no other application is using. If the port is in use, you can either enter a different port, or accept the proposed default in which case you must kill whatever process is currently using that port before starting up Messaging Server.

Note: When performing a Typical installation, this prompt is only displayed if the default port (143) is already in use.

35. Enter the port number for POP3 to use.

The port number specified here must be a unique port that no other application is using. If the port is in use, you can either enter a different port, or accept the proposed default in which case you must kill whatever process is currently using that port before starting up Messaging Server.

Note: When performing a Typical installation, this prompt is only displayed if the default port (110) is already in use.

36. (Unix only) This step is necessary only if sendmail is using a port designated for Messaging Server.

If sendmail is running and you answer:

• yes -- sendmail is halted and Messaging Server 4.1 is installed and then started.


• no -- Messaging Server 4.1 is installed, but it will not be started. You will later have to manually halt sendmail and then start Messaging Server.


37. Enter a port number for Webmail to use (the default is 80).

The port number you specify here must be a unique port that no other application is using. If the port is in use, you can either enter a different port, or accept the proposed default in which case you must stop whatever process is currently using that port before starting Messaging Server.

38. (Windows NT only) The installation program displays a warning message if you selected an installation directory located on a drive partition that is not formatted as NTFS (NT File System). It is recommended that, for improved performance, you choose an NTFS-formatted drive on which to install Messaging Server.

Note: If you click Back several times until you reach the installation directory option, your selections up to this point will be saved. You can then click Next several times to return to your current place in the installation procedure. If you click Cancel to exit the installation program, your selections will be lost.

39. Specify a directory where Messaging Server queues mail before delivering to individual mailboxes or other servers in the form:

server-root/serverID/queue

This directory should be secure enough to prevent any undesirable eavesdropping or tampering.

For example:

/usr/netscape/server4/msg-tango/queue

40. Specify a directory to locate user mailboxes to store email messages in the form:

server-root/serverID/store/partition/primary

This directory should be secure enough to prevent any undesirable eavesdropping or tampering and large enough to hold the e-mail messages of all the user accounts you intend to create on this server.

For example:

/usr/netscape/server4/msg-tango/store/partition/primary

41. Specify a Webmail end user admin account and password.

The Webmail end user admin account resides on the Users/Groups directory server and has privileges to manage the Webmail preferences of any Messaging Server user. Be sure to enter a user ID (uid) and not to enter a DN (distinguished name).

Note: If a Webmail End User Admin account does not exist, the installation program will create one and provide it with the required privileges.

42. Choose the server instances that you wish to start after the installation.

Note: Enter none if you do not want to start any of the servers.

43. Review the summary information that displays to make sure thy are correct. If you need to make corrections, you can use Control-B (or click Back on Windows NT) to return to previous screens.

When the list is correct, press Enter to continue.

Installation status messages are displayed as the servers are installed and configured.

44. Press Enter or type y to continue.

Status messages display as Messaging Server 4.1 is started and the installation program creates a cache file.

Note: If you ran an Express or Typical installation and the host name or domain name displayed in the summary information is not correct, run the installation program and select Custom Installation instead, then explicitly enter the correct information.

45. (Unix only) Either press Enter to keep the cache file or, type no to discard it.

Because this file contains user IDs and passwords that you may want to keep secure, by default, the installation program will the delete it. If, however, you choose keep the cache file (install.inf), you can use it as an installation template for other Messaging Server 4.1 instances as described in Silent Installation.

Note: On Windows NT, by default, the installation program does not save the cache file. To save the cache file on Windows NT, you must run the installation program with the -k command line option.

For example:

From the Start Menu, choose Run and enter setup -k

or, on a DOS command line, type setup -k

46. (Windows NT only.) The installation program asks you to shut down and restart the machine when the installation program completes. Netscape strongly recommends that you shut-down and restart. Otherwise, the server will be unstable.

1. Login as root (Unix) or administrator (NT).

(You must have superuser privileges (that is, be logged in as root or administrator) to run the uninstall program successfully.

2. Halt the server instance.

To halt the server instance, run the stop-msg utility. This utility is stored in the server-root/msg-instance directory. For example:

cd /usr/netscape/server4/msg-tango

stop-msg

3. Change to the server-root directory.

Change to the directory in which you installed the Administration and Messaging Servers. For example:

cd /usr/netscape/server4

4. Run the uninstall program.

From the command line, type uninstall (or in Windows NT, double-click uninstall.exe located in the directory where you installed Messaging Server 4.1 or choose Add/Remove Programs from the Control Panel).

The uninstall program then prompts you for the following information:

• Select the components you wish to uninstall (default: all) [All]
• Specify the Netscape Server Family Core components you wish to uninstall [1, 2]


• Specify the Netscape Administration Suite components you wish to uninstall.


• Specify the Netscape Messaging Suite components you wish to uninstall.


• Configuration Admin ID or DN [admin]


• Directory Server Suite (if installed)


• Configuration Admin Password


• Remove Mail Queue and Message Store for this server instance [Yes]?