This site powered by: Netscape Enterprise Server and Netscape Compass Server.
Welcome to Netscape Messaging Server. Netscape Messaging Server is an open,
standards-based client-server messaging system that lets users easily exchange
information within a company as well as across the Internet. Controlled
by forms accessed through the World Wide Web (WWW), Netscape Messaging
Server lets server administrators manage Messaging Server functions with
the easy-to-use Netscape Navigator interface from any desktop in the network.
It addresses the major security vulnerabilities associated with email systems
and delivers superior performance. Because the messaging server is based
on Internet open standards (such as SMTP, POP3, IMAP4, LDAP, and MIME),
you avoid costly dependence on proprietary solutions and are assured of
maximum compatibility with other systems.
Netscape Messaging Server 3.0 offers a variety of new features designed to enhance your electronic mail (email) system:
Netscape Messaging Server 3.0 supports the Lightweight Directory Access Protocol (LDAP) standard, allowing the Messaging Server to integrate with local or centralized directory services flexibly. A centralized directory service gives server administrators a single point where they can add, change, and delete users. And that user information can be shared across all Netscape SuiteSpot Servers, including Netscape Messaging Server.
Netscape Messaging Server employs LDAP user address information for message routing and address resolution. It also takes advantage of LDAP search capabilities, allowing you to create criteria-based mail groups. That is, you can define a mail group by indicating the criteria you want to use to define a mail group--for example, a group composed of all users who belong to a particular organizational unit.
For users, LDAP means controlling their own account information, including passwords, automated replies, and automated message forwarding, thereby reducing administration costs.
Netscape Messaging Server 3.0 supports authenticated Simple Mail Transfer Protocol (SMTP) for greater security in sending messages over the SMTP channel. When supported by the user's mail client, authenticated SMTP requires users to enter their password before being allowed to send messages. Recipients can determine whether a message has been sent by an authenticated sender: the sender's name is followed by an indication that the message is internal.
Netscape Messaging Server 3.0 lets you specify the level of encryption and authentication for receiving messages with Internet Message Access Protocol (IMAP) clients. It provides a variety of options for encryption using Single Socket Layers (SSL) and authentication with passwords and client certificates.
Netscape Messaging Server 3.0 also includes Simple Network Management Protocol (SNMP) support for unified network management with any SNMP-compatible network management tool.
Netscape Messaging Server 3.0 supports message quotas. With the quota system enabled, server administrators can limit users to a fixed mailbox size by setting disk size limits. In this way, administrators have a manageable mechanism with which to control their potentially explosive messaging growth. The Messaging Server also provides warnings when users are nearing their message quotas. Messages received after a user's message quota has been reached are returned to the sender with a message indicating the reason for the message rejection.
Netscape Messaging Server 3.0 includes a new single-copy message store capability that, if enabled, stores a single copy of any message sent to multiple recipients rather than one copy per recipient. This feature is designed to conserve disk space.
Netscape Messaging Server 3.0 can confirm message delivery, whether messages are sent within the enterprise or across the Internet. The Messaging Server's delivery status notification feature is based on the prevailing Internet standards (RFCs 1891 through 1894). Consequently, email users are apprised of message delivery not only by Netscape Messaging Server but also by other internal or Internet messaging systems that support these standards.
Netscape Messaging Server 3.0 provides an application program interface (API) that allows third parties to "plug in" site-specific functionality in the Messaging Server. It is intended for developers who wish to extend the functionality of the Messaging Server for site-specific reasons.
This guide is intended for Netscape Messaging Server administrators, those responsible for setting up and administering the Messaging Server after it has been installed. For instructions on installing Netscape Messaging Server, see the Installation Guide.
Here's what you'll find in this guide:
This guide also includes a glossary of terms and an index.
This guide provides instructions on administering Netscape Messaging Server. Here's what you'll find in the other Netscape guides:
This guide uses standard naming conventions. The following table describes those naming conventions and provides examples of their use. It also describes the typeface conventions and margin notes used in this book.
This guide provides information about two versions of the Netscape Messaging Server: one for Unix, the other for Windows NT. In cases where pathnames for Unix and Windows NT differ only in their use of their respective slash conventions--the forward slash (/) for Unix, the backslash () for Windows NT--for brevity, this guide presents the pathname only in the Unix format.
Note
Windows NT supports both forwardslash and backslash characters.
In cases where the differences between Unix and Windows pathnames are significant and go beyond their differing slash convention, the pathnames are provided in both forms and identified with a margin note.
For the latest technical information on Sun-Netscape Alliance products, go to: http://developer.iplanet.com
For more Internet development resources, try Netscape TechSearch.