Your migration plan will probably include setting up mail service for your network. NetWare 4 server software comes bundled with a store-and-forward messaging engine for NetWare 4-based networks. This messaging engine is implemented by the MHS.NLM installed on the server during MHS installation.
NetWare 4 MHS Services also includes DOS and MS Windows versions of an e-mail client software package called FirstMail. FirstMail is an NDS-aware e-mail client from Novell.
This chapter describes how to install NetWare 4 message handling services and how to install the FirstMail client software that will access those services for DOS and Windows machines.
Messaging services transport data, called messages, between nodes on the network's underlying communications protocol of the network. The method of transmitting messages is called store-and-forward, which means that the message may be temporarily held at an intervening node on the network until it can be delivered. The message is delivered and then stored at the final destination node until the recipient is ready to read the message and decide its status (forward, delete, or store it). The types of messages include text, binary, graphic, audio, and video information.
For a simple LAN-based messaging application, messaging services consist of the following components:
The messaging server accepts messages from an application, typically a user's e-mail client software, and delivers the message to the destination user's mailbox. In a larger network consisting of an interconnection of many different types of networks, the message may have to be routed to other messaging servers before it can be delivered.
User mailboxes are held on a machine that is local to the user. This is typically the server the user is most frequently logged in to. A common method of implementing user mailboxes is to use a file system directory on the local server. Other methods that treat the user mailboxes as abstract mail objects are also available.
Typical messaging applications are e-mail client software and groupware software such as Novell's GroupWise, calendaring software, scheduling programs, and so on.
Lager networks require other messaging service components, such as mail gateways and mail routers. Mail gateways allow the delivery of messages to a foreign e-mail system. Mail routers are store-and-forward computers that may temporarily store the message and then forward the message to the final destination or an intervening destination. In some systems, the mail router may be implemented as part of the messaging server.
The NetWare 4 MHS software is provided in the NetWare 4 CD-ROM. You can create an unlimited number of mailboxes per NetWare server. You are, however, limited by the NetWare server license, which limits the number of concurrent user sessions on the network.
The minimum hardware requirements for the NetWare server on which MHS is installed are the following:
The NetWare MHS services take up the following server resources:
Novell claims that the preceding minimum requirements are not sufficient to handle more than 10 users or more than 100 messages per day. For networks that need to process more than 100 messages per day, the following configuration is recommended:
The following is a guided tour of the NetWare 4 MHS installation process:
LOAD ASPICD (For ASPI for SCSI CDROM) LOAD CDROM CD MOUNT N
CD VOLUME LIST
Figure 8.1 The Installation Options menu.
Figure 8.2 Other installation options.
Figure 8.3 The Install NetWare MHS Services option.
Figure 8.4 Default source path name for NetWare MHS Services.
Figure 8.5 File Copy Status.
11. Load the MHS.NLM with the following line:
You can also install NetWare MHS services during the initial NetWare 4.x installation by completing the previously outlined steps after the initial NetWare 4.x server installation (see Chapter 3, "Installing and Upgrading to NetWare 4.x").
As part of the NetWare 4 MHS installation, the Messaging Server and the Message Routing Group objects are created. This section describes these objects, their properties, and the changes to the NDS tree.
The Messaging Server enables the messaging services. This object defines the location of the message directory structure. This is the \MHS directory on the volume object on which MHS services were installed. The Messaging Server also identifies (via its NetWare Server property) the NetWare server on which the MHS services program (MHS.NLM) is running. This object is created and automatically configured as part of the NetWare 4 MHS service installation.
The Message Routing Group is used to identify a cluster of Messaging Servers that communicate with each other for transferring messages. A default message-routing group called MHS_ROUTING_GROUP is created as part of the NetWare MHS services installation.
The following is a list of changes made to the NDS tree:
Figure 8.6 Newly created message objects in server context.
Figure 8.7 Postmaster General owner of Message Routing Group object.
Figure 8.8 Messaging Servers property of the Message Routing Group.
Figure 8.9 Postmasters property of the Messaging Server.
If you delete or rename the Postmaster General user (Admin user), you must make changes to the Postmaster General properties of the Messaging Server and the Message Routing Groups. If you neglect to do this, the messaging services will malfunction.
Figure 8.10 Message Routing Groups property of the Messaging Server.
Figure 8.11 The NetWare server and the MHS Database location properties for a Messaging Server object.
Figure 8.12 Mailbox Location and Mailbox ID of Postmaster General user.
The user, group, organizational role, organization, and organizational unit NDS objects have MHS-related properties. You can assign these properties using NWADMIN. You can use the Users page button of the Messaging Server object, or select the Mailbox page button of the object whose property needs to be set.
The following is an outline of how these properties can be set from the Messaging Server.
Figure 8.13 Users property of Messaging Server.
Figure 8.14 The Select Object dialog box for assigning users to Messaging Server.
The following steps outline how you can set these properties for the user, group, organizational role, organization, or organizational unit objects. The example given involves setting the mailbox properties for the organization O=SCS.
Figure 8.15 Mailbox properties of Organization O=SCS.
Figure 8.16 The Select Object dialog box for selecting the Messaging Server.
Figure 8.17 The Messaging Server object found using the Select Object dialog box.
Figure 8.18 Mailbox properties set for O=SCS.
Besides the Messaging Server and the Message Routing Group objects, which are created when NetWare 4 MHS services are installed, there are two other objects that deal with messaging services. These objects are the External Entity and the Distribution List objects.
The External Entity object is used to refer to non-native NDS objects such as e-mail addresses of foreign e-mail systems. These objects are created and configured when gateway software is installed; they are not used for basic MHS services.
The External Entity object is a placeholder that allows you to send messages to users who would not normally be listed in the NDS tree because they are not part of the NDS-based network.
A distribution list is a group of mailbox addresses. A single message can be addressed to the entire group and all group members will receive the message. If the mailboxes are on the same server, addressing a message to a distribution list reduces network traffic because a single message addressed to the distribution list mailbox is replicated at the server and distributed to the mailboxes on the list.
You can also use NDS group objects to distribute mail to the members of the group. Whereas a group's membership property cannot contain other groups, a distribution list can contain other distribution lists. In other words, distribution lists can be nested. Members of a distribution list do not share login scripts or trustee assignments. The membership only serves for the convenience of sending messages to multiple recipients.
To create a distribution list, use the following steps:
Figure 8.19 The dialog box for creating a distribution list.
Figure 8.20 The Select Object dialog box for setting the Mailbox Location.
Figure 8.21 Distribution List properties.
Figure 8.22 Members property of Distribution List object.
Figure 8.23 Assigning members to the distribution list.
FirstMail is available in MS Windows and DOS versions. The following guided tour describes how to set up FirstMail for MS Windows.
To use FirstMail, you must first set up a program item. Use the following steps to set up a FirstMail program item for MS Windows.
The following is a guided tour for using FirstMail to create, send, and receive e-mail messages:
Figure 8.24 The FirstMail screen.
Figure 8.25 The Create Message screen.
The recipient of the message should perform the following tasks to read the message:
In this chapter you learned how to set up NetWare 4 Message handling services and how to install FirstMail, an NDS-aware e-mail client for DOS and Windows systems.
© Copyright, Macmillan Computer Publishing. All rights reserved.