Netscape Messaging Server 3.5 README
Netscape Messaging Server 3.5
This file was last updated on July 08, 1998.
Thank you for choosing Netscape Messaging Server 3.5. This file contains
installation and configuration instructions only. Please see the release
notes for a description of new features and known problems, and other
information about this release.
NOTE: Please install Messaging
Server 3.54 instead of Messaging Server 3.5. The 3.54 release
includes all fixes in the 3.52
patch release, as well as a fix for the Million
Question vulnerability in SSL. This document is still applicable
to Messaging Server 3.54, except where the Release
Notes specify differences.
This release of Messaging Server is available on the following platforms:
-
Windows NT 3.51 (requires Service Pack 5)
-
Windows NT 4.0 (requires Service Pack 3)
-
Sun SPARC Solaris 2.5.1
-
Sun SPARC Solaris 2.6
-
Silicon Graphics IRIX 6.2
-
Hewlett-Packard HP-UX 10.10
-
Hewlett-Packard HP-UX 10.20
-
Digital Unix 4.0b
Note: In order for Messaging Server 3.5 to run properly on the
Digital Unix platform, you will need to install the OS patches in Patch
Kit-0004. To obtain Patch Kit-0004, click here
-
IBM AIX 4.1.5
-
IBM AIX 4.2
Note: In order for Messaging Server 3.5 to run properly on the
IBM AIX platform, you will need to install OS patches as follows:
-
AIX 4.1.5 with these patches:
-
APAR IX64176 (libsvld.a)
-
APAR IX62194 (DCE patch for Sybase/Informix)
-
AIX 4.2.0 with these patches:
-
APAR IX64183 (libsvld.a)
APAR IX62194 (DCE patch for Sybase/Informix)
-
APAR IX60895 (snprintf symbol in libc.a)
-
AIX 4.2.1 without any patches
To obtain patches (APAR's) from the IBM Software Support Fix Distribution
website, click here.
Contents of this README file
How to report problems
If you are a test-drive customer and are having problems with Messaging
Server 3.5, please click here
to send an email to our technical support staff. If you are affiliated
with an educational institution and you are using the product for free,
click here. You can also
search our online
database for answers to your questions.
If you have purchased Messaging Server 3.5, you can either search our
online
database for answers to your questions or use the up-to-date contact
information and support phone numbers provided there to contact our technical
support staff.
How to get more information
For complete instructions on installing, deploying, and administering Messaging
Server 3.5, consult these documents:
-
Messaging Server 3.0 Installation and Deployment Planning Guide
-
Messaging Server 3.0 Administrator's Guide
-
Managing Netscape Servers
An online version of the 3.0 Administrator's Guide, updated for
Messaging Server 3.5, is provided with Messaging Server 3.5 software. Click
the Help button on any Messaging Server or Administration Server form to
access the online Help. (The online version of the Administrator's Guide
is also provided in the online
database for Messaging Server 3.5.)
You can also search our online
database for more documents relating to Messaging Server 3.5.
Before installing Messaging Server 3.5
To manage information about users and groups for use with Netscape Messaging
Server 3.5, you can use either an LDAP-compliant Directory Server such
as the Netscape Directory Server or a local database that comes bundled
with the Administration Server (installed with the Messaging Server). LDAP
(Lightweight Directory Access Protocol) is the Internet standard directory
service protocol designed to store and retrieve information about users,
groups and other network data. Sites that wish to publish user and group
information for use by mail clients such as Netscape's Communicator, or
who need to deploy multiple Netscape Servers managed by a single administration
framework, must use a Directory Server. The local database is intended
primarily for sites running a stand-alone Netscape server.
Important: If you plan to use this Messaging Server 3.5 with
the Netscape Directory Server, you must install the Directory Server before
installing the Messaging Server. (See Installing
the Directory Server for instructions.)
Before you install Netscape Messaging Server 3.5, ensure that:
-
If you are upgrading from Mail Server 2.0, Messaging Server 3.0x, or a
beta version of Messaging Server 3.5, you should read the next section,
"Upgrading from earlier versions."
-
You are using Netscape Navigator 3.0 (or later) to configure and administer
the Messaging Server.
-
DNS is operating correctly and your machine name is configured correctly.
-
You create new SuiteSpot user and group accounts--for example, nsuser and
nsgroup.
-
You create a Unix user account to run the Messaging Server--for example,
mta--and that this account has the SuiteSpot group account you just created
(for example, nsgroup) as its primary group.
-
If you are using the Directory Server to maintain user and group accounts,
you know the machine name and port number of the Directory Server.
-
If you are using the Directory Server to maintain user and group accounts,
you know the base DN (Distinguished Name) for the Messaging Server--for
example, o=Ace Industry, c=US. (Click here
for more information on DNs.) (It is also helpful to know the "Directory
Bind DN & Bind password.")
-
If you are using HP-UX, you must make sure you have at least 15 kilobytes
of free space in your / (root) and /usr partitions. If
you don't do this, the Messaging Server 3.5 installation will fail without
displaying any error or warning messages.
Upgrading from earlier versions
on Unix
If you are already using Mail Server 2.0 (2.0, 2.01, or 2.02), Messaging
Server 3.0 (3.0 or 3.01), or a beta version of Messaging Server 3.5, follow
the instructions in this section before installing Messaging Server 3.5.
Important: Upgrading from beta versions of Messaging Server 3.0
is not supported.
If you have either a Mail Server 2.0 or a version of Messaging Server
3.0x somewhere on your system, the installation will detect it. If this
is the case, the installation script will ask if you want to use the mailbox
and postoffice directories that you already have on the system. (It is
recommended that you use the same directories as your current 2.x or 3.x
installation.) The following sections describe the implications of the
answer you provide to this question.
Important: It is recommended that before
starting the installation, you save the mailbox and postoffice directories
into a temporary backup area and retain the file permissions of all files
in them.
It is recommended that POP users download existing messages from their
mailboxes prior to installing Messaging Server 3.5. Any messages that remain
in users' mailboxes will be delivered as new messages after upgrading.
During the upgrade, the message format is changed, which causes these messages
to be downloaded again. (In effect, the POP UIDs are changed.)
Upgrading from a Mail Server 2.0 installation
The actual upgrade from Mail Server 2.0 does not occur during the installation
of Messaging Server 3.5. It occurs afterwards. However, the choices you
make during the installation have a bearing on how you upgrade later. After
installation, you can take one of two approaches to upgrade from Mail Server
2.0.
Important: Be sure to stop the Mail Server 2.0 before installing
Messaging Server 3.5.
Some notes on upgrading from Mail Server 2.x to Messaging Server 3.5
If you plan to upgrade from Mail Server 2.x to Messaging Server 3.5, note
that Netscape recommends "in place" upgrades--that is, upgrades in which
the same post office and mailbox directories are used from 2.x to 3.5.
If you choose not to perform an "in place" upgrade, be sure to process
all messages in the queue prior to upgrading. Follow these steps:
-
Stop the Mail Server 2.x before installing Messaging Server 3.5.
-
Check and clear the message queue.
Use mailq to check the queue; use processq to clear
the queue.
-
Perform the Messaging Server 3.5 installation.
-
Use the mta-migrate utility to complete the upgrade.
Important: If you do attempt to upgrade from Mail Server
2.x to Messaging Server 3.5 with messages remaining in the message queue,
the installer will detect these messages and offer to deliver the queue.
The Yes option does not work, and will result in a failed installation.
Important: When upgrading from Mail Server 2.x, you must use
the same Unix username for the Messaging Server as you did for Mail Server
2.x. The upgrade will not work if you attempt to do an "in place" upgrade
with a different username.
Upgrading via "Migrate from previous version" link
You will find this URL in the Server Administration page when you connect
as a user with administrative privileges. This provides a simple approach
for moving all of your users and their mailboxes to the Messaging Server
3.5. To use this approach, during installation you must
choose the same mailbox and postoffice directories as you use
with Mail Server 2.0.
The appropriate time for upgrading is immediately
after you finish installing Messaging Server 3.5. At the end of installation,
you are asked if you want to start the Messaging Server. It is advisable
at this point that you do not start the Messaging Server and that
you proceed with the upgrade process as outlined below.
To complete the upgrade:
-
Go the Administration Server's Server Administration
page.
-
Click "Migrate from previous version."
-
Enter the 2.x server root where Mail Server 2.0 is
installed.
-
In the Choose Server to Import window, click Netscape
Mail Server.
As soon as you click this option, a browser window
will open to show the progress of the user and mailbox migration. You should
save the contents of this browser window for later analysis. This output
will indicate if there was a problem migrating some of the users/mailboxes.
For each user who was successfully migrated you will see a message similar
to this one:
Added: cn=Join Smith, o=nscp,c=us
Mailbox migrated in /var/spool/mailbox/jsmith
If the mailbox is not migrated properly, you will
see a warning from the output as follows:
Added: cn=John Smith, o=nscp, c=us
Warning: Can not rename mailbox
Warning: Upgrade of mailbox failed for jsmith
For users who fail on mailbox migration, diagnose
the problem using the following steps:
-
Look up the mailbox directory for the user. For example:
cd /var/spool/mailbox/jsmith
-
Look for "inbox" under the user's
mailbox directory. Check for directories of "in" and "inbox" under the
user's mailbox. If both exist, manually copy 2.x messages from the "in"
directory to the "inbox" directory, and then remove the "in" directory.
-
If nothing is found in the user's mailbox, go to
the backup mailbox. For example:
cd /var/spool/mailbox.backup/john_smith
Note that Mail Server 2.x mailboxes are based
on user names whereas Messaging Server 3.0 mailboxes are based on uid.
-
Manually restore the Messaging Server 3.5 mailbox.
For example:
su
cp -r /var/spool/mailbox.backup/jojn_smith/in
/var/spool/mailbox/jsmith/inbox
chown -R mta:nsgroup /var/spool/mailbox/jsmith
Important: Remember to change ownership of
the mailbox for MailUserName in Messaging Server 3.5 after the restoration.
Note: If a user account is either tagged
as a Unix Delivery or Program Delivery in Mail Server 2.0, then the second
line in the above example output will be missing for these accounts. You
must analyze the output of this process to identify these users before
you restart Messaging Server 3.5.
Via MTA-migrate
You can find MTA-migrate in the <server-root>/bin/mail/server/bin
directory. You must use MTA-migrate if any
of the following circumstances applies to your situation:
-
If you chose a mailbox (and/or) postoffice directory that is different
from the 2.0 mailbox and post office during the installation.
-
If you already have a Directory Server installed and you want to move 2.0
user information into it.
-
If you want the distinguished name for user entries
in a form other than "cn=%cn, %basedn" such as "cn=John Smith, o=Ace Industry,
c=US".
-
If you want to migrate users and the mailbox in separate steps.
Caution: If you are using a Directory Server, you must supply the
bind password in the command line. This password could potentially be visible
to all users in the system while the MTA-migrate tool is running. See the
Administrator's Guide for more information on the options you can
use with MTA-migrate.
Upgrading a previous 3.0x installation
During the installation, you must choose the same user and group IDs that
you used for the previous installation for running this release of the
Messaging Server. Also, supply the same mailbox and postoffice directories
as the ones you used for the previous installation.
If you were using a local directory database with your previous
installation, populate your new directory database with the user entries
you had in that installation. Now start the Messaging server.
If you were using Single Copy Message Store in your previous installation,
you must use the same mailbox directory for your Messaging Server 3.5 installation.
For this reason, the Messaging Server 3.5 upgrade installer will not allow
you to choose a different mailbox directory in this case.
Installing Messaging Server
3.5 on Unix
The procedure for installing Netscape Messaging Server 3.5 varies somewhat
depending on whether you intend to use a local database or the Netscape
Directory Server to manage user and group accounts. If you plan to use
a local database, follow the steps in the next
section. If you plan to use the Netscape Directory Server, click here.
Important: The instructions provided here are sufficient for
installing Messaging Server 3.5. However, a much fuller discussion of installation
and deployment issues is provide in the Installation and Deployment Planning
Guide. It is strongly recommended that you consult the guide before attempting
to install Messaging Server 3.5.
Installing for use with a
local database
To install Messaging Server 3.5, follow these instructions:
-
Log in as root.
-
Uncompress the tar file by typing the following command:
tar xvf message.tar
Note: Make sure you follow the download instructions carefully
to obtain the tar file appropriate for your Unix platform; the
tar file name will reflect the platform and version for which
it is intended.
-
Run this command: ./ns-setup
-
Follow the onscreen instructions.
After the installation is complete, you can create new users. For instructions,
see the Messaging Server 3.0 Administrator's Guide.
Installing for
use with Netscape Directory Server
If you are planning to use the Directory Server to maintain user and group
accounts, follow the instructions in the following sections in order:
Installing the Directory Server
If you plan to use the Directory Server to maintain user and group accounts,
you must install the Directory Server before installing the Messaging Server.
You can install the Directory Server from the Messaging Server CD, or you
can download it from the Netscape
download site. Please see the README file provided with the Directory
Server product.
Configuring the Directory Server
If you haven't already configured the SuiteSpot 3.0 Administrator's ID
during the Directory Server installation, you will need to do so before
installing the Messaging Server. Follow these steps:
-
From the Server Adminstration page, choose the Directory Server.
-
Choose System Settings|On/Off to turn on the Directory Server.
-
Choose Database Mgmt|SuiteSpot 3.5 Settings. In the SuiteSpot 3.0
Settings form, follow these steps:
-
Confirm the SuiteSpot 3.5 Administrator's ID.
-
Enter a password for the SuiteSpot 3.0 Administrator's ID.
-
Enter a password for the Directory Server's Unrestricted User.
-
Click OK.
-
When the "SuiteSpot 3.5 Settings Updated" page appears, write down the
URL for the Directory Server and the Administrator's ID. (You'll need this
information later when installing the Messaging Server.)
Completing the Messaging Server
installation
To install Messaging Server 3.5, follow these instructions:
-
Log in as root.
-
Uncompress the tar file by typing the following command:
tar xvf message.tar
Note: Make sure you follow the download instructions carefully
to obtain the tar file appropriate for your Unix platform; the
tar file name will reflect the platform and version for which
it is intended.
-
Run this command: ./ns-setup
-
Follow the onscreen instructions.
Important: The installation program asks you to enter an Administrator's
ID for the Messaging Server. Be sure to use the same Administrator's ID
as you did for the SuiteSpot 3.0 Administrator's ID. The program also asks
for the URL for the Directory Server. Enter the URL that you copied from
the "SuiteSpot 3.0 Settings Updated" page.
After the installation is complete, you can create new users. For instructions,
see the Messaging Server 3.5 online help.
Uninstalling Messaging Server
3.5 on Unix
To uninstall Messaging Server 3.5, follow the instructions for your Unix
platform below:
Solaris
To remove the Messaging Server:
-
Login as root.
-
Go to the /etc directory.
Enter: cd /etc
-
Stop the Netscape Messaging Server.
Enter ./NscpMail stop
-
Remove the following files.
Enter: rm netscape.mail.conf NscpMail mailbin nsmail.als
-
Go to the /usr/lib directory.
Enter: cd /usr/lib
-
Remove the following files.
Enter: rm libNSmail.so libNSmatch.so libldap*.so liblcache*.so
-
Rename the sendmail.bak file to sendmail.
Enter: mv sendmail.bak sendmail
-
Go to the /etc/init.d directory.
Enter: cd /etc/init.d
-
Restart the sendmail daemon.
Enter: ./sendmail start
-
Go to the /etc/inet directory.
Enter: cd /etc/inet
-
Copy the inetd.conf.bak file to inetd.conf.
Enter: cp inetd.conf.bak inetd.conf
-
Obtain the process ID (pid) of the inetd daemon.
Enter: ps -ef | grep inetd
-
Read the newly renamed file into memory.
Enter: kill -1 <pid of inetd>
-
Go to the /var directory.
Enter: cd /var
-
Change the permissions for the mail directory.
Enter: chmod g-s mail
-
Go to the directory where you installed the post office and mailbox.
For example: cd /var/spool
-
Remove the postoffice and mailbox directories.
Enter: rm -rf postoffice mailbox
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save, or email in the mailbox
directory, this will remove it.
Warning: The following steps remove the Netscape Administration
Server. If you have other Netscape servers installed that will continue
to use the Administration Server, do not perform the following steps.
To remove the Netscape Administration Server:
-
If you have the Messaging Server SNMP subagent running, stop it via the
Administration Server interface.
-
If you have the SNMP master agent running, stop it via the Administration
Server interface.
-
Go to the server root (the directory where you installed the server).
For example: cd /usr/netscape/suitespot
-
Stop the Administration Server.
Enter: ./stop-admin
It may take a few seconds to come down.
-
Go to the parent of the server root.
For example: cd /usr/netscape
-
Remove the server root.
For example: rm -rf suitespot
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save this will remove it.
IRIX
To remove the Messaging Server:
-
Login as root.
-
Go to the /etc directory.
Enter: cd /etc
-
Stop the Netscape Messaging Server.
Enter ./NscpMail stop
-
Copy the inetd.conf.bak file to inetd.conf.
Enter: cp inetd.conf.bak inetd.conf
-
Obtain the process ID (pid) of the inetd daemon.
Enter: ps -ef | grep inetd
-
Read the newly renamed file into memory.
Enter: kill -1 <pid of inetd>
-
Remove the following files.
Enter: rm netscape.mail.conf NscpMail mailbin nsmail.als
-
Go to the /usr/lib directory.
Enter: cd /usr/lib
-
Remove the following files.
Enter: rm libNSmail.so libNSmatch.so rm libldap*.so liblcache*.so
-
Rename the sendmail.bak file to sendmail.
Enter: mv sendmail.bak sendmail
-
Go to the /etc/init.d directory.
Enter: cd /etc/init.d
-
Restart the sendmail daemon.
Enter: ./mail start
-
Go to the /var directory.
Enter: cd /var
-
Change the permissions for the mail directory.
Enter: chmod g-s mail
-
Go to the directory where you installed the post office and mailbox.
For example: cd /var/spool
-
Remove the postoffice and mailbox directories.
Enter: rm -rf postoffice/ mailbox
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save, or email in the mailbox
directory, this will remove it.
Warning: The following steps remove the Netscape Administration
Server. If you have other Netscape servers installed that will continue
to use the Administration Server, do not perform the following steps.
To remove the Netscape Administration Server:
-
If you have the Messaging Server SNMP subagent running, stop it via the
Administration Server interface.
-
If you have the SNMP master agent running, stop it via the Administration
Server interface.
-
Go to the server root (the directory where you installed the server).
For example: cd /usr/netscape/suitespot
-
Stop the Administration Server.
Enter: ./stop-admin
It may take a few seconds to come down.
-
Go to the parent of the server root.
For example: cd /usr/netscape
-
Remove the server root.
For example: rm -rf suitespot
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save this will remove it.
HP-UX
To remove the Messaging Server:
-
Login as root.
-
Go to the /etc directory.
Enter: cd /etc
-
Stop the Netscape Messaging Server.
Enter ./NscpMail stop
-
Copy the inetd.conf.bak file to inetd.conf.
Enter: cp inetd.conf.bak inetd.conf
-
Obtain the process ID (pid) of the inetd daemon.
Enter: ps -ef | grep inetd
-
Read the newly renamed file into memory.
Enter: kill -1 <pid of inetd>
-
Remove the following files.
Enter: rm netscape.mail.conf NscpMail mailbin nsmail.als
-
Go to the /usr/lib directory.
Enter: cd /usr/lib
-
Remove the following files.
Enter: rm libNSmail.sl libNSmatch.sl rm libldap*.sl liblcache*.sl
-
Go to the /usr/sbin directory.
Enter: cd /usr/sbin
-
Rename the sendmail.bak file to sendmail.
Enter: mv sendmail.bak sendmail
-
Restart the sendmail daemon.
Enter: ./sendmail -bd -q15m
-
Go to the /var directory.
Enter: cd /var
-
Change the permissions for the mail directory.
Enter: chmod g-s mail
-
Go to the directory where you installed the post office and mailbox.
For example: cd /var/spool
-
Remove the postoffice and mailbox directories.
Enter: rm -rf postoffice/ mailbox
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save, or email in the mailbox
directory, this will remove it.
Warning: The following steps remove the Netscape Administration
Server. If you have other Netscape servers installed that will continue
to use the Administration Server, do not perform the following steps.
To remove the Netscape Administration Server:
-
If you have the Messaging Server SNMP subagent running, stop it via the
Administration Server interface.
-
If you have the SNMP master agent running, stop it via the Administration
Server interface.
-
Go to the server root (the directory where you installed the server).
For example: cd /usr/netscape/suitespot
-
Stop the Administration Server.
Enter: ./stop-admin
It may take a few seconds to come down.
-
Go to the parent of the server root.
For example: cd /usr/netscape
-
Remove the server root.
For example: rm -rf suitespot
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save this will remove it.
AIX
To remove the Messaging Server:
-
Login as root.
-
Go to the /etc directory. Enter:
cd /etc
-
Stop the Netscape Messaging Server. Enter:
./NscpMail stop
-
Remove the following files. Enter:
rm netscape.mail.conf NscpMail mailbin nsmail.als
-
Go to the /usr/lib directory. Enter:
cd /usr/lib
-
Remove the following files. Enter:
rm libNSmatch_shr.a libldap*_shr.a
-
Go to the /usr/sbin directory. Enter:
cd /usr/sbin
-
Rename the sendmail.bak file to sendmail. Enter:
mv sendmail.bak sendmail
-
Start the System Management Interface Tool. Enter:
smit
-
Restart the sendmail daemon. Select:
Processes & Subsystems/Subsystems/Start a Subsystem/sendmail
-
Go to the /etc directory. Enter:
cd /etc
-
Copy the inetd.conf.bak file to inetd.conf. Enter:
cp inetd.conf.bak inetd.conf
-
Start the System Management Interface Tool. Enter:
smit
-
Read the newly renamed file into memory. Select:
Processes & Subsystems/Subsystems/Refresh a Subsystem/inetd
-
Go to the /var directory. Enter:
cd /var/spool
-
Change the permissions for the mail directory. Enter:
chmod g-s mail
-
Go to the directory where you installed the post office and mailbox. For
example:
cd /var/spool
-
Remove the postoffice and mailbox directories. Enter:
rm -rf postoffice mailbox
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save, or email in the mailbox
directory, this will remove it.
Warning: The following steps remove the Netscape Administration
Server. If you have other Netscape servers installed that will continue
to use the Administration Server, do not perform the following steps.
To remove the Netscape Administration Server:
-
If you have the Messaging Server SNMP subagent running, stop it via the
Administration Server interface.
-
If you have the SNMP master agent running, stop it via the Administration
Server interface.
-
Go to the server root (the directory where you installed the server).
For example: cd /usr/netscape/suitespot
-
Stop the Administration Server.
Enter: ./stop-admin
It may take a few seconds to come down.
-
Go to the parent of the server root.
For example: cd /usr/netscape
-
Remove the server root.
For example: rm -rf suitespot
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save this will remove it.
Digital Unix
To remove the Messaging Server:
-
Login as root.
-
Go to the /etc directory.
Enter: cd /etc
-
Stop the Netscape Messaging Server.
Enter ./NscpMail stop
-
Go to the /usr/shlib directory.
Enter: cd /usr/shlib
-
Remove the following files.
Enter: rm libNSmatch.so libNSmail.so libldap*.so liblcache*.so
-
Go to the /usr/sbin directory.
Enter: cd /usr/sbin
-
Remove the processq file.
Enter: rm processq
-
Rename the mail.bak file to mailq.
Enter: mv mail.bak mailq
-
Rename the sendmail.bak file to sendmail.
Enter: mv sendmail.bak sendmail
-
Go to the /sbin/init.d directory.
Enter: cd /sbin/init.d
-
Restart the sendmail daemon.
Enter: ./sendmail start
-
Go to the /etc/ directory.
Enter: cd /etc
-
Remove the nsmail.als file.
Enter: rm nsmail.als
-
Rename the inetd.conf.bak file to inetd.conf.
Enter: mv inetd.conf.bak inetd.conf
-
Obtain the process ID (pid) of the inetd daemon.
Enter: ps -ef | grep inetd
-
Read the newly renamed file into memory.
Enter: kill -1 <pid of inetd>
-
Remove three files.
Enter: rm netscape.mail.cof NscpMail mailbin
-
Go to the /var/spool directory.
Enter: cd /var/spool
-
Change the permissions for the mail directory.
Enter: chmod g-s mail
-
Go to the directory where you installed the post office and mailbox.
For example: cd /var/spool
-
Remove the postoffice and mailbox directories.
Enter: rm -rf postoffice mailbox
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save, or email in the mailbox
directory, this will remove it.
Warning: The following steps remove the Netscape Administration
Server. If you have other Netscape servers installed that will continue
to use the Administration Server, do not perform the following steps.
To remove the Netscape Administration Server:
-
If you have the Messaging Server SNMP subagent running, stop it via the
Administration Server interface.
-
If you have the SNMP master agent running, stop it via the Administration
Server interface.
-
Go to the server root (the directory where you installed the server).
For example: cd /usr/netscape/suitespot
-
Stop the Administration Server.
Enter: ./stop-admin
It may take a few seconds to come down.
-
Go to the parent of the server root.
For example: cd /usr/netscape
-
Remove the server root.
For example: rm -rf suitespot
Important: Be sure that this is what you want to do. If there is
any configuration information that you want to save this will remove it.
Installing Messaging Server
3.5 on Windows NT
The procedure for installing Netscape Messaging Server 3.5 varies somewhat
depending on whether you intend to use a local database or the Netscape
Directory Server to manage user and group accounts. If you plan to use
a local database, follow the steps in the next
section. If you plan to use the Netscape Directory Server, click here.
Important: The instructions in the following sections differ
from those provided in the Messaging Server 3.0 Installation and Deployment
Planning Guide. The instructions in this Readme file are more
recent and supersede those in the printed documentation.
Installing for use with a
local database
If you are upgrading from Mail Server 2.0, before installing the Messaging
Server, you will need to have the appropriate privileges enabled for the
migration tool to work correctly.
To enable the correct Windows NT privileges, follow these instructions:
-
Start the User Manager application (under Administrative Tools).
-
Choose Policies|User Rights.
-
Enable the Show Advanced User Rights option by clicking its checkbox.
-
Choose Act as part of the operating system.
-
Select the user or users to whom you want to grant the right and click
Add.
-
Click OK.
Now you can continue installing Netscape Messaging Server 3.5.
To install Netscape Messaging Server 3.5, follow these instructions:
Installing from the CD:
-
Run the F:/ntx86/message/setup.exe file to start the installation
process.
Note: This path assumes that your CD drive is mapped to
drive F. If it is not, enter the correct drive in place of F.
-
Follow the onscreen instructions.
Installing from a download file:
-
Run the m301eiu.exe file to start the installation process.
-
Follow the onscreen instructions.
If at any time you quit the setup program, you can run it again later to
finish the installation process.
After the installation is completed, you can create new users. For instructions,
see Chapter 1 in the online version of the Messaging
Server 3.0 Administrator's Guide.
Installing for
use with Netscape Directory Server
If you are planning to use the Directory Server to maintain user and group
accounts, follow the instructions in the following sections in order:
Installing the Directory Server
If you plan to use the Directory Server to maintain user and group accounts,
you must install the Directory Server before installing the Messaging Server.
You can install the Directory Server from the Messaging Server CD, or you
can download it from the Netscape
download site. Please see the README file provided with the Directory
Server product.
Configuring the Directory Server
If you haven't already configured the SuiteSpot 3.0 Administrator's ID
during the Directory Server installation, you will need to do so before
installing the Messaging Server. Follow these steps:
-
From the Server Selector page, choose the Directory Server.
-
Choose System Settings | On/Off and turn on the Directory Server.
-
Choose Database Mgmt | SuiteSpot 3.0 Settings. In the SuiteSpot
3.0 Settings form, follow these steps:
-
Confirm the SuiteSpot 3.0 Administrator's ID.
-
Enter a password for the SuiteSpot 3.0 Administrator's ID.
-
Enter a password for the Directory Server's Unrestricted User.
-
Click OK.
-
When the "SuiteSpot 3.0 Settings Updated" page appears, write down the
Administrator's ID. (You'll need this information later when installing
the Messaging Server.)
Completing the Messaging Server
installation
If you are upgrading from Mail Server 2.0, before installing the Messaging
Server, you will need to have the appropriate privileges enabled for the
migration tool to work correctly.
To enable the correct Windows NT privileges, follow these instructions:
-
Start the User Manager application (under Administrative Tools).
-
Choose Policies|User Rights.
-
Enable the Show Advanced User Rights option by clicking its checkbox.
-
Choose Act as part of the operating system.
-
Select the user or users to whom you want to grant the right and click
Add.
-
Click OK.
To install Netscape Messaging Server 3.5, follow these instructions:
Installing from the CD:
-
Run the F:/ntx86/message/setup.exe file to start the installation
process.
Note: This path assumes that your CD drive is mapped to
drive F. If it is not, enter the correct drive in place of F.
-
Follow the onscreen instructions.
Installing from a download file:
-
Run the m301eiu.exe file to start the installation process.
Follow the onscreen instructions.
If at any time you quit the setup program, you can run it again later to
finish the installation process.
Important: The installation program asks you to enter an Administrator's
ID for the Messaging Server. Be sure to use the same Administrator's ID
as you did for the SuiteSpot 3.0 Administrator's ID. The program also asks
for the base DN for the Directory Server. Enter the base DN that you copied
from the "SuiteSpot 3.0 Settings Updated" page.
After the installation is completed, you can create new users. For instructions,
see Chapter 1 in the online version of the Messaging
Server 3.0 Administrator's Guide.
Uninstalling Messaging Server
3.5 on Windows NT
Follow these steps to uninstall Messaging Server 3.5 on a Windows NT system.
Note: These instructions can also be used to uninstall Messaging
Server 2.0 and 3.0x.
To start the uninstall program do the following:
Windows NT 4.0:
-
Open the Control Panel.
-
Select Add/Remove Programs.
-
Choose Netscape Messaging Server.
-
Click OK.
Windows NT 3.51:
-
Open the Netscape SuiteSpot program group.
-
Double-click the Remove Messaging Server icon.
Now under either NT versions, you will be presented with a list of all
the Netscape Servers on this system. If you have only Messaging Server
3.5 installed, you see Netscape Administration Server and Netscape Messaging
Server in the list.
-
To remove only the Messaging Server, set the check next to Messaging Server
3.5 to ON.
-
To remove both the Messaging Server and the Administration Server, set
the checks to ON for both servers.
Important: If you have other SuiteSpot 3.0 servers installed,
they will also show up in this list. To avoid removing these, deselect
their entries from the list and deselect the Administration Server.
Do not remove the Administration Server if there are Netscape SuiteSpot
3.0 servers that you are not removing.
-
Click Uninstall and follow the onscreen instructions.
Copyright 1997 Netscape Communications Corporation.
All rights reserved.