#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'MHS Services for NetWare 4MHS Services for NetWare 4Novell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=7 ID="BP1"About this GuideThis guide helps you understand what NetWare® MHS(tm) Services for NetWare 4 offers, and explains how to install and manage it. The guide also describes how to use FirstMail(tm).RENDERAS="SECT1"Who Should Use this GuideThis guide is written for messaging administrators in a NetWare 4 network.RENDERAS="SECT1"How to Use this GuideThe guide is divided into the following chapters:MARK=BULLETIDREF="FM43011"Chapter 1, "Introduction," presents an overview of MHS Services and describes MHS (Message Handling Service) concepts, MHS names, and the utilities provided for management of messaging. It also provides a road map of tasks for the messaging administrator. Read this chapter before installing MHS Services.IDREF="FM19262"Chapter 2, "Installing and Running MHS Services," explains how to install, load (or activate), and unload MHS Services. IDREF="FM12795"Chapter 3, "Managing MHS Mailboxes," describes how to manage mailboxes using the NetWare Administrator utility. IDREF="FM90793"Chapter 4, "Using Gateways," explains how to configure support for gateways in your NetWare network. Read this chapter if your network will contain gateways.IDREF="FM56530"Chapter 5, "Monitoring and Maintaining an MHS Messaging ServerPAGENUM=8 ID="BP2"," provides guidelines on how to monitor messaging statistics, statuses, and event logs, and how to customize the MHS messaging server configuration.IDREF="FM82881"Appendix A, "Assigning Applications to Users," explains how to register applications and assign them to users. Read this appendix if you are using messaging applications that are not NDS-aware.IDREF="FM43407"Appendix B, "Getting Started with FirstMail," describes how to use FirstMail. You can copy this appendix and distribute it to the users who will be using FirstMail.RENDERAS="SECT1"Related DocumentsFor information about third-party messaging applications, refer to the NetWare MHS Solutions Guide, Novell Part Number 462-000230-004.For assistance with developing a messaging-enabled application, refer to the Novell SMF v71 Programmer's Reference, Novell Part Number 100-001213-001.LABEL="1"PAGENUM=1 ID="BP3"ID="FM43011"IntroductionNetWare® MHS(tm) Services provides a store-and-forward message-transfer service to NetWare 4 networks. MHS Services, which is an integral part of the NetWare 4.1 operating system, allows users of MHS-compatible messaging applications to exchange electronic mail, share calendars, schedule facilities, and perform many other tasks.MHS Services supports NDS-aware messaging applications that adhere to Novell's Standard Message Format (SMF) v71. (Applications that use IDXID="w4561"BOOK="_idx" COLLECTION="nw41" TIDREF="i453"
bindery services work only for users in a bindery context.)Your NetWare 4.1 package contains FirstMail(tm), a starter E-mail application from Novell®. In addition, third-party developers offer a wide variety of MHS-compatible applications, such as calendaring, workflow, and electronic data interchange (EDI).This chapter containsMARK=BULLETAn overview of MHS ServicesAn explanation of the messaging concepts you must understand to install and administer MHS ServicesA description of MHS namesA description of each of the utilities and programs used to manage messaging servicesA road map of the tasks the messaging server administrator must perform to implement and maintain MHS ServicesPAGENUM=2 ID="BP4"RENDERAS="SECT1"Overview of MHS ServicesThis section describes the advantages of implementing messaging in your NetWare network, and describes Novell's messaging products.RENDERAS="SECT2"Why Use Messaging?IDXID="w4562"BOOK="_idx" COLLECTION="nw41" TIDREF="i2430"IDXID="w4563"BOOK="_idx" COLLECTION="nw41" TIDREF="i128"
In more and more companies, messaging has become a critical component of the network environment. In fact, messaging has become a central part of a network's service (third only to file and print) because itMARK=BULLETImproves communication.Messaging applications are among the many tools developed to meet modern communication needs. These applications enable employees to communicate even when meetings, travel schedules, and different locations prevent them from meeting face-to-face.Increases productivity.In many companies, employees spend time on "telephone tag" and other unsuccessful communication attempts. Messaging increases productivity by improving the success rate for communication. The success rate improves because, unlike other forms of communication, messaging does not require conversing participants to be available at the same time. Participants contribute to the conversation at their convenience, and messages are stored until recipients can process them.Maximizes the use of existing resources.Messaging leverages the use of your existing network. You can provide users with all the benefits of a messaging solution without adding more resources.RENDERAS="SECT2"What Is MHS Services?IDXID="w4564"BOOK="_idx" COLLECTION="nw41" TIDREF="i2440"
MHS Services provides message delivery to users on a NetWare 4.1 network. IDXID="w4565"BOOK="_idx" COLLECTION="nw41" TIDREF="i2436"IDXID="w4566"BOOK="_idx" COLLECTION="nw41" TIDREF="i4179"IDXID="w4567"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"PAGENUM=3 ID="BP5"Users can create messages with an application that adheres to Novell's Standard Message Format (SMF) 71 interface. The application submits its message to MHS Services, which delivers it to the recipient's mailbox. For a list of SMF-compatible applications, refer to the NetWare MHS Solutions Guide, which is available from your Novell reseller or sales office.MHS Services is easy to install and use. It requires less than 500 KB of Random Access Memory (RAM). Additionally, it is fully integrated with NetWare Directory Services (NDS) and other NetWare 4 components (such as NetWare Administrator, NETADMIN, and UIMPORT).Like other products in the NetWare MHS family, MHS Services supports a simple file-based interface that you can use to write IDXID="w4568"BOOK="_idx" COLLECTION="nw41" TIDREF="i2431"IDXID="w4569"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
messaging-enabled applications. Messaging-enabled applications can use MHS Services to send messages to users, or to each other. For example, a messaging-enabled database program can generate a report and use MHS Services to distribute it to a group of MHS users.RENDERAS="SECT2"What Is FirstMail?IDXID="w4570"BOOK="_idx" COLLECTION="nw41" TIDREF="i1516"
FirstMail is an electronic mail application that is available in DOS and MS Windows versions. With FirstMail, a user canMARK=BULLETCreate and send messages and attached filesRead, print, delete, save, reply to, and forward messagesCreate and maintain an address directoryOrganize messages in foldersFirstMail provides easy-to-use menus and online help.FirstMail is installed during MHS Services installation. To use FirstMail for MS Windows, users must create a program item in MS Windows (see IDREF="FM32549""FirstMail for MS Windows," on page 85). FirstMail requires no additional configuration. PAGENUM=4 ID="BP6"RENDERAS="SECT1"MHS Services ConceptsThis section explains some of the concepts you must understand to be able to install and implement MHS Services successfully. These concepts includeMARK=BULLETMessaging ServerMessage Routing GroupPostmaster GeneralPostmasterMailboxGatewayRENDERAS="SECT2"Messaging ServerEach NetWare server on which MHS Services is installed and loaded is a IDXID="w4571"BOOK="_idx" COLLECTION="nw41" TIDREF="i2429"messaging server. Each NetWare server that will contain user mailboxes must be a messaging server.When you install MHS Services on a NetWare server, the installation program creates a messaging server object in the same context as the NetWare server object. The name of the messaging server is NetWare_server_MSG.context. For example, if you install MHS Services on the NetWare server "BOSTON.Acme," the messaging server object will have the name "BOSTON_MSG.Acme." You can move a messaging server object to a different context, or change its name, with the NetWare Administrator (NWADMIN) or NETADMIN utilities.RENDERAS="SECT2"Message Routing GroupA IDXID="w4572"BOOK="_idx" COLLECTION="nw41" TIDREF="i2414"message routing group is a group of messaging servers that communicate with each other directly to transfer messages. (That is, each messaging server in a message routing group can deliver messages to all the other messaging servers in the same message routing group.)PAGENUM=5 ID="BP7"The current release of MHS Services supports a single message routing group.The first time you install MHS Services in your NetWare network, the installation program creates an NDS object called "MHS_Routing_Group" in the same context as the NetWare server object. You can move the message routing group object, or change its name, with the NWADMIN or NETADMIN utilities.When you install messaging servers in your network, they are added to this message routing group.RENDERAS="SECT2"ID="FM46099"Postmaster GeneralEach message routing group has one or more IDXID="w4573"BOOK="_idx" COLLECTION="nw41" TIDREF="i3347"Postmaster Generals. The Postmaster General, typically the Admin user, is automatically granted the privileges necessary to perform the following tasks:MARK=BULLETModify the message routing group objectModify the messaging servers that belong to that message routing groupWhen you install the MHS Services software, the installation program prompts you to log in as the user who will be the Postmaster General. RENDERAS="SECT2"PostmasterEach messaging server has one or more IDXID="w4574"BOOK="_idx" COLLECTION="nw41" TIDREF="i3346"Postmasters, users who are automatically granted the privileges necessary to perform the following tasks:MARK=BULLETModify the messaging server objectAssign a mailbox on the messaging server to an objectModify or delete mailboxes on the messaging serverIn addition, the Postmaster receives notifications of special messaging events. For example, if MHS Services receives a message that is in an invalid format, and it cannot identify the sender, it sends an error notification to the Postmaster.PAGENUM=6 ID="BP8"By default, the Postmaster for a messaging server is the Postmaster General for the message routing group to which the server belongs. You can use the NWADMIN or NETADMIN utilities to add users to or delete users from the list of Postmasters.To de-centralize administration of your messaging network, remove the Postmaster General from the list of Postmasters for each messaging server in the network.RENDERAS="SECT2"GatewayA IDXID="w4575"BOOK="_idx" COLLECTION="nw41" TIDREF="i1593"gateway is a software program that does either of the following:MARK=BULLETSupplies additional messaging features, such as access to a gateway service (for example, a fax service or an electronic bulletin board).Provides access to another protocol or messaging system. (For example, a cc:Mail* gateway allows MHS users to exchange messages with users in a cc:Mail environment.)MHS Services provides messaging connectivity in a homogeneous NetWare 4.1 network. To extend messaging connectivity to other networks, such as X.400 and SMTP, you must install and configure optional gateways. Many gateways are available from Novell and from third-party vendors. For a list of supported gateways, refer to the NetWare MHS Solutions Guide. To find out how to implement gateways in your network, refer to IDREF="FM90793"Chapter 4, "Using Gateways."RENDERAS="SECT2"ID="FM28227"MailboxIDXID="w4576"BOOK="_idx" COLLECTION="nw41" TIDREF="i2307"
You must assign a mailbox to each object that will be receiving messages. A mailbox is the physical location to which the object's messages are delivered. There are two types of mailboxes, native (MHS) mailboxes, and foreign (non-MHS) mailboxes.RENDERAS="SECT3"MHS MailboxIDXID="w4577"BOOK="_idx" COLLECTION="nw41" TIDREF="i2437"
An MHS mailbox is identified by two properties: mailbox location and mailbox ID.PAGENUM=7 ID="BP9"The IDXID="w4578"BOOK="_idx" COLLECTION="nw41" TIDREF="i2305"mailbox location is the MHS messaging server on which the MHS mailbox resides. For user objects, this is the MHS messaging server to which the user's messages are delivered. For other objects, this is the MHS messaging server responsible for IDXID="w4579"BOOK="_idx" COLLECTION="nw41" TIDREF="i1431"fanning out messages addressed to the object (that is, determining the members or occupants of the object, and creating a copy of the message for each one).Only user objects have a IDXID="w4580"BOOK="_idx" COLLECTION="nw41" TIDREF="i2304"mailbox ID, which identifies the subdirectory to which the user's messages are delivered.To find out how to assign an MHS mailbox, refer to IDREF="FM12795"Chapter 3, "Managing MHS Mailboxes."RENDERAS="SECT3"Foreign MailboxIDXID="w4581"BOOK="_idx" COLLECTION="nw41" TIDREF="i1541"
A foreign mailbox is a mailbox on a foreign E-mail system. It is identified by the foreign E-mail address property, which specifies an object's address on the foreign E-mail system.If you are using gateways in your messaging network, you might need to assign a foreign mailbox to an NDS object. For example, if an NDS user wishes to receive mail in SMTP, you might need to assign that user an SMTP address.To find out how to assign a foreign mailbox, refer to IDREF="FM95390""Assigning Foreign E-Mail Addresses," on page 31.RENDERAS="SECT1"MHS Names for NDS ObjectsIDXID="w4582"BOOK="_idx" COLLECTION="nw41" TIDREF="i2632"IDXID="w4583"BOOK="_idx" COLLECTION="nw41" TIDREF="i105"IDXID="w4584"BOOK="_idx" COLLECTION="nw41" TIDREF="i4026"
The following NDS objects are addressable (that is, they can receive E-mail messages): MARK=BULLETUsersOrganizational rolesMail addressed to an organizational role is delivered to the occupants of the role.Groups and distribution listsPAGENUM=8 ID="BP10"A group is an NDS object created for the purpose of granting a common login script or common trustee assignments to multiple users. A group's membership cannot contain other groups. A distribution list, on the other hand, is an NDS object created to simplify the addressing of messages. Distribution list members do not share a login script or trustee assignments, and a distribution list's membership can contain other distribution lists.Mail addressed to a group is delivered to the members of the group, and mail addressed to a distribution list is delivered to the members of the list.AliasesMail addressed to an alias is delivered to the aliased object.External EntitiesMail addressed to an external entity is delivered to the gateway that connects to the foreign E-mail system on which the external entity's mailbox is located.You need not assign these objects special names for use by MHS Services. MHS Services uses their complete names, as defined in the NetWare database. To enable an object to receive mail, you must assign it a mailbox. See IDREF="FM28227""Mailbox," on page 6 for more information.MHS Services requires a slightly different name format than NDS. Whereas NDS complete names take the format common_name.context, MHS Services requires names in the format common_name@context. (Names in this format are called IDXID="w4585"BOOK="_idx" COLLECTION="nw41" TIDREF="i2438"MHS names.)Some MHS-compatible applications refer to the context as the IDXID="w4586"BOOK="_idx" COLLECTION="nw41" TIDREF="i4830"workgroup. The MHS name is sometimes referred to as the IDXID="w4587"BOOK="_idx" COLLECTION="nw41" TIDREF="i4178"SMF 71 name.For example, consider the user with the common name "Anne Black." Her context is "OU=Marketing.O=Novell." Therefore, her MHS name is "Anne Black@Marketing.Novell."IDXID="w4588"BOOK="_idx" COLLECTION="nw41" TIDREF="i4341"IDXID="w4589"BOOK="_idx" COLLECTION="nw41" TIDREF="i617"PAGENUM=9 ID="BP11"MHS Services does not support all the characters that are valid in complete names. To ensure that objects can receive messages, restrict complete names to the subset of printable characters in the IBM-437 character set (0x20 to 0x7E). Also, exclude the following characters, because they have a special meaning in MHS: double quotation mark ("), backslash (\), semicolon (;), parentheses (( )), square brackets ([ ]), braces ({ }), comma (,), at sign (@), period (.), and tab.Many MHS-compatible applications provide an IDXID="w4590"BOOK="_idx" COLLECTION="nw41" TIDREF="i95"Address Book (a IDXID="w4591"BOOK="_idx" COLLECTION="nw41" TIDREF="i3336"IDXID="w4592"BOOK="_idx" COLLECTION="nw41" TIDREF="i1059"
popup directory list), from which users can select addresses. To users of these applications, the difference in format of complete names and MHS names is transparent. Only users who enter addresses manually must be aware of the MHS name format.For more information about complete names, refer to the BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services manual.RENDERAS="SECT1"MHS Services Utilities and ProgramsIDREF="FM55657"Table 1-1 describes the utilities and programs used by MHS Services, and the tasks they will help you accomplish.LABEL="1-1" PGWIDE=1 TOCENTRY="1"ID="FM55657" MHS Services Utilities and ProgramsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Utility/ProgramCOLNAME=2 ROTATE="0" MOREROWS="0"TasksVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4593"BOOK="_idx" COLLECTION="nw41" TIDREF="i3028"
NWADMINCOLNAME=2 ROTATE="0" MOREROWS="0"(MS Windows-based graphical utility) Managing mailboxes, configuring gateways. COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4594"BOOK="_idx" COLLECTION="nw41" TIDREF="i2641"
NETADMINCOLNAME=2 ROTATE="0" MOREROWS="0"(Text utility) Managing mailboxes, configuring gateways.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4595"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"
UIMPORTCOLNAME=2 ROTATE="0" MOREROWS="0"(Batch utility) Assigning mailboxes.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4596"BOOK="_idx" COLLECTION="nw41" TIDREF="i2441"
MHSCONCOLNAME=2 ROTATE="0" MOREROWS="0"(NLM) Monitoring messaging server statistics and events, managing message flow, and customizing the messaging server configuration.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4597"BOOK="_idx" COLLECTION="nw41" TIDREF="i2439"
MHSCOLNAME=2 ROTATE="0" MOREROWS="0"(NLM) Picking up, routing, and delivering messages.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4598"BOOK="_idx" COLLECTION="nw41" TIDREF="i2302"
MAILCOLNAME=2 ROTATE="0" MOREROWS="0"(DOS-based FirstMail application) Creating and sending messages and reading, printing, and filing incoming messages. FirstMail for DOS is automatically installed during MHS Services installation, and is ready-to- use without further configuration.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4599"BOOK="_idx" COLLECTION="nw41" TIDREF="i4829"
WMAILCOLNAME=2 ROTATE="0" MOREROWS="0"(MS Windows-based FirstMail application) Creating and sending messages and reading, printing, and filing incoming messages. FirstMail for MS Windows is automatically installed during MHS Services installation. To use this application, users must create a program item in Windows.PAGENUM=10 ID="BP12"NWADMIN, NETADMIN, and UIMPORT are installed as part of the NetWare 4.1 installation.For information about how to use FirstMail for DOS, refer to IDREF="FM87350""FirstMail for DOS," on page 73. For information about how to use FirstMail for MS Windows, refer to IDREF="FM32549""FirstMail for MS Windows," on page 85. For information about how to use the other utilities, refer to the 
BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference manual. RENDERAS="SECT1"ID="FM22592"Road Map of TasksThe messaging administrator's tasks can be divided into the following categories:MARK=BULLETInitial tasks (such as the installation and loading of MHS Services)Ongoing tasks (such as assigning or moving user mailboxes) that are part of ongoing maintenanceOther, optional, tasks (such as monitoring the messaging server or configuring gateways)IDREF="FM24918"Figure 1-1 illustrates all the messaging administrator's tasks.PAGENUM=11 ID="BP13"LABEL="1-1" FLOAT="0"ID="FM24918"Road MapFILEREF="roadmap.tif"LABEL="2"PAGENUM=13 ID="BP14"ID="FM19262"Installing and Running MHS ServicesThis chapter describes the hardware and software requirements for NetWare® MHS(tm) Services, and explains how to perform the following tasks:MARK=BULLETInstall and load MHS Services on a NetWare server.MHS Services must be installed and loaded on every NetWare server on which you want to store mailboxes. For more information, refer to IDREF="FM59669""Installing MHS Services," on page 14, and IDREF="FM65094""Loading MHS Services," on page 17.Unload MHS Services.When you unload MHS Services, message-delivery services are suspended temporarily (until MHS Services is reloaded). You must unload and reload MHS Services after you change the configuration parameters. (The new parameters will not take effect until MHS Services is reloaded.) You might also want to unload MHS Services when you are troubleshooting messaging problems. For more information, refer to IDREF="FM41804""Unloading MHS Services," on page 18.RENDERAS="SECT1"ID="FM62106"Hardware Requirements for MHS ServicesIDXID="w4600"BOOK="_idx" COLLECTION="nw41" TIDREF="i1641"
The NetWare 4.1 server on which you are installing MHS Services must have the following resources available for MHS Services:MARK=BULLET500 KB of additional IDXID="w4601"BOOK="_idx" COLLECTION="nw41" TIDREF="i3670"
Random Access Memory (RAM) IDXID="w4602"BOOK="_idx" COLLECTION="nw41" TIDREF="i1129"
2.5 MB of disk space for program storage, plus additional disk space for user mailboxesPAGENUM=14 ID="BP15"The amount of disk space required for user mailboxes will vary, depending on the size and number of messages that users store in their mailboxes. After you install and implement MHS Services, you can use the Statistics function of the MHSCON utility (see IDREF="FM64236""Monitoring Statistics," on page 34) to obtain statistics about the number and size of messages sent by users.If message traffic is heavy, you might need to install MHS Services on a dedicated volume, to ensure that sufficient storage space is available for messages.RENDERAS="SECT1"ID="FM59669"Installing MHS ServicesIDXID="w4603"BOOK="_idx" COLLECTION="nw41" TIDREF="i1826"IDXID="w4604"BOOK="_idx" COLLECTION="nw41" TIDREF="i2440"
You can install MHS Services when you install NetWare 4.1 on your server, or you can install it later. To install MHS Services, follow this procedure.PERFORMANCE="REQUIRED"If you are installing MHS Services at the same time as NetWare 4.1, follow these steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Install NetWare 4.1 with the 
CLASS=MENUITEM MOREINFO="NONE"Customized installation of NetWare 4.1 option.PERFORMANCE="REQUIRED"Complete the operating system installation by following the instructions in the 

BOOK="instlenu" COLLECTION="nw41"Installation or 

BOOK="upmigenu" COLLECTION="nw41"Upgrade and Migration manuals.When the operating system installation is complete, the Other Installation Actions menu appears. Skip to IDREF="FM22038"Step 3.PERFORMANCE="REQUIRED"If you are installing MHS Services at a later time than NetWare 4.1, follow these steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Enter the following command at the file server console:MOREINFO="NONE"LOAD INSTALLThe Installation Options menu appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Product options.The Other Installation Actions menu appears.PERFORMANCE="REQUIRED"ID="FM22038"Select the 
CLASS=MENUITEM MOREINFO="NONE"Choose an item or product 
CLASS=MENUITEM MOREINFO="NONE"listed above option. 
PAGENUM=15 ID="BP16"The Other Installation Items/Products menu appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Install NetWare MHS option.The INSTALL NLM prompts for the location of the MHS Services software. PERFORMANCE="REQUIRED"Specify the path to the MHS Services software.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"To accept the default source path, press 
MOREINFO="NONE"<Enter>.If the default path is on a NetWare server, the Remote Server Authentication screen appears. Continue with IDREF="FM26765"Step 6.If the default path points to a local drive, the INSTALL program begins copying files to the \SYSTEM and \PUBLIC directories. Then the Postmaster General Authentication window appears (see IDREF="FM76557"Figure 2-1). Skip to IDREF="FM52207"Step 7.PERFORMANCE="REQUIRED"ID="FM43586"To specify a different source path, press 
MOREINFO="NONE"<F3>, and enter the path when prompted.If the specified path is on a NetWare server, enter it in the format server\volume:path. The Remote Server Authentication screen appears. Continue with IDREF="FM26765"Step 6.If the specified path points to a local drive, the INSTALL program begins copying files to the \SYSTEM and \PUBLIC directories. Then the Postmaster General Authentication window appears (see IDREF="FM76557"Figure 2-1). Skip to IDREF="FM52207"Step 7.PERFORMANCE="REQUIRED"ID="FM26765"Log into the remote server by typing a User Name and Password and pressing 
MOREINFO="NONE"<Enter>.The INSTALL program begins copying files to the \SYSTEM and \PUBLIC directories. Then the Postmaster General Authentication window appears (see 
IDREF="FM76557"Figure 2-1).
PAGENUM=16 ID="BP17"LABEL="2-1" FLOAT="0"ID="FM76557"Postmaster General Authentication WindowFILEREF="custom6.tif"PERFORMANCE="REQUIRED"ID="FM52207"In the Name field of the Postmaster General Authentication window, enter the complete name of the user who will be Postmaster General. For example, 
MOREINFO="NONE"ADMIN.Acme.
 The Postmaster General is typically the Admin user. For more detailed information, refer to the section, 
IDREF="FM46099""Postmaster General," on page 5.PERFORMANCE="REQUIRED"In the Password field, enter the Postmaster General's password.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to continue.If the NetWare server has multiple volumes, INSTALL prompts for the volume on which the MHS Services 
database (the MHS subdirectory, which contains MHS mailboxes) is to be installed. Continue with 
IDREF="FM25270"Step 10.If the NetWare server has a single volume, INSTALL continues installing MHS Services. When the installation is complete, it displays the message, 
MOREINFO="NONE"MHS Installation completed successfully. Press ENTER to continue. Skip to 
IDREF="FM64604"Step 11.PERFORMANCE="REQUIRED"ID="FM25270"If the NetWare server on which you are installing MHS Services has multiple volumes, select the one on which you want to install the MHS Services database. 
PAGENUM=17 ID="BP18"When you select a volume, keep in mind the disk space requirements of MHS Services. (For more information about disk space requirements, see 
IDREF="FM62106""Hardware Requirements for MHS Services," on page 13.)INSTALL continues installing MHS Services. When the installation is complete, it displays the message, 
MOREINFO="NONE"MHS Installation completed successfully. Press ENTER to continue.PERFORMANCE="REQUIRED"ID="FM64604"Press 
MOREINFO="NONE"<Enter>.You are returned to the Other Installation Items/Products menu. You can continue installing optional products, or exit from the INSTALL program. MHS Services is a file- and directory-intensive application. By default, NetWare allocates thirteen percentage of the volume to directories. Over time, a messaging server with heavy message traffic can consume all of the available directory space. When this happens, the server sends users a broadcast message indicating that the number of directory entries has been exceeded.To prevent this problem, increase the percentage of the volume allocated to directory entries to 20. (If the problem still occurs, increase it even further.) You can change the parameter at the server console by typing the command:MOREINFO="NONE"Maximum percent of volume used by directory=20CLASS=OPTION MOREINFO="NONE"Or, you can enter this command in the AUTOEXEC.NCF file so that it will take effect whenever the server is re-booted.RENDERAS="SECT1"ID="FM65094"Loading MHS ServicesTo start or activate an MHS messaging server, you must load the MHS Services NLMs (MHS.NLM and MHSLIB.NLM) on a NetWare server. When activated, MHS Services provides message-delivery services to all users with mailboxes on the NetWare server.IDXID="w4605"BOOK="_idx" COLLECTION="nw41" TIDREF="i2440"IDXID="w4606"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"IDXID="w4607"BOOK="_idx" COLLECTION="nw41" TIDREF="i2439"
To load MHS Services manually, enter the following command at the NetWare server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD MHSAdd this command to your AUTOEXEC.NCF file, so that MHS Services is loaded automatically whenever you bring up your NetWare server.PAGENUM=18 ID="BP19"RENDERAS="SECT1"ID="FM41804"Unloading MHS ServicesIDXID="w4608"BOOK="_idx" COLLECTION="nw41" TIDREF="i2440"IDXID="w4609"BOOK="_idx" COLLECTION="nw41" TIDREF="i4668"IDXID="w4610"BOOK="_idx" COLLECTION="nw41" TIDREF="i2439"
You must unload and reload MHS Services after you change the configuration parameters (see IDREF="FM74858""Configuring MHS Services," on page 57). New parameters will not take effect until MHS Services is reloaded. Novell recommends that you unload MHS Services before bringing down the NetWare server for maintenance. (However, if you fail to do so, the shutdown procedure will unload MHS Services automatically.) You might also want to unload MHS Services when you are troubleshooting messaging problems.You can unload MHS Services by entering the following commands at the NetWare server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"UNLOAD MHS
UNLOAD MHSLIBBefore unloading, MHS.NLM completes the processing of any messages in progress. This can take several minutes, during which the NetWare server console is unavailable.You can also unload MHS Services from the MHSCON utility. If you do so, you can use the console for other tasks while MHS Services is unloading. To unload MHS Services from the MHSCON utility, follow this procedure.PERFORMANCE="REQUIRED"Select IDXID="w4611"BOOK="_idx" COLLECTION="nw41" TIDREF="i4146"CLASS=MENUITEM MOREINFO="NONE"Shut down MHS from the MHSCON Available Options menu.MHSCON prompts for confirmation.PERFORMANCE="REQUIRED"Select
CLASS=MENUITEM MOREINFO="NONE" Yes.MHSCON terminates and MHS Services is unloaded.
ID="FM24832"LABEL="3"PAGENUM=19 ID="BP20"ID="FM12795"Managing MHS MailboxesIDXID="w4612"BOOK="_idx" COLLECTION="nw41" TIDREF="i2632"
You must assign an MHS mailbox to each user, organizational role, group, or distribution list whose messages will be delivered by an MHS messaging server. (To find out how to define a foreign mailbox for an object whose messages are delivered to a foreign E-mail system, refer to IDREF="FM95390""Assigning Foreign E-Mail Addresses," on page 31.)As soon as you assign a mailbox to a user, that user can start the FirstMail application, and begin sending and receiving mail. To start FirstMail for DOS, users enter the MOREINFO="NONE"MAIL command at the DOS prompt. To start FirstMail for MS Windows, users choose the Run option from the Program Manager File menu, and enter the MOREINFO="NONE"WMAIL.EXE command. (Users can also create a program item for FirstMail for MS Windows.)You can use the graphic NetWare® Administrator utility (NWADMIN), the text-based NETADMIN utility, or the batch UIMPORT utility to manage MHS mailboxes. For more information about these utilities, and how to use them to add and modify objects, refer to the 
BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference manual. This chapter describes the properties you use to assign mailboxes to objects. It also explains how to assign, delete, and move mailboxes.RENDERAS="SECT1"ID="FM79868"MHS Mailbox PropertiesIDXID="w4613"BOOK="_idx" COLLECTION="nw41" TIDREF="i2306"
The properties you use to assign an MHS mailbox to an object vary, depending on the object type. You can assign MHS mailboxes to users and to other objects (organizational roles, groups, and distribution lists).In the current release, mailbox properties for organizations and organizational units are unused.(To find out how to assign MHS mailboxes, refer to IDREF="FM14312""Managing MHS Mailboxes," on page 20.)PAGENUM=20 ID="BP21"RENDERAS="SECT2"MHS Mailbox Properties for UsersIDXID="w4614"BOOK="_idx" COLLECTION="nw41" TIDREF="i4714"
When you assign an MHS mailbox to a user, you must define the following properties:MARK=BULLETIDXID="w4615"BOOK="_idx" COLLECTION="nw41" TIDREF="i2305"
Mailbox location, which identifies the messaging server on which the user's MHS mailbox is located.Locate the user's MHS mailbox on the NetWare server containing the user's home directory (or the directory where the user stores most document and data files). By doing so, you will minimize network traffic. To understand why, consider a user who is sending an attached file. If the user's MHS mailbox is on the same NetWare server as the file being attached, the user's E-mail application need not transfer the file between NetWare servers when it submits the file to MHS Services.IDXID="w4616"BOOK="_idx" COLLECTION="nw41" TIDREF="i2304"
Mailbox ID, which is the name of the subdirectory in which the user's incoming messages are stored. IDXID="w4617"BOOK="_idx" COLLECTION="nw41" TIDREF="i965"
If you do not assign a Mailbox ID, the administration utility automatically generates one from the user's login name.RENDERAS="SECT2"MHS Mailbox Properties for Other ObjectsIDXID="w4618"BOOK="_idx" COLLECTION="nw41" TIDREF="i3119"IDXID="w4619"BOOK="_idx" COLLECTION="nw41" TIDREF="i1618"IDXID="w4620"BOOK="_idx" COLLECTION="nw41" TIDREF="i1160"
When you assign an MHS mailbox to a distribution list, group, or organizational role, you must define a mailbox location. The mailbox location property for these objects identifies the MHS messaging server with the ability to IDXID="w4621"BOOK="_idx" COLLECTION="nw41" TIDREF="i1431"fan out messages addressed to the object (that is, the MHS messaging server that determines the users who are members or occupants of the object, and creates a copy of the message for each one). RENDERAS="SECT1"ID="FM14312"Managing MHS MailboxesIDXID="w4622"BOOK="_idx" COLLECTION="nw41" TIDREF="i2307"
This section explains how to manage MHS mailboxes with NWADMIN and UIMPORT. NETADMIN provides functionality similar to that provided by NWADMIN. If you prefer to use NETADMIN to manage mailboxes, refer to the instructions for NWADMIN.PAGENUM=21 ID="BP22"RENDERAS="SECT2"Managing MHS Mailboxes with NWADMINYou can use NWADMIN to assign, move, or delete MHS mailboxes. Two dialog boxes are available for managing MHS mailboxes: the object dialog box and the messaging server dialog box. You would use the object dialog box if you are assigning, moving, or deleting the MHS mailbox of MARK=BULLETAn individual objectMultiple objects with mailboxes on different MHS messaging servers.You would use the messaging server dialog box if you are assigning MHS mailboxes to, or deleting MHS mailboxes from, multiple objects on the same server.When you assign a mailbox to a user object, you identify the MHS messaging server on which the user's messages are stored. When you assign a mailbox to another class of object (distribution list, group, or organizational role), you identify the MHS messaging server responsible for fanning out messages addressed to the object.When you move a mailbox, mail in transit is automatically redirected to the new location.This section provides procedures for managing MHS mailboxes from both the object and server dialog boxes.To create a mailbox on, or delete a mailbox from, a messaging server, you must be logged in as a Postmaster for the messaging server. To move a mailbox from one messaging server to another, you must be logged in as a user who is a Postmaster for both the source and destination messaging servers.RENDERAS="SECT3"Managing MHS Mailboxes from the Object Dialog BoxFollow this procedure to assign or move an MHS mailbox with the object dialog box.PERFORMANCE="REQUIRED"To assign a mailbox when you create a user, group, or organizational role, follow this procedure.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Create option from the Object menu.
PAGENUM=22 ID="BP23"PERFORMANCE="REQUIRED"Select the object class from the New Object dialog box.PERFORMANCE="REQUIRED"Complete all the necessary fields on the Create form.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Define Additional Properties option.PERFORMANCE="REQUIRED"Choose the Create button.The object Identification page appears. Skip to IDREF="FM81134"Step 4.PERFORMANCE="REQUIRED"To assign a mailbox when you create a distribution list, follow this procedure.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Create option from the Object menu.PERFORMANCE="REQUIRED"Select Distribution List from the New Object dialog box.PERFORMANCE="REQUIRED"Type the distribution list name in the Distribution List Name field.PERFORMANCE="REQUIRED"Choose the Browser button beside the Mailbox Location field.PERFORMANCE="REQUIRED"Find and select the MHS messaging server on which you want to locate the distribution list's mailbox.PERFORMANCE="REQUIRED"Choose the Create button.NWADMIN creates the distribution list, and assigns it a mailbox on the selected MHS messaging server. PERFORMANCE="REQUIRED"To assign or move the mailbox of an existing object, click the object and select the 
CLASS=MENUITEM MOREINFO="NONE"Details... option from the Object menu.The object Identification page appears.PERFORMANCE="REQUIRED"ID="FM81134"Choose the Mailbox button.The Mailbox page appears (see 
IDREF="FM91910"Figure 3-1).
PAGENUM=23 ID="BP24"LABEL="3-1" FLOAT="0"ID="FM91910"Mailbox PageFILEREF="mailbox.tif"PERFORMANCE="REQUIRED"To assign or move the mailbox location, follow these steps.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Choose the Browser button beside the Mailbox Location field.PERFORMANCE="REQUIRED"Find and select the MHS messaging server on which you want to locate the object's mailbox.PERFORMANCE="REQUIRED"(Optionally) for user objects, define a Mailbox ID. If you leave the Mailbox ID field blank, NWADMIN automatically generates a mailbox ID for the user. If the generated mailbox ID is the same as an existing mailbox ID, NWADMIN prompts you to enter one manually.PAGENUM=24 ID="BP25"(The Mailbox ID field is not currently used for other objects.)PERFORMANCE="REQUIRED"Choose the OK button to save the new properties.To manage mailboxes from the object form in NETADMIN, select the object, select the CLASS=MENUITEM MOREINFO="NONE"View or edit properties of this object option, and then select the CLASS=MENUITEM MOREINFO="NONE"Mailbox Information option.RENDERAS="SECT3"Managing Mailboxes from the Messaging Server Dialog BoxFollow this procedure to assign or delete a mailbox with the server dialog box.PERFORMANCE="REQUIRED"Click the messaging server object and select the CLASS=MENUITEM MOREINFO="NONE"Details... option from the Object menu.PERFORMANCE="REQUIRED"Choose the Users button.NWADMIN displays the list of objects with mailboxes on the MHS messaging server (see 
IDREF="FM17097"Figure 3-2).
PAGENUM=25 ID="BP26"LABEL="3-2" FLOAT="0"ID="FM17097"Users at Messaging ServerFILEREF="users.tif"PERFORMANCE="REQUIRED"To assign object(s) mailboxes on the MHS messaging server, choose the Add... button. NWADMIN displays a list of objects in the current container. Select the object(s) to be assigned mailboxes on this MHS messaging server.For user objects, NWADMIN automatically generates a mailbox ID. If the generated mailbox ID is the same as an existing mailbox ID, NWADMIN prompts you to enter one manually.PERFORMANCE="REQUIRED"To delete an object's mailbox from this server, highlight the object and choose the Delete button.
PAGENUM=26 ID="BP27"When you delete an object's mailbox, the object can no longer receive mail.PERFORMANCE="REQUIRED"Choose the OK button to save the changes.If you have deleted one or more user mailboxes, NWADMIN displays the following prompt for each one:
MOREINFO="NONE" Do you want to delete the existing mail for mail_idMOREINFO="NONE"? Select 
CLASS=MENUITEM MOREINFO="NONE"Yes to delete the user's mailbox. (If you delete the mailbox, the mail subdirectory and all the messages it contains will be deleted.) Select 
CLASS=MENUITEM MOREINFO="NONE"No to retain the mailbox. If you retain the mailbox, remember to delete the mail manually later.To manage mailboxes from the messaging server form in NETADMIN, select the messaging server, select the CLASS=MENUITEM MOREINFO="NONE"View or edit properties of this object option, and then select the CLASS=MENUITEM MOREINFO="NONE"Messaging Server Properties option. Add or remove mailboxes using the Users field.RENDERAS="SECT2"Assigning Mailboxes with UIMPORTIDXID="w4623"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"
When you use UIMPORT to import users from an existing database into an NDS database, you can also import user mailbox information. Use the UIMPORT Mailbox Location and Mailbox ID fields.If you leave the Mailbox ID field blank, UIMPORT automatically assigns a mailbox ID generated from the user's login name. If the generated mailbox ID is the same as an existing mailbox ID, UIMPORT will not assign a mailbox to the user.LABEL="4"PAGENUM=27 ID="BP28"ID="FM90793"Using GatewaysYou can install and configure optional gateways to extend messaging connectivity in your network. A gateway is a software program that does either of the following:MARK=BULLETSupplies additional messaging features, such as access to a gateway service (for example, a fax service or an electronic bulletin board).Provides access to another protocol or messaging system. (For example, a cc:Mail* gateway allows NetWare® MHS(tm) users to exchange messages with users in a cc:Mail environment.)To use a gateway, you must perform the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Install the gateway by following the instructions provided in the gateway documentation.Configure the MHS messaging server that is attached to the gateway.Assign foreign E-mail aliases to NDS objects whose mailboxes are located on an MHS messaging server (if necessary). Some gateways require that you assign a foreign E-mail alias to each object that will be sending or receiving mail through the gateway. Refer to the gateway documentation to find out if you need to define foreign E-mail aliases.Assign foreign E-mail addresses to NDS objects whose mailboxes are located on a foreign E-mail system reached through the gateway.To complete the first task, refer to the gateway documentation. This chapter provides instructions for the remaining tasks.PAGENUM=28 ID="BP29"RENDERAS="SECT1"ID="FM98691"Configuring an MHS Messaging Server to Support a GatewayIDXID="w4624"BOOK="_idx" COLLECTION="nw41" TIDREF="i971"IDXID="w4625"BOOK="_idx" COLLECTION="nw41" TIDREF="i4343"IDXID="w4626"BOOK="_idx" COLLECTION="nw41" TIDREF="i1593"
Each gateway to which an MHS messaging server will deliver messages, and from which it will receive messages, must be defined as a supported gateway. Follow this procedure to use the NetWare® Administrator (NWADMIN) utility to define supported gateways for an MHS messaging server.To define a supported gateway on a messaging server, you must be logged in as a Postmaster for the messaging server.PERFORMANCE="REQUIRED"Click the messaging server object and select the CLASS=MENUITEM MOREINFO="NONE"Details... option from the Object menu.PERFORMANCE="REQUIRED"Choose the Supported Gateways button.PERFORMANCE="REQUIRED"Choose the Add... button. NWADMIN displays the Supported Gateways dialog box.PERFORMANCE="REQUIRED"In the Name field, enter the name of the gateway. The gateway name can be up to eight characters long, and must consist of valid DOS filename characters. (Refer to the gateway documentation for specific naming guidelines.) The name must be unique within your network. If you have two fax gateways, for example, you could name them "FAXGATE1" and "FAXGATE2."PERFORMANCE="REQUIRED"In the Type field, enter the address type supported by the gateway.You can type a value, or choose the Browser button to select one from a list. Refer to the gateway documentation to find out what value to enter.Note: For many gateways, the Type is the key used in the extended address for messages sent to this gateway. For example, a gateway requires that addresses be entered in the format: 
user@
gateway {FAX:
phone_number}. Therefore, the address type for this gateway is "FAX."
PAGENUM=29 ID="BP30"PERFORMANCE="REQUIRED"Choose the OK button to save the new gateway.To define supported gateways in NETADMIN, select the messaging server object, select the CLASS=MENUITEM MOREINFO="NONE"View or edit properties of this object option, and then select the CLASS=MENUITEM MOREINFO="NONE"Messaging CLASS=MENUITEM MOREINFO="NONE"Server Properties option. Define supported gateways in the Supported gateway field, in the format type/name.RENDERAS="SECT1"Assigning Foreign E-Mail Aliases to NDS ObjectsIDXID="w4627"BOOK="_idx" COLLECTION="nw41" TIDREF="i301"IDXID="w4628"BOOK="_idx" COLLECTION="nw41" TIDREF="i2632"
Some gateways require that you assign a foreign E-mail alias to an NDS object if the object will send or receive messages through the gateway.A IDXID="w4629"BOOK="_idx" COLLECTION="nw41" TIDREF="i1537"foreign E-mail alias is the object's address as it is known in the foreign messaging system. For example, if an NDS user receives mail from X.400 users through an X.400 gateway, the NDS user might need to be assigned an X.400 alias.Objects can have multiple foreign E-mail aliases, one for each gateway through which they communicate. You can assign these aliases when you create an object, or at a later time.Follow this procedure to use the NWADMIN utility to assign a foreign E-mail alias.If your gateway provides a facility for assigning foreign E-mail aliases, use that facility instead of the procedure described here.PERFORMANCE="REQUIRED"To assign a foreign E-mail alias when you create an object, follow this procedure.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Complete all the necessary fields on the Create form.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Define Additional Properties option.PERFORMANCE="REQUIRED"Choose the Create button.The object Identification page appears. Skip to IDREF="FM72659"Step 3.PERFORMANCE="REQUIRED"To assign a foreign E-mail alias to an existing object, click the object and select the 
CLASS=MENUITEM MOREINFO="NONE"Details... option from the Object menu.The object Identification page appears.PERFORMANCE="REQUIRED"ID="FM72659"Choose the Foreign E-mail address button.
PAGENUM=30 ID="BP31"PERFORMANCE="REQUIRED"Choose the Add... button below the list of Foreign E-Mail Aliases.The Foreign E-Mail Alias dialog box appears (see 
IDREF="FM82923"Figure 4-1). LABEL="4-1" FLOAT="0"ID="FM82923"Foreign E-Mail Alias Dialog BoxFILEREF="fealias.tif"PERFORMANCE="REQUIRED"In the Address field, enter the object's address, in the format required by the foreign E-mail environment.Refer to the gateway documentation to find out what format to use.PERFORMANCE="REQUIRED"In the Type field, enter the address type used by the foreign E-mail environment.The type must match the address type defined for the gateway (see 
IDREF="FM98691""Configuring an MHS Messaging Server to Support a Gateway" on page 28). When you select the browser button for this field, a list of supported alias types appears.PERFORMANCE="REQUIRED"Choose the OK button to save the new alias.To define foreign E-mail aliases in NETADMIN, select the object, select the CLASS=MENUITEM MOREINFO="NONE"View or edit properties of this object option, and then select the CLASS=MENUITEM MOREINFO="NONE"Mailbox CLASS=MENUITEM MOREINFO="NONE"Information option. Define foreign E-mail aliases in the Foreign E-mail alias field.PAGENUM=31 ID="BP32"RENDERAS="SECT1"ID="FM95390"Assigning Foreign E-Mail AddressesIDXID="w4630"BOOK="_idx" COLLECTION="nw41" TIDREF="i301"IDXID="w4631"BOOK="_idx" COLLECTION="nw41" TIDREF="i2632"
You must assign a foreign E-mail address to NDS objects with mailboxes on a foreign E-mail system. The IDXID="w4632"BOOK="_idx" COLLECTION="nw41" TIDREF="i1535"foreign E-mail address is the user's address on the foreign system. For example, if a user wishes to have E-mail messages delivered to an SMTP mailbox, you must assign that user an SMTP address. Or, if you have defined a UNIX user as an external entity in the NDS directory, and if messages for that user are delivered to an SMTP gateway, you can assign that user an E-mail address of the type "SMTP."An NDS object can have a mailbox or a foreign E-mail address, but not both.You can assign foreign E-mail addresses when you create an object or at a later time.Follow this procedure to use the NWADMIN utility to assign a foreign E-mail address.If your gateway provides a facility for assigning foreign E-mail addresses, use that facility instead of the procedure described here.PERFORMANCE="REQUIRED"To assign a foreign E-mail address when you create an object, follow this procedure.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Complete all the necessary fields on the Create form.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Define Additional Properties option.PERFORMANCE="REQUIRED"Choose the Create button.The object Identification page appears. Skip to IDREF="FM59263"Step 3.PERFORMANCE="REQUIRED"To assign a foreign E-mail address to an existing object, click the object and select the 
CLASS=MENUITEM MOREINFO="NONE"Details... option from the Object menu.The object Identification page appears. PERFORMANCE="REQUIRED"ID="FM59263"Choose the Foreign E-mail address button.PERFORMANCE="REQUIRED"Choose the Set button below the list of Foreign E-Mail Addresses.The Foreign E-Mail Address dialog box appears (see 
IDREF="FM46308"Figure 4-2). 
PAGENUM=32 ID="BP33"LABEL="4-2" FLOAT="0"ID="FM46308"Foreign E-Mail Address Dialog BoxFILEREF="feaddr.tif"PERFORMANCE="REQUIRED"In the Address field, enter the object's address, in the format required by the foreign E-mail environment.Refer to the gateway documentation to find out what format to use.PERFORMANCE="REQUIRED"In the Type field, enter the address type used by the foreign E-mail environment.The type must match the address type defined for the gateway (see 
IDREF="FM98691""Configuring an MHS Messaging Server to Support a Gateway" on page 28). When you select the browser button for this field, a list of supported alias types appears.PERFORMANCE="REQUIRED"Choose the OK button to save the new address.To define a foreign E-mail address in NETADMIN, select the object, select the CLASS=MENUITEM MOREINFO="NONE"View or edit properties of this object option, and then select the CLASS=MENUITEM MOREINFO="NONE"Mailbox CLASS=MENUITEM MOREINFO="NONE"Information option. Define a foreign E-mail address in the Foreign E-mail address field.LABEL="5"PAGENUM=33 ID="BP34"ID="FM56530"Monitoring and Maintaining an MHS Messaging ServerThis chapter explains how to monitor and maintain an MHS messaging server. The tasks are performed by a NetWare® MHS(tm) Services administrator on the NetWare server on which MHS Services is installed.The following tasks are described in this chapter:MARK=BULLETMonitoring statisticsMonitoring messaging server eventsMonitoring and administering message flowChecking the Postmaster's mailboxConfiguring MHS ServicesUpdating the extract fileThe chapter also provides instructions for starting the MHSCON utility, which you will use to perform many of these tasks.RENDERAS="SECT1"Starting the MHSCON UtilityIDXID="w4633"BOOK="_idx" COLLECTION="nw41" TIDREF="i2441"IDXID="w4634"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
The MHSCON utility provides options for administering your messaging server. To load the utility, enter the following command at the NetWare server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD MHSCONIf MHS Services NLMs are not already loaded, they will be loaded automatically when you load MHSCON.PAGENUM=34 ID="BP35"The Available Options menu appears (see IDREF="FM80272"Figure 5-1). From this menu, you can perform the tasks described in the following sections.LABEL="5-1" FLOAT="0"ID="FM80272"MHSCON Available Options MenuFILEREF="mhscon.tif"RENDERAS="SECT1"ID="FM64236"Monitoring StatisticsIDXID="w4635"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w4636"BOOK="_idx" COLLECTION="nw41" TIDREF="i4276"
MHS Services cumulates messaging statistics. These statistics provide information about the volume of message traffic on your MHS messaging server and between your server and other messaging servers in the message-routing group. You can use this information to balance the messaging load. With the NWADMIN utility, you can move mailboxes to messaging servers with less messaging traffic. You can access the statistics in the following ways:MARK=BULLETFrom the Messaging Server Statistics screen in the MHSCON utility.You can output statistics to a snapshot file (a file containing a "snapshot" of the statistics at a given point in time).From the Statistics Log file.If the IDREF="FM12797"Statistics-Log-Enabled parameter (see page 65) is set to TRUE, MHS Services appends statistics records to the statistics log, located in MHS\SYS\IDXID="w4637"BOOK="_idx" COLLECTION="nw41" TIDREF="i4282"
STATSLOG.DAT. The PAGENUM=35 ID="BP36"IDREF="FM31516"Statistics-Log-Interval parameter (see page 65) allows you to specify how often statistics records will be written out. When the file reaches the size specified in the IDREF="FM37444"Statistics-Log-Size parameter (see page 65), MHS Services renames the STATSLOG.DAT file to IDXID="w4638"BOOK="_idx" COLLECTION="nw41" TIDREF="i4283"
STATSLOG.OLD (overwriting the existing STATSLOG.OLD file, if any), and starts writing statistics to the new STATSLOG.DAT file. For information about the format of the snapshot and log files, refer to IDREF="FM20359""Format of the Statistics Files," on page 40.The statistics files contain more detailed statistics than the Messaging Server Statistics screen. In addition to statistics on message transfers and connections, they include statistics on attachments, recipients, and delivery and nondelivery notifications.This section provides instructions for viewing, resetting, and writing statistics out to a snapshot file. It also explains the messaging statistics displayed by the CLASS=MENUITEM MOREINFO="NONE"Statistics option in MHSCON and describes the format of the statistics files.RENDERAS="SECT2"Viewing, Writing Out, and Resetting Messaging StatisticsWrite the statistics to a file before resetting them.IDXID="w4639"BOOK="_idx" COLLECTION="nw41" TIDREF="i4766"IDXID="w4640"BOOK="_idx" COLLECTION="nw41" TIDREF="i4276"
To view messaging statistics, write them to a file, or reset them, follow this procedure.PERFORMANCE="REQUIRED"Select the IDXID="w4641"BOOK="_idx" COLLECTION="nw41" TIDREF="i4278"CLASS=MENUITEM MOREINFO="NONE"Statistics option from the MHSCON Available Options menu.The MHS Messaging Server Statistics window appears (see 
IDREF="FM26776"Figure 5-2).
PAGENUM=36 ID="BP37"LABEL="5-2" FLOAT="0"ID="FM26776"MHS Messaging Server Statistics WindowFILEREF="statisti.tif"This window displays summary statistics for all messaging servers in the message-routing group. Refer to 
IDREF="FM70979""Interpreting Messaging Statistics," on page 37 for an explanation of the statistics on this window.From this window, you can perform the following tasks:
MARK=BULLETDisplay the statistics for a specific server (continue with IDREF="FM42210"Step 2).Write the summary statistics to a disk file (skip to IDREF="FM97831"Step 3).Reset the summary statistics (skip to IDREF="FM65834"Step 4).PERFORMANCE="REQUIRED"ID="FM42210"To view the statistics for a specific server, follow these steps.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the Statistics For field.The list of messaging servers appears. PERFORMANCE="REQUIRED"Select the messaging server.MHSCON displays the statistics for the server. From this window, you can perform the following tasks:MARK=BULLETWrite the statistics for this server to a file (continue with IDREF="FM97831"Step 3).PAGENUM=37 ID="BP38"Reset the statistics for this server (skip to IDREF="FM65834"Step 4).PERFORMANCE="REQUIRED"ID="FM97831"IDXID="w4642"BOOK="_idx" COLLECTION="nw41" TIDREF="i4855"IDXID="w4643"BOOK="_idx" COLLECTION="nw41" TIDREF="i4276"
To write the displayed statistics to a file, perform these steps.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F6>.MHSCON prompts for a filename.PERFORMANCE="REQUIRED"Enter the name of the file in which you want to store the statistics.The file is created in the MHS\SYS directory on the volume on which you installed MHS Services. It is in Comma-Separated Value (CSV) format. Refer to IDREF="FM20359""Format of the Statistics Files," on page 40 for a detailed description of the file format.PERFORMANCE="REQUIRED"IDXID="w4644"BOOK="_idx" COLLECTION="nw41" TIDREF="i3813"IDXID="w4645"BOOK="_idx" COLLECTION="nw41" TIDREF="i4276"ID="FM65834"To reset the displayed statistics to zero, press 
MOREINFO="NONE"<F8> and select 
CLASS=MENUITEM MOREINFO="NONE"Yes to confirm the reset.RENDERAS="SECT2"ID="FM70979"Interpreting Messaging StatisticsIDXID="w4646"BOOK="_idx" COLLECTION="nw41" TIDREF="i4276"
The CLASS=MENUITEM MOREINFO="NONE"Statistics option in MHSCON displays the following types of statistics:MARK=BULLETStatistics for message traffic between your MHS messaging server and other messaging servers in the message-routing groupStatistics for message traffic on your MHS messaging server (that is, deliveries to user mailboxes, and pick-up of messages submitted by applications).Summary statistics for message traffic on your MHS messaging server and message traffic between your MHS messaging server and all other messaging servers in the message-routing groupAll statistics displayed are cumulative since the last reset.PAGENUM=38 ID="BP39"IDXID="w4647"BOOK="_idx" COLLECTION="nw41" TIDREF="i4276"IDREF="FM77087"Table 5-1 describes the fields displayed on the Messaging Server Statistics window (IDREF="FM26776"Figure 5-2).LABEL="5-1" PGWIDE=1 TOCENTRY="1"ID="FM77087" Messaging StatisticsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"StatisticCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Time of Last ResetCOLNAME=2 ROTATE="0" MOREROWS="0"Date and time of the last reset of the currently-displayed statistics.SPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"IDXID="w4648"BOOK="_idx" COLLECTION="nw41" TIDREF="i4556"Transfer Out MessagesCOLNAME=1 ROTATE="0" MOREROWS="0"CountCOLNAME=2 ROTATE="0" MOREROWS="0"Total number of messages your MHS messaging server delivered. The Count statistic helps you determine with which MHS messaging servers your users communicate most frequently. (That is, the messaging server with the highest Count statistics is the one with which your users communicate most often.) You might choose to install a high-speed link to servers with which your users communicate frequently.COLNAME=1 ROTATE="0" MOREROWS="0"Total SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Total size of messages your server delivered. You might choose to install high-speed, low-cost links to MHS messaging servers with high Total Size values. COLNAME=1 ROTATE="0" MOREROWS="0"Maximum SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Largest message delivered. COLNAME=1 ROTATE="0" MOREROWS="0"Average SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Average size of messages your server delivered. Average size is calculated by dividing Total Size by Count.COLNAME=1 ROTATE="0" MOREROWS="0"Current RateCOLNAME=2 ROTATE="0" MOREROWS="0"Number of messages your server is delivering per minute. COLNAME=1 ROTATE="0" MOREROWS="0"Peak RateCOLNAME=2 ROTATE="0" MOREROWS="0"The highest Current Rate since the time of last reset. Try to schedule server activities (such as backups) so that they do not coincide with peak rate periods.SPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"IDXID="w4649"BOOK="_idx" COLLECTION="nw41" TIDREF="i4554"Transfer In MessagesCOLNAME=1 ROTATE="0" MOREROWS="0"CountCOLNAME=2 ROTATE="0" MOREROWS="0"Total number of messages your MHS messaging server received. The Count statistic helps you determine with which MHS messaging servers your users communicate most frequently. (That is, the messaging server with the highest Count statistics is the one with which your users communicate most often.) Install high-speed links to servers with which your users communicate frequently. You can also compare the Count statistic on different MHS messaging servers. If one server has a much higher Count of messages transferred to all servers, you might choose to move users from that server to balance the load.COLNAME=1 ROTATE="0" MOREROWS="0"Total SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Total size of messages your MHS messaging server received. You might choose to install high-speed, low-cost links to MHS messaging servers with high Total Size values. You can also compare the Total Size statistic on different MHS messaging servers. If one server has a much higher Total Size for messages transferred to all servers, you might choose to move users from that server to balance the load.COLNAME=1 ROTATE="0" MOREROWS="0"Maximum SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Largest message your server received. COLNAME=1 ROTATE="0" MOREROWS="0"Average SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Average size of messages your server received. Average Size is calculated by dividing Total Size by Count.COLNAME=1 ROTATE="0" MOREROWS="0"Current RateCOLNAME=2 ROTATE="0" MOREROWS="0"Number of messages your server is receiving per minute. COLNAME=1 ROTATE="0" MOREROWS="0"Peak RateCOLNAME=2 ROTATE="0" MOREROWS="0"The highest Current Rate since the time of last reset. Try to schedule server activities (such as backups) so that they do not coincide with peak rate periods.SPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"IDXID="w4650"BOOK="_idx" COLLECTION="nw41" TIDREF="i787"Connection InformationCOLNAME=1 ROTATE="0" MOREROWS="0"Total Successful ConnectionsCOLNAME=2 ROTATE="0" MOREROWS="0"The number of times your server connected successfully.COLNAME=1 ROTATE="0" MOREROWS="0"Total Unsuccessful ConnectionsCOLNAME=2 ROTATE="0" MOREROWS="0"The number of times your server attempted to connect and failed. If this number is high, check the physical connections to this messaging server.COLNAME=1 ROTATE="0" MOREROWS="0"Last Successful ConnectionCOLNAME=2 ROTATE="0" MOREROWS="0"The last time your server connected successfully.COLNAME=1 ROTATE="0" MOREROWS="0"Last Unsuccessful ConnectionCOLNAME=2 ROTATE="0" MOREROWS="0"The last time your server attempted to connect and failed.PAGENUM=39 ID="BP40"When you display the statistics for a remote messaging server, the statistics window contains sections for "Transfer In" and "Transfer Out" Messages. When you display statistics for local traffic, the window contains sections for "Submitted" and "Delivered" Messages. The former records statistics for messages submitted by local users, and the latter records statistics for messages delivered to user mailboxes.PAGENUM=40 ID="BP41"RENDERAS="SECT2"ID="FM20359"Format of the Statistics FilesThe statistics files are ASCII text files. Statistics records are output to the files in Comma-Separated Value (CSV) format (that is, each field is separated from the next by a comma). This format allows you to export statistics records to spreadsheet and database programs to produce reports on system performance.IDREF="FM52296"Table 5-2 lists the fields in the statistics file, and their data types. The data type can beMARK=BULLETString. A text string enclosed in double quotation marks.Time. An unsigned long (32-bit) decimal number, representing the number of seconds since 12:00 a.m., January 1, 1970. Suggestion: Convert time statistics to a more user-friendly format when you import them into a spreadsheet.Number. An unsigned long (32-bit) decimal number.(Fields that appear on the Messaging Server Statistics window are referenced by the name displayed in that window. These fields are described in the section, IDREF="FM70979""Interpreting Messaging Statistics," on page 37.)LABEL="5-2" PGWIDE=1 TOCENTRY="1"ID="FM52296" Statistics File FieldsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="3*"COLNAME=2 COLWIDTH="26*"COLNAME=3 COLWIDTH="6*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"#COLNAME=2 ROTATE="0" MOREROWS="0"FieldCOLNAME=3 ROTATE="0" MOREROWS="0"Data TypeCOLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"Statistics ForCOLNAME=3 ROTATE="0" MOREROWS="0"StringCOLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"Time/Date of entryCOLNAME=3 ROTATE="0" MOREROWS="0"TimeCOLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"Time of Last ResetCOLNAME=3 ROTATE="0" MOREROWS="0"TimeSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Transfer Out/Delivery StatisticsCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"4COLNAME=2 ROTATE="0" MOREROWS="0"CountCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"5COLNAME=2 ROTATE="0" MOREROWS="0"Total Size (KB)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"6COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"7COLNAME=2 ROTATE="0" MOREROWS="0"Average Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"8COLNAME=2 ROTATE="0" MOREROWS="0"Current Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"9COLNAME=2 ROTATE="0" MOREROWS="0"Peak Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"10COLNAME=2 ROTATE="0" MOREROWS="0"Total RecipientsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"11COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"12COLNAME=2 ROTATE="0" MOREROWS="0"Average Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"13COLNAME=2 ROTATE="0" MOREROWS="0"Total AttachmentsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"14COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"15COLNAME=2 ROTATE="0" MOREROWS="0"Average Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Transfer In/Submission StatisticsCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"16COLNAME=2 ROTATE="0" MOREROWS="0"CountCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"17COLNAME=2 ROTATE="0" MOREROWS="0"Total Size (KB)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"18COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"19COLNAME=2 ROTATE="0" MOREROWS="0"Average Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"20COLNAME=2 ROTATE="0" MOREROWS="0"Current Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"21COLNAME=2 ROTATE="0" MOREROWS="0"Peak Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"22COLNAME=2 ROTATE="0" MOREROWS="0"Total RecipientsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"23COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"24COLNAME=2 ROTATE="0" MOREROWS="0"Average Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"25COLNAME=2 ROTATE="0" MOREROWS="0"Total AttachmentsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"26COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"27COLNAME=2 ROTATE="0" MOREROWS="0"Average Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Delivery Notification StatisticsCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"28COLNAME=2 ROTATE="0" MOREROWS="0"CountCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"29COLNAME=2 ROTATE="0" MOREROWS="0"Total Size (KB)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"30COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"31COLNAME=2 ROTATE="0" MOREROWS="0"Average Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"32COLNAME=2 ROTATE="0" MOREROWS="0"Current Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"33COLNAME=2 ROTATE="0" MOREROWS="0"Peak Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"34COLNAME=2 ROTATE="0" MOREROWS="0"Total RecipientsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"35COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"36COLNAME=2 ROTATE="0" MOREROWS="0"Average Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"37COLNAME=2 ROTATE="0" MOREROWS="0"Total AttachmentsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"38COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"39COLNAME=2 ROTATE="0" MOREROWS="0"Average Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Nondelivery Notification StatisticsCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"40COLNAME=2 ROTATE="0" MOREROWS="0"CountCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"41COLNAME=2 ROTATE="0" MOREROWS="0"Total Size (KB)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"42COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"43COLNAME=2 ROTATE="0" MOREROWS="0"Average Size (bytes)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"44COLNAME=2 ROTATE="0" MOREROWS="0"Current Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"45COLNAME=2 ROTATE="0" MOREROWS="0"Peak Rate (messages/minute)COLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"46COLNAME=2 ROTATE="0" MOREROWS="0"Total RecipientsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"47COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"48COLNAME=2 ROTATE="0" MOREROWS="0"Average Recipients/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"49COLNAME=2 ROTATE="0" MOREROWS="0"Total AttachmentsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"50COLNAME=2 ROTATE="0" MOREROWS="0"Maximum Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"51COLNAME=2 ROTATE="0" MOREROWS="0"Average Attachments/MessageCOLNAME=3 ROTATE="0" MOREROWS="0"NumberSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Connection StatisticsCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"52COLNAME=2 ROTATE="0" MOREROWS="0"Total Successful ConnectionsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"53COLNAME=2 ROTATE="0" MOREROWS="0"Total Unsuccessful ConnectionsCOLNAME=3 ROTATE="0" MOREROWS="0"NumberCOLNAME=1 ROTATE="0" MOREROWS="0"54COLNAME=2 ROTATE="0" MOREROWS="0"Last Successful ConnectionCOLNAME=3 ROTATE="0" MOREROWS="0"TimeCOLNAME=1 ROTATE="0" MOREROWS="0"55COLNAME=2 ROTATE="0" MOREROWS="0"Last Unsuccessful ConnectionCOLNAME=3 ROTATE="0" MOREROWS="0"TimePAGENUM=43 ID="BP42"RENDERAS="SECT1"Monitoring MHS Messaging Server EventsIf users report message-delivery problems, you can use the following tools to troubleshoot them:MARK=BULLETOngoing Events screen.The IDXID="w4651"BOOK="_idx" COLLECTION="nw41" TIDREF="i3072"
Ongoing Events screen displays event messages as events occur.IDXID="w4652"BOOK="_idx" COLLECTION="nw41" TIDREF="i1360"
Event log.MHS Services appends records to the event log, located in MHS\SYS\MHSLOG.TXT, until the file reaches the size specified in the IDREF="FM62086"Log-File-Size parameter (see page 62). When the file reaches this size, MHS Services begins writing event records to the beginning of the file. To find the most recent entry in the file, look for the text MOREINFO="NONE"***The End***. The entry immediately preceding this line is the last entry written to the log.You can filter events written to both the Ongoing Events screen and the event log by the severity level of the event and the MHS Services subsystem that produced it. PAGENUM=44 ID="BP43"This section explains how to set the filters for the Ongoing Events screen and the event log. It provides instructions for monitoring system activity using the Ongoing Events screen, and for viewing and resetting the log file. It also explains how to interpret event records.RENDERAS="SECT2"ID="FM77848"Setting Event Log FiltersIDXID="w4653"BOOK="_idx" COLLECTION="nw41" TIDREF="i1360"IDXID="w4654"BOOK="_idx" COLLECTION="nw41" TIDREF="i1507"
You can set filters to limit the events written to the log file or displayed in the Ongoing Events screen. You can filter events by severity level and MHS Services subsystem. (IDREF="FM23454"Table 5-3 lists the MHS Services severity levels and IDREF="FM42917"Table 5-4 lists the MHS Services subsystems.)LABEL="5-3" PGWIDE=0 TOCENTRY="1"IDXID="w4655"BOOK="_idx" COLLECTION="nw41" TIDREF="i4114"ID="FM23454" MHS Services Severity LevelsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Severity LevelCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4656"BOOK="_idx" COLLECTION="nw41" TIDREF="i1344"
ErrorCOLNAME=2 ROTATE="0" MOREROWS="0"An error that prevents successful completion of a task (such as inability to connect to another messaging server).COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4657"BOOK="_idx" COLLECTION="nw41" TIDREF="i4815"
WarningCOLNAME=2 ROTATE="0" MOREROWS="0"An error that does not prevent successful completion of a task. MHS Services uses defaults or makes assumptions necessary to allow processing to be completed.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4658"BOOK="_idx" COLLECTION="nw41" TIDREF="i1796"
InformationalCOLNAME=2 ROTATE="0" MOREROWS="0"Normal MHS processing (such as successful message deliveries).LABEL="5-4" PGWIDE=0 TOCENTRY="1"IDXID="w4659"BOOK="_idx" COLLECTION="nw41" TIDREF="i4327"ID="FM42917" MHS Services SubsystemsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SubsystemCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4660"BOOK="_idx" COLLECTION="nw41" TIDREF="i4316"
SubmissionCOLNAME=2 ROTATE="0" MOREROWS="0"Picks up messages submitted to MHS by applications.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4661"BOOK="_idx" COLLECTION="nw41" TIDREF="i993"
DeliveryCOLNAME=2 ROTATE="0" MOREROWS="0"Delivers messages to the recipients' mailboxes.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4662"BOOK="_idx" COLLECTION="nw41" TIDREF="i4555"
Transfer InCOLNAME=2 ROTATE="0" MOREROWS="0"Picks up messages received from a gateway or another server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4663"BOOK="_idx" COLLECTION="nw41" TIDREF="i4557"
Transfer OutCOLNAME=2 ROTATE="0" MOREROWS="0"Delivers messages to a gateway or another server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4664"BOOK="_idx" COLLECTION="nw41" TIDREF="i3908"
RoutingCOLNAME=2 ROTATE="0" MOREROWS="0"Consults the address information on the message to determine where to deliver the message.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4665"BOOK="_idx" COLLECTION="nw41" TIDREF="i1419"
ExtractCOLNAME=2 ROTATE="0" MOREROWS="0"Generates an extract file, which MHS applications use as the basis for their Address Books.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4666"BOOK="_idx" COLLECTION="nw41" TIDREF="i853"
CoreCOLNAME=2 ROTATE="0" MOREROWS="0"Controls the initiation of the other subsystems, as well as system startup and shutdown.PAGENUM=45 ID="BP44"When MHS Services is loaded, the severity level filters are reset to the values specified for the IDREF="FM76547"Log-Error-Events parameter (see page 62), the IDREF="FM52192"Log-Warning-Events parameter (see page 63), and the IDREF="FM83669"Log-Info-Events parameter (see page 62), if these parameters are present in the MHS Services configuration file (SYS:SYSTEM\MHS.CFG). To set event log filters for a specific subsystem or severity level, follow this procedure.PERFORMANCE="REQUIRED"Select the IDXID="w4667"BOOK="_idx" COLLECTION="nw41" TIDREF="i1361"CLASS=MENUITEM MOREINFO="NONE"Event Logs option from the MHSCON Available Options menu.The Event Log Options menu appears.PERFORMANCE="REQUIRED"Select the 
IDXID="w4668"BOOK="_idx" COLLECTION="nw41" TIDREF="i4091"CLASS=MENUITEM MOREINFO="NONE"Set Event Log Filters option.The MHS Log Event Filters form appears (see 
IDREF="FM76031"Figure 5-3).
PAGENUM=46 ID="BP45"LABEL="5-3" FLOAT="0"ID="FM76031"MHS Log Event Filters FormFILEREF="filters.tif"PERFORMANCE="REQUIRED"Set the Filter For field to 
CLASS=MENUITEM MOREINFO="NONE"Log File or 
CLASS=MENUITEM MOREINFO="NONE"Ongoing Events.PERFORMANCE="REQUIRED"Select the Subsystems for which you want to filter entries.To suppress the logging of entries for a subsystem, move the cursor to the subsystem, press 
MOREINFO="NONE"<Enter>, and select 
CLASS=MENUITEM MOREINFO="NONE"Off. To turn on the logging of entries for a subsystem, move the cursor to the subsystem, press 
MOREINFO="NONE"<Enter>, and select 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Select the severity levels for which you want to filter entries.To suppress the logging of entries for a severity level, move the cursor to the severity level, press 
MOREINFO="NONE"<Enter>, and select 
CLASS=MENUITEM MOREINFO="NONE"Off. To turn on the logging of entries for a severity level, move the cursor to the severity level, press 
MOREINFO="NONE"<Enter>, and select 
CLASS=MENUITEM MOREINFO="NONE"On.RENDERAS="SECT2"Monitoring System ActivityIDXID="w4669"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w4670"BOOK="_idx" COLLECTION="nw41" TIDREF="i3071"
To monitor system activity, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Event Logs option from the MHSCON Available Options menu.The Event Log Options menu appears.PERFORMANCE="REQUIRED"Select the 
IDXID="w4671"BOOK="_idx" COLLECTION="nw41" TIDREF="i4764"CLASS=MENUITEM MOREINFO="NONE"View Ongoing Events option.For information about the format of event records, refer to 
IDREF="FM11767""Interpreting Event Records," on page 47.
PAGENUM=47 ID="BP46"RENDERAS="SECT2"Viewing the Event LogIDXID="w4672"BOOK="_idx" COLLECTION="nw41" TIDREF="i4766"
To display the event log, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Event Logs option from the MHSCON Available Options menu.The Event Log Options menu appears.PERFORMANCE="REQUIRED"Select the 
IDXID="w4673"BOOK="_idx" COLLECTION="nw41" TIDREF="i4763"CLASS=MENUITEM MOREINFO="NONE"View Event Log File option.MHSCON displays the log file. MHS Services appends records to the log file, located in MHS\SYS\MHSLOG.TXT, until the file reaches the maximum size specified in the 
IDREF="FM62086"Log-File-Size parameter (see page 62). When the file reaches this size, MHS Services begins writing text records to the beginning of the file. To find the most recent entry in the file, look for the text string 
MOREINFO="NONE"*** The End ***. The entry immediately before this line is the last entry written to the log.For information about the format of event records, refer to the following section, "
IDREF="FM11767"Interpreting Event Records ."RENDERAS="SECT2"ID="FM11767"Interpreting Event RecordsIDXID="w4674"BOOK="_idx" COLLECTION="nw41" TIDREF="i1362"IDXID="w4675"BOOK="_idx" COLLECTION="nw41" TIDREF="i1546"IDXID="w4676"BOOK="_idx" COLLECTION="nw41" TIDREF="i1360"
Event records are stored in Comma-Separated Value (CSV) format (that is, each field in an event record is separated from the next by a comma). This format allows you to export event records to spreadsheet and database programs to produce reports on system performance.IDREF="FM30917"Table 5-5 describes the elements of the event record.LABEL="5-5" PGWIDE=0 TOCENTRY="1"ID="FM30917" Elements of an Event RecordCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ElementCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"First LineCOLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"SeverityCOLNAME=2 ROTATE="0" MOREROWS="0"Event severity. For a description of the MHS Services severities, refer to IDREF="FM23454"Table 5-3.COLNAME=1 ROTATE="0" MOREROWS="0"SubsystemCOLNAME=2 ROTATE="0" MOREROWS="0"Subsystem reporting the event. For a description of the MHS Services subsystems, refer to IDREF="FM42917"Table 5-4.COLNAME=1 ROTATE="0" MOREROWS="0"Date & TimeCOLNAME=2 ROTATE="0" MOREROWS="0"Date and time, in the formatmm-dd-yy hh:mm:ss[am] | [pm]COLNAME=1 ROTATE="0" MOREROWS="0"Message IDCOLNAME=2 ROTATE="0" MOREROWS="0"The message ID of the message being processed, if applicable. The message ID uniquely identifies the message. You can use the message ID to trace the route of a message as it travels from subsystem to subsystem, and from messaging server to messaging server en route to its destination.COLNAME=1 ROTATE="0" MOREROWS="0"Reference IDCOLNAME=2 ROTATE="0" MOREROWS="0"An internal reference ID used by Novell Technical Support for troubleshooting.COLNAME=1 ROTATE="0" MOREROWS="0"Second LineCOLNAME=2 ROTATE="0" MOREROWS="0"Text of the event message. For a detailed explanation of the message text, refer to the 
BOOK="sysmsenu" COLLECTION="nw41"System Messages manual.PAGENUM=48 ID="BP47"IDREF="FM39523"Figure 5-4 illustrates a series of event records produced when MHS Services encountered a message that was missing required address information.PAGENUM=49 ID="BP48"LABEL="5-4" FLOAT="0"ID="FM39523"Sample Event RecordsFILEREF="fig_a.tif"The first entry in the example is produced by the submission subsystem, as it attempts to open the message file. The file is in valid MHS format, so the attempt is successful. The submission subsystem determines that required information is missing from the file. The second entry reports an error.MHS Services produces an undeliverable notice, and delivers it to the Postmaster. The last two entries report the success of this activity.Note that the message ID reported in the first two messages is blank. MHS Services does not assign a message ID until it determines that the message is valid.RENDERAS="SECT2"Resetting the Log FileIDXID="w4677"BOOK="_idx" COLLECTION="nw41" TIDREF="i3813"IDXID="w4678"BOOK="_idx" COLLECTION="nw41" TIDREF="i1360"
When the log file reaches the maximum size specified in the IDREF="FM62086"Log-File-Size parameter (see page 62)PAGENUM=50 ID="BP49", MHS Services begins writing messages to the beginning of the file. Consequently, the sequence of messages in the log file ceases to be chronological, and it might be difficult to find the current entries. You can reset the log file to ensure that the messages in the log file appear in chronological order.Before you reset the log file, make a copy of it in case you must research intermittent problems.To reset the log file, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Event Logs option from the MHSCON Available Options menu.The Event Log Options menu appears.PERFORMANCE="REQUIRED"Select the 
IDXID="w4679"BOOK="_idx" COLLECTION="nw41" TIDREF="i3811"CLASS=MENUITEM MOREINFO="NONE"Reset Event Log File option and select 
CLASS=MENUITEM MOREINFO="NONE"Yes to confirm.RENDERAS="SECT1"Monitoring and Administering Message FlowPart of maintaining a NetWare MHS messaging server involves managing the flow of messages. You can perform the following tasks to manage message flow:MARK=BULLETSuspend and resume message flow (that is, pickup of messages submitted by applications, gateways, and other messaging servers, and delivery to applications, gateways, and messaging servers)Display the status of a messaging serverReroute messages queued for a messaging serverReturn messages queued for a messaging serverTest a connection to a messaging serverSuspend and resume delivery to a specific messaging serverThe following sections describe how to perform these tasksRENDERAS="SECT2"ID="FM56099"Suspending and Resuming Message FlowIDXID="w4680"BOOK="_idx" COLLECTION="nw41" TIDREF="i4350"IDXID="w4681"BOOK="_idx" COLLECTION="nw41" TIDREF="i3835"IDXID="w4682"BOOK="_idx" COLLECTION="nw41" TIDREF="i2411"IDXID="w4683"BOOK="_idx" COLLECTION="nw41" TIDREF="i2411"IDXID="w4684"BOOK="_idx" COLLECTION="nw41" TIDREF="i4294"IDXID="w4685"BOOK="_idx" COLLECTION="nw41" TIDREF="i3826"
While you are troubleshooting message-delivery problems, you might want to:PAGENUM=51 ID="BP50"MARK=BULLETSuspend pickup of messages submitted by all applications, gateways, and other messaging servers.Suspend and delivery of messages to applications, gateways, and messaging servers. To do so, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Flow Control option from the MHSCON Available Options menu.The Message Flow Control form appears.PERFORMANCE="REQUIRED"To suspend the pickup of incoming messages, set the Inbound Message Flow field to Suspended.When you select the field, a popup list appears. Select an option from this list.To resume the pickup of incoming messages, set this field to Active.PERFORMANCE="REQUIRED"To suspend the delivery of outgoing messages, set the Outbound Message Flow field to Suspended.To resume the delivery of outgoing messages, set this field to Active.RENDERAS="SECT2"Monitoring Messaging Server StatusIDXID="w4686"BOOK="_idx" COLLECTION="nw41" TIDREF="i2429"IDXID="w4687"BOOK="_idx" COLLECTION="nw41" TIDREF="i4286"
When users report that they cannot send messages to or receive messages from another user, check the statuses of the messaging servers on which the sender's and recipient's mailboxes are located. To determine the location of a user mailbox with NWADMIN, display Details for the user, and click on the Mailbox button. To determine the location of a user mailbox with NETADMIN, choose the CLASS=MENUITEM MOREINFO="NONE"Mailbox Information option from the View or edit user menu.Follow this procedure to check a server's status.PERFORMANCE="REQUIRED"Select the IDXID="w4688"BOOK="_idx" COLLECTION="nw41" TIDREF="i2420"CLASS=MENUITEM MOREINFO="NONE"Messages option from the MHSCON Available Options menu.The server status window appears (see 
IDREF="FM35752"Figure 5-5). 
PAGENUM=52 ID="BP51"LABEL="5-5" FLOAT="0"ID="FM35752"Server Status WindowFILEREF="messages.tif"IDREF="FM74676"Table 5-6 describes the information in this window.LABEL="5-6" PGWIDE=1 TOCENTRY="1"ID="FM74676" Message-Management DataCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FieldCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Messaging ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Complete name of the MHS messaging server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4689"BOOK="_idx" COLLECTION="nw41" TIDREF="i2419"
MessagesCOLNAME=2 ROTATE="0" MOREROWS="0"Number of messages queued for delivery to the remote server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4690"BOOK="_idx" COLLECTION="nw41" TIDREF="i332"
AttemptsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of failed attempts to connect to the remote server since last successful connection.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4691"BOOK="_idx" COLLECTION="nw41" TIDREF="i2090"
Last ConnectCOLNAME=2 ROTATE="0" MOREROWS="0"The date and time your MHS messaging server last connected successfully to the remote server. If the last successful connection was some time ago, check the communication links between your server and the remote messaging server. COLNAME=1 ROTATE="0" MOREROWS="0"StatusCOLNAME=2 ROTATE="0" MOREROWS="0"The status of the remote server. Valid statuses include the following:IDXID="w4692"BOOK="_idx" COLLECTION="nw41" TIDREF="i4805"Waiting. Messages are queued for delivery to the remote server. They will be delivered when your MHS messaging server connects to the remote server.IDXID="w4693"BOOK="_idx" COLLECTION="nw41" TIDREF="i4349"Suspended. The local administrator has suspended delivery to the remote server. Messages will not be delivered to the server until the connection is resumed. (See IDREF="FM52415""Suspending or Resuming Delivery to a Messaging Server," on page 55 for instructions.)IDXID="w4694"BOOK="_idx" COLLECTION="nw41" TIDREF="i1758"Idle. No messages are queued for the remote MHS messaging server.IDXID="w4695"BOOK="_idx" COLLECTION="nw41" TIDREF="i85"Active. Your MHS messaging server is delivering a message to the remote server.PAGENUM=53 ID="BP52"PERFORMANCE="REQUIRED"To display a list of messages queued for a messaging server, select the server and then select the 
IDXID="w4696"BOOK="_idx" COLLECTION="nw41" TIDREF="i2129"CLASS=MENUITEM MOREINFO="NONE"List Messages option.The Messages window appears (see 
IDREF="FM96805"Figure 5-6).LABEL="5-6" FLOAT="0"ID="FM96805"Messages WindowFILEREF="listmes.tif"PAGENUM=54 ID="BP53"RENDERAS="SECT2"Rerouting MessagesIDXID="w4697"BOOK="_idx" COLLECTION="nw41" TIDREF="i3807"IDXID="w4698"BOOK="_idx" COLLECTION="nw41" TIDREF="i2418"
If you change the name of a messaging server, MHS Services automatically attempts to reroute messages queued for that server. You can manually force a rerouting attempt to hasten delivery. During rerouting, MHS Services checks the address information on the messages, and determines where to deliver them.To reroute messages, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Messages option from the MHSCON Available Options menu.PERFORMANCE="REQUIRED"Select the MHS messaging server whose messages you want to reroute.The Messaging Server Options menu appears.PERFORMANCE="REQUIRED"To reroute all messages queued for a server, select the 
IDXID="w4699"BOOK="_idx" COLLECTION="nw41" TIDREF="i3806"CLASS=MENUITEM MOREINFO="NONE"Reroute Messages option.PERFORMANCE="REQUIRED"To reroute selected messages, follow this procedure.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"List Messages option from the Messaging Server Options menu.PERFORMANCE="REQUIRED"Select the message(s) you want to reroute.The Message Options menu appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Reroute Message option.RENDERAS="SECT2"Returning MessagesIDXID="w4700"BOOK="_idx" COLLECTION="nw41" TIDREF="i3846"IDXID="w4701"BOOK="_idx" COLLECTION="nw41" TIDREF="i2418"
If an MHS messaging server will be unavailable for some time, you might want to return messages queued for that server. By returning a message, you notify the sender that it is undeliverable. You can return all messages queued for a server, or you can return individual messages. To return messages, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Messages option from the MHSCON Available Options menu.PAGENUM=55 ID="BP54"PERFORMANCE="REQUIRED"Select the MHS messaging server whose messages you want to return.The Messaging Server Options menu appears.PERFORMANCE="REQUIRED"To return all messages queued for a server, select the 
IDXID="w4702"BOOK="_idx" COLLECTION="nw41" TIDREF="i3845"CLASS=MENUITEM MOREINFO="NONE"Return Messages option.PERFORMANCE="REQUIRED"To return selected messages, follow this procedure.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"List Messages option from the Messaging Server Options menu.PERFORMANCE="REQUIRED"Select the message(s) you want to return.The Message Options menu appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Return Message option.RENDERAS="SECT2"Retrying a ConnectionIDXID="w4703"BOOK="_idx" COLLECTION="nw41" TIDREF="i3844"IDXID="w4704"BOOK="_idx" COLLECTION="nw41" TIDREF="i789"
Once you have corrected the cause of a connection failure, you can force a connection to the remote MHS messaging server. When you force a connection to a server, MHS Services attempts to deliver any messages queued for the server.To force a connection, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Messages option from the MHSCON Available Options menu.PERFORMANCE="REQUIRED"Select the MHS messaging server to which you want to force a connection.The Messaging Server Options menu appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Retry Connection option.MHSCON attempts to connect to the server and transfer any queued messages.RENDERAS="SECT2"ID="FM52415"Suspending or Resuming Delivery to a Messaging ServerIDXID="w4705"BOOK="_idx" COLLECTION="nw41" TIDREF="i4350"IDXID="w4706"BOOK="_idx" COLLECTION="nw41" TIDREF="i3835"IDXID="w4707"BOOK="_idx" COLLECTION="nw41" TIDREF="i789"IDXID="w4708"BOOK="_idx" COLLECTION="nw41" TIDREF="i789"PAGENUM=56 ID="BP55"If an MHS messaging server becomes unavailable for some time, you might want to suspend delivery to the server. (When you suspend delivery to a messaging server, your messaging server will not attempt to log in to the server, thus reducing NetWare server activity.) When the server becomes available again, you can resume delivery.You might also want to suspend delivery while you are troubleshooting delivery problems. For example, if a user on the server NEW_YORK.Acme is unable to send mail to a user on BOSTON.Acme, you canMARK=BULLETSuspend delivery from NEW_YORK.Acme to BOSTON.AcmeSuspend delivery on BOSTON.AcmeSend a message from NEW_YORK.Acme to BOSTON.Acme.After the message is queued, resume delivery from NEW_YORK.Acme to BOSTON.Acme, and check the event logs on both servers. If no errors are reported, resume delivery on BOSTON.Acme, and check its event log.To suspend delivery to all messaging servers, use the CLASS=MENUITEM MOREINFO="NONE"Flow Control option on the Main Menu. Refer to IDREF="FM56099""Suspending and Resuming Message Flow," on page 50.To find out whether delivery has been suspended, check the MHS messaging server status. To suspend or resume delivery, follow this procedure.PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Messages option from the MHSCON Available Options menu.PERFORMANCE="REQUIRED"Select the MHS messaging server for which you want to suspend or resume delivery.The Messaging Server Options menu appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Suspend/Resume Connection option and select 
CLASS=MENUITEM MOREINFO="NONE"Yes in response to the prompt for confirmation.
PAGENUM=57 ID="BP56"RENDERAS="SECT1"Checking the Postmaster's MailboxIDXID="w4709"BOOK="_idx" COLLECTION="nw41" TIDREF="i3348"IDXID="w4710"BOOK="_idx" COLLECTION="nw41" TIDREF="i623"
MHS Services sends an error notification to the Postmaster's mailbox when it encounters a message that is not in a valid MHS format. You should check the Postmaster's mailbox daily, to ensure that problems are resolved in a timely fashion.To check the Postmaster's mailbox, follow this procedure.PERFORMANCE="REQUIRED"From a workstation, log in to the network as the Postmaster.(To find out which users have been designated as Postmasters for the messaging server, check the Postmaster attribute for the messaging server object.)PERFORMANCE="REQUIRED"Start the user's messaging application.The FirstMail(tm) application is installed automatically when you install MHS Services. If you want to use FirstMail for DOS, start it with the following command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAILIf you want to use FirstMail for MS Windows, start it by choosing the Run command from the Program Manager File menu. Enter the following command:MOREINFO="NONE"WMAIL.EXEPERFORMANCE="REQUIRED"Read the messages in the Postmaster's mailbox.If the mailbox contains error notifications, refer to the 

BOOK="sysmsenu" COLLECTION="nw41"System Messages manual to find out what action to take.RENDERAS="SECT1"ID="FM74858"Configuring MHS ServicesIDXID="w4711"BOOK="_idx" COLLECTION="nw41" TIDREF="i764"IDXID="w4712"BOOK="_idx" COLLECTION="nw41" TIDREF="i2440"IDXID="w4713"BOOK="_idx" COLLECTION="nw41" TIDREF="i2429"IDXID="w4714"BOOK="_idx" COLLECTION="nw41" TIDREF="i905"
The default configuration options will be adequate for most installations. However, you can customize the configuration options to optimize messaging efficiency.PAGENUM=58 ID="BP57"Like any other NLM loaded on your NetWare server, MHS Services uses CPU, disk, and memory resources on the server. How MHS Services is configured determines how many of these resources it uses. When you configure MHS Services, you must balance messaging efficiency against efficiency of the other services provided by the NetWare server.This section explains when you need to change the MHS Services configuration. It also describes the structure of the configuration file and provides instructions for editing it.RENDERAS="SECT2"When to Customize an MHS Messaging ServerMHS Services is installed with default settings for the configuration options. Therefore, you need only change the default settings if:MARK=BULLETYou would like users to be notified with a network broadcast when messages are delivered to their mailboxes.Messages are not being delivered.You can reduce the maximum hop count to detect configuration errors that cause message looping.Messages are not being delivered quickly enough.NetWare 4 is a multithreaded operating system (that is, an NLM can start multiple processes, called threads). You can specify how many threads MHS Services can use for message pickup and delivery. By increasing the number of threads used by MHS Services, you can speed up the message pickup and delivery processes. By default, MHS Services uses one thread for pickup and one thread for delivery.The higher the number of threads, the greater the load on the NetWare server.You frequently add, delete, or change messaging users in the NetWare Directory database, and users complain that their application Address Books are not current.MHS Services provides an IDXID="w4715"BOOK="_idx" COLLECTION="nw41" TIDREF="i1418"extract file (that is, a file containing the list of messaging users defined in the NetWare Directory database). Some applications produce an Address BookPAGENUM=59 ID="BP58" (or pop-up directory list) from the extract file. By default, the extract file is updated every day. You can reduce the extract interval if you frequently add or remove messaging users. You can increase the interval if you seldom do so. The more frequently you update the extract file, the greater the load on the NetWare server.You need the MHSCON messaging server status and statistics screens to be current.You can specify how often the screen is to be refreshed, and how often statistics (such as totals, averages, and peak rates) are calculated. By default, the screen is refreshed every two seconds and statistics are calculated every minute.The more frequently the statistics are refreshed, the greater the load on the NetWare server.Your NetWare server is short on disk space.To reduce the amount of disk space used by MHS Services, you canMARK=BULLETDecrease the maximum log file size (by default, the log file can grow to 200 KB in size), or choose to log only error events (by default, both error and warning events are logged) Choose not to log statistics (by default, statistics logging is enabled), or reduce the size of the statistics log file (by default, the log can grow to 1 MB in size)Reduce the number of containers whose objects will be written to the extract fileNote: You can use the NWADMIN or FILER utilities to determine the amount of disk space available on your NetWare server. If you are using NWADMIN, display details for the volume object, and then select the Statistics button. If you are using FILER, select the CLASS=MENUITEM MOREINFO="NONE"Statistics option from the Volume menu.)The performance of other services on the NetWare 4.x server is suboptimal.PAGENUM=60 ID="BP59"To improve performance of other services on the NetWare server, decrease the number of threads used by MHS Services, disable automatic extract-file generation, or change the automatic extract-file generation time to a low-demand period. (If you disable automatic extract-file generation, you must generate the extract file manually after adding or removing messaging users. For instructions, refer to IDREF="FM80098""Updating the Extract File," on page 67.)RENDERAS="SECT2"Structure of the Configuration FileConfiguration information is stored in an ASCII text file called MHS.CFG, located in the SYS:\SYSTEM directory. This section describes the structure of the configuration file.The configuration file (IDXID="w4716"BOOK="_idx" COLLECTION="nw41" TIDREF="i2442"IDXID="w4717"BOOK="_idx" COLLECTION="nw41" TIDREF="i744"
MHS.CFG) contains all the MHS Services configuration parameters. IDREF="FM30200"Figure 5-7 shows the default configuration file.LABEL="5-7" FLOAT="0"ID="FM30200"MHS Configuration FileFILEREF="fig_b.tif"Each entry in the file is in the format parameter=value. Parameters are arranged in groups, or contexts. Each context is identified by the context name, enclosed in square brackets (for example [MHS] identifies the beginning of the MHS context).The following format rules apply to the configuration file:MARK=BULLETIf the value specified for a parameter is invalid, MHS Services uses the default value for the parameter.PAGENUM=61 ID="BP60"If a nonrepeatable parameter appears more than once within a context, MHS Services uses the first occurrence of the parameter, and ignores all subsequent occurrences. MHS Services ignores spaces around equal signs and before parameters.Comments must be preceded by a semicolon (;). A semicolon can be placed at the beginning of a line, or at the end of a line containing a parameter. If the comment extends to a second line, you must begin the second line with a semicolon.RENDERAS="SECT2"Editing the Configuration FileYou can view or edit the configuration file with a text editor, or with the MHSCON utility. This section provides instructions for editing the configuration file with the MHSCON utility. PERFORMANCE="REQUIRED"Select the IDXID="w4718"BOOK="_idx" COLLECTION="nw41" TIDREF="i749"CLASS=MENUITEM MOREINFO="NONE"Configuration option from the MHSCON Available Options menu.PERFORMANCE="REQUIRED"Edit the configuration parameters.For a list of the cursor and editing keys available in the Edit MHS Configuration Parameters screen, press 
MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> and select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save the changes.MHSCON returns you to the Main Menu. The changes take effect the next time you start MHS.NLM.Changes to the configuration file do not take effect until MHS Services is reloaded.PAGENUM=62 ID="BP61"RENDERAS="SECT2"Configuration ParametersIDREF="FM68673"Table 5-7 lists the MHS Services configuration parameters.LABEL="5-7" PGWIDE=1 TOCENTRY="1"ID="FM68673" MHS Services Configuration ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"SPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"MHS Services ParametersCOLNAME=1 ROTATE="0" MOREROWS="0"ID="FM76547"IDXID="w4719"BOOK="_idx" COLLECTION="nw41" TIDREF="i2229"
Log-Error-EventsCOLNAME=2 ROTATE="0" MOREROWS="0"Specify whether error events will be logged. Default: TRUEValid values: TRUE, FALSENote: You can also set this parameter using the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option of the MHSCON utility. (See IDREF="FM77848""Setting Event Log Filters," on page 44.) If the Log-Error-Events parameter is present in the configuration file, the value specified with the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option overrides it until the next time MHS Services is loaded. If the parameter is not present in MHS.CFG, the value specified with the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option is retained permanently.COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM62086"IDXID="w4720"BOOK="_idx" COLLECTION="nw41" TIDREF="i2230"
Log-File-SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Specify the maximum size of the log file. When the log file reaches this size, MHS Services begins writing entries at the beginning of the file. The end of the log is marked by the text MOREINFO="NONE"*** The End ***. Default: 200Range: 1-100000Unit of Measurement: KBCOLNAME=1 ROTATE="0" MOREROWS="0"ID="FM83669"IDXID="w4721"BOOK="_idx" COLLECTION="nw41" TIDREF="i2231"
Log-Info-EventsCOLNAME=2 ROTATE="0" MOREROWS="0"Specify whether informational events (such as successful message deliveries) should be logged. Default: FALSEValid values: TRUE, FALSENote: You can also set this parameter using the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option of the MHSCON utility. (See IDREF="FM77848""Setting Event Log Filters," on page 44.) If the Log-Info-Events parameter is present in the configuration file, the value specified with the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option overrides it until the next time MHS Services is loaded. If the parameter is not present in MHS.CFG, the value specified with the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option is retained permanently.COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM52192"IDXID="w4722"BOOK="_idx" COLLECTION="nw41" TIDREF="i2232"
Log-Warning-EventsCOLNAME=2 ROTATE="0" MOREROWS="0"Specify whether warning events will be logged. (A warning event is a recoverable error event.) Default: TRUEValid values: TRUE, FALSENote: You can also set this parameter using the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option of the MHSCON utility. (See IDREF="FM77848""Setting Event Log Filters," on page 44.) If the Log-Warning-Events parameter is present in the configuration file, the value specified with the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option overrides it until the next time MHS Services is loaded. If the parameter is not present in MHS.CFG, the value specified with the CLASS=MENUITEM MOREINFO="NONE"Event Log Filter option is retained permanently.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4723"BOOK="_idx" COLLECTION="nw41" TIDREF="i2358"
Maximum-Hop- CountCOLNAME=2 ROTATE="0" MOREROWS="0"Specify the maximum number of messaging servers through which a message can pass en route to its destination. If the message has not been delivered after being processed by the specified number of servers, it is declared undeliverable.Use this parameter to detect configuration errors that cause messages to loop between servers. Default: 15Range: 5-60COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM76522"IDXID="w4724"BOOK="_idx" COLLECTION="nw41" TIDREF="i2427"
Message-Rate- Calculation-IntervalCOLNAME=2 ROTATE="0" MOREROWS="0"Specify how often MHS Services should calculate totals, averages, and peak rates. By calculating the statistics more frequently, you improve the currency of statistical data but increase the load on the NetWare server. Default: 60 (1 minute)Range: 30-172800 (2 days)Unit of Measurement: SecondsCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4725"BOOK="_idx" COLLECTION="nw41" TIDREF="i2914"
New-Mail- Notification-EnabledCOLNAME=2 ROTATE="0" MOREROWS="0"Specify whether users should receive a NetWare broadcast message when messages arrive in their mailboxes. If this option is set to "TRUE," when MHS Services delivers a message to a user's mailbox, it sends a broadcast message to each workstation at which the user is currently logged on.Default: FALSEValid values: TRUE, FALSECOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4726"BOOK="_idx" COLLECTION="nw41" TIDREF="i2965"
Non-Delivery-IntervalCOLNAME=2 ROTATE="0" MOREROWS="0"Specify the maximum amount of time a message can spend in transit. If the time elapsed since the message was first submitted exceeds the value specified for this parameter, MHS Services declares the message undeliverable and notifies the sender. (If the originating application specified an expiration date on the message, the expiration date overrides the nondelivery interval.) Default: 172800 (2 days)Range: 0-2592000 (30 days)Unit of Measurement: SecondsCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4727"BOOK="_idx" COLLECTION="nw41" TIDREF="i3023"
Number-of-Inbound- ThreadsCOLNAME=2 ROTATE="0" MOREROWS="0"Specify how many threads MHS Services can use to pick up incoming messages. The greater the number of threads it uses, the more quickly messages will be picked up, but the greater the load on the server. Default: 1Range:1-10COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4728"BOOK="_idx" COLLECTION="nw41" TIDREF="i3024"
Number-of- Outbound-ThreadsCOLNAME=2 ROTATE="0" MOREROWS="0"Specify how many threads MHS Services can use to deliver outgoing messages. The greater the number of threads it uses, the more quickly messages will be delivered, but the greater the load on the server. Default: 1Range: 1-10COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM47494"IDXID="w4729"BOOK="_idx" COLLECTION="nw41" TIDREF="i3376"
Preferred-ApplicationCOLNAME=2 ROTATE="0" MOREROWS="0"(Required for compatibility with some applications. Refer to your application documentation to find out if you need to enter a Preferred- Application.) The preferred application is the application to which MHS Services will deliver a message, unless the originating application specifically requests delivery to another application. Use this parameter to specify a default preferred application that will be used for users who have not been assigned a preferred application. (To assign preferred applications to individual users, refer to IDREF="FM82881"Appendix A, "Assigning Applications to Users.")Default: MHSCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4730"BOOK="_idx" COLLECTION="nw41" TIDREF="i4024"
Sender-Validation- EnabledCOLNAME=2 ROTATE="0" MOREROWS="0"Specify whether messages submitted by local users (that is, messages picked up from the \SND directory) should be validated. If you enable sender validation, MHS Services ensures that the sender specified in the message is the owner of the message file. Default: FALSE (sender validation is disabled)Valid values: TRUE, FALSECOLNAME=1 ROTATE="0" MOREROWS="0"ID="FM12797"IDXID="w4731"BOOK="_idx" COLLECTION="nw41" TIDREF="i4279"
Statistics-Log- EnabledCOLNAME=2 ROTATE="0" MOREROWS="0"Specify whether statistics are to be written to a log file at regular intervals. Default: TRUEValid values: TRUE, FALSECOLNAME=1 ROTATE="0" MOREROWS="0"ID="FM31516"IDXID="w4732"BOOK="_idx" COLLECTION="nw41" TIDREF="i4280"
Statistics-Log-IntervalCOLNAME=2 ROTATE="0" MOREROWS="0"If the Statistics-Log-Enabled parameter is set to TRUE, specify how often statistics will be written to the statistics log file. After this interval has elapsed, MHS Services writes out statistics for individual messaging servers, as well as summary statistics for all messaging servers.Default: 3600 (1 hour)Range: 5-604800 (1 week)Unit of Measurement: SecondsCOLNAME=1 ROTATE="0" MOREROWS="0"ID="FM37444"IDXID="w4733"BOOK="_idx" COLLECTION="nw41" TIDREF="i4281"
Statistics-Log-SizeCOLNAME=2 ROTATE="0" MOREROWS="0"If the Statistics-Log-Enabled parameter is set to TRUE, specify the maximum size of the statistics log file. When the file reaches this size, it is renamed to MHS\SYS\STATSLOG.OLD. New entries are written to the beginning of the empty MHS\SYS\STATSLOG.DAT file.Default: 1000 (1 MB)Range: 100 -100000Unit of Measurement: KBSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"EXTRACT ParametersCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4734"BOOK="_idx" COLLECTION="nw41" TIDREF="i1421"
Extract-ContainerCOLNAME=2 ROTATE="0" MOREROWS="0"Specify the container(s) whose objects will be written to the extract file. Objects in containers within these containers will not be written to the extract file. The configuration file can contain multiple Extract-Container parameters. For example, to include all users in the containers OU=Marketing.O=Acme and OU=Sales.O=Acme in the extract file, enterMOREINFO="NONE"Extract-Container=OU=Marketing.O=Acme  Extract-Container=OU=Sales.O=AcmeNote: You can specify a combination of Extract-Containers and Extract- Subtrees.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4735"BOOK="_idx" COLLECTION="nw41" TIDREF="i1424"
Extract-SubtreeCOLNAME=2 ROTATE="0" MOREROWS="0"Specify the container(s) whose objects will be written to the extract file. Objects in all containers within these containers will be written to the extract file. The configuration file can contain multiple Extract-Subtree parameters. For example, to include all users in the Organization Acme and in all the OUs contained within the organization, enterMOREINFO="NONE"Extract-Subtree=O=AcmeDefault: [ROOT]Note: You can specify a combination of Extract-Containers and Extract- Subtrees.COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM63501"IDXID="w4736"BOOK="_idx" COLLECTION="nw41" TIDREF="i1422"
Extract-Generation- EnabledCOLNAME=2 ROTATE="0" MOREROWS="0"Specify whether you want the extract file to be generated automatically. (If you disable automatic extract-file generation, you can still generate the extract file from the MHSCON utility. See IDREF="FM80098""Updating the Extract File," on page 67.)Default: TRUEValid Values: TRUE, FALSECOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4737"BOOK="_idx" COLLECTION="nw41" TIDREF="i1423"
Extract-Initiation- TimeCOLNAME=2 ROTATE="0" MOREROWS="0"Specify the time of day (in 24-hour clock format) at which you want automatic extract-file generation to occur. Extract-file generation is a resource-intensive activity. Therefore, you should schedule it to occur during off-peak hours (late at night), when it will have minimal impact on other services provided by the NetWare server.Default: 00:00 (midnight)Range: 00:00-23:59COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM76496"IDXID="w4738"BOOK="_idx" COLLECTION="nw41" TIDREF="i2917"
Next-Extract- Generation-IntervalCOLNAME=2 ROTATE="0" MOREROWS="0"Specify how often MHS Services should update the extract file. When the time since the beginning of the last update equals the value specified here, MHS Services initiates the update process again. By updating the extract file more frequently, you improve the currency of application Address Books. However, you also increase the load on the NetWare server. Default: 86400 (1 day)Range: 36000 (10 hours)-604800 (1 week)Unit of Measurement: SecondsNote: You can force an update of the extract file with the CLASS=MENUITEM MOREINFO="NONE"Update Extract File option (see the following section, "IDREF="FM80098"Updating the Extract File").SPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"MHSCON ParametersCOLNAME=1 ROTATE="0" MOREROWS="0"ID="FM65317"Screen-Update- IntervalIDXID="w4739"BOOK="_idx" COLLECTION="nw41" TIDREF="i3965"COLNAME=2 ROTATE="0" MOREROWS="0"Specify how often MHS Services should refresh the MHSCON display. By refreshing the display more frequently, you improve the currency of statistical data but increase the load on the NetWare server. Default: 2Range:1-30.Unit of Measurement: SecondsPAGENUM=67 ID="BP62"RENDERAS="SECT1"ID="FM80098"Updating the Extract FileMHS Services provides an IDXID="w4740"BOOK="_idx" COLLECTION="nw41" TIDREF="i1418"extract file (that is, a file containing the list of messaging users defined in the NetWare Directory database). Some applications use the extract file to display an Address Book (or pop-up directory list), for users who are addressing messages. The extract file is automatically updated at the interval specified in the IDREF="FM76496"Next-Extract-Generation-Interval parameter (see page 67). You can also force an update of the extract file by selecting the CLASS=MENUITEM MOREINFO="NONE"Update Extract File option from the MHSCON Available Options menu.LABEL="A"PAGENUM=69 ID="BP63"ID="FM82881"Assigning Applications to UsersIf users on your server are using an application that is not NDS-aware, you must register the application with NetWare® MHS(tm) Services and add the application to the list of applications for each user who will be using it. Read this appendix to find out how. (Refer to your application documentation to determine whether your application is NDS-aware.)For each user, you can register two types of applications, a preferred application, and up to four other applications.The preferred application is the application to which MHS Services will deliver a message, unless the originating application specifically requests delivery to another application. Each user must have a preferred application. If you do not assign a preferred application explicitly (following the procedures in this appendix), MHS Services uses the default preferred application specified in the IDREF="FM47494"Preferred-Application parameter (see page 64).The other applications are applications to which MHS Services will deliver a message when explicitly requested by the originating application.RENDERAS="SECT1"Registering an ApplicationIDXID="w4741"BOOK="_idx" COLLECTION="nw41" TIDREF="i3725"IDXID="w4742"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
To register an application with MHS Services, follow this procedure.PERFORMANCE="REQUIRED"Enter the following command at the NetWare server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD MHSCONThe Available Options menu appears.PERFORMANCE="REQUIRED"Select
 the 
CLASS=MENUITEM MOREINFO="NONE"Applications option.
PAGENUM=70 ID="BP64"The Applications Options menu appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Application Registration option.The list of registered applications appears.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Ins> to register an application.PERFORMANCE="REQUIRED"In the Name field, type the name of the application.The name can be up to eight characters long, and must consist of valid DOS filename characters. Consult the application documentation for naming guidelines.PERFORMANCE="REQUIRED"(Optionally) in the Description field, type a description of the application.The description can be up to 24 characters long.PERFORMANCE="REQUIRED"In the Maximum User field, type the maximum number of users supported by the application.Refer to your application documentation to find out what value to enter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> and select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save the changes.RENDERAS="SECT1"Assigning an Application to a UserYou can assign an application to a user in the following ways:MARK=BULLETManually, using MHSCONUse this method ifMARK=BULLETYou are assigning a preferred application to a small number of users.You are assigning a preferred application to users who are not using your standard messaging application.You are assigning other applications.In batch mode, using the Extract facilityPAGENUM=71 ID="BP65"Use the batch method if you are assigning one messaging application as the preferred application for all users with mailboxes on your MHS messaging server. You would probably use this method after installing MHS Services and your messaging application for the first time.Note: If most local users use one application, but a small group uses another application, assign the first application in batch mode, and then change users of the other application manually.This section provides instructions for assigning applications using both of these methods.RENDERAS="SECT2"Assigning Applications ManuallyIDXID="w4743"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"IDXID="w4744"BOOK="_idx" COLLECTION="nw41" TIDREF="i4714"
To manually assign an application to a user, follow this procedure.PERFORMANCE="REQUIRED"Enter the following command at the NetWare server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD MHSCONPERFORMANCE="REQUIRED"The Available Options menu appears.PERFORMANCE="REQUIRED"Select
 the 
CLASS=MENUITEM MOREINFO="NONE"Applications option.The Applications Options menu appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"User Applications option.MHSCON displays the list of the users with mailboxes on the MHS messaging server.PERFORMANCE="REQUIRED"Select the user to whom you want to assign an application.The User Application Configuration form appears. PERFORMANCE="REQUIRED"Select the applications to be assigned to the user.Assign the user one preferred application and up to four other applications. To assign an application, select the desired field. MHSCON displays the list of registered applications. (This list excludes any applications that have already been assigned to the user.) Select an application from the list.
PAGENUM=72 ID="BP66"Note: To remove an application from the list of Other Applications, highlight the application and press 
MOREINFO="NONE"<Del>. You cannot delete the preferred application.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> and select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save the changes.RENDERAS="SECT2"Assigning Applications with the Extract FacilityThe Extract facility assigns an application as the preferred application for all users who do not currently have one.To assign a preferred application with the Extract facility, you must set the IDREF="FM47494"Preferred-Application parameter (see page 64) in the MHS Services configuration file (MHS.CFG) to the application you want to assign. If the IDREF="FM63501"Extract-Generation-Enabled parameter (see page 66) is set to "TRUE," the Extract facility will assign preferred applications the next time it runs. If the parameter is set to "FALSE," you must invoke the Extract facility manually. Select the CLASS=MENUITEM MOREINFO="NONE"Update Extract File option from the MHSCON Available Options menu.LABEL="B"PAGENUM=73 ID="BP67"ID="FM43407"Getting Started with FirstMailIDXID="w4745"BOOK="_idx" COLLECTION="nw41" TIDREF="i4026"IDXID="w4746"BOOK="_idx" COLLECTION="nw41" TIDREF="i1516"IDXID="w4747"BOOK="_idx" COLLECTION="nw41" TIDREF="i2308"IDXID="w4748"BOOK="_idx" COLLECTION="nw41" TIDREF="i1303"
FirstMail` is an electronic mail utility. When you install MHS Services, both FirstMail for DOS and FirstMail for MS Windows are automatically installed in the SYS:\PUBLIC directory on your NetWare Server. You do not need to configure FirstMail with user information because FirstMail gets its user information directly from NetWare Directory Services (NDS). This means that as soon as you install MHS Services, users can start using FirstMail.This appendix contains all the information users need to get started using FirstMail. The information is divided into the following sections:MARK=BULLETFirstMail for DOSFirstMail for MS WindowsRENDERAS="SECT1"ID="FM87350"FirstMail for DOSThis section describes how to start FirstMail for DOS and provides the information you need to get started using FirstMail, including how to:MARK=BULLETStart and quit FirstMailDisplay on-line help at any time Compose and send a messageRead messages you receiveSend a reply to, or forward a messagePrint a messagePAGENUM=74 ID="BP68"Organize and store your messagesRENDERAS="SECT1"What You Should Know Before Using FirstMail For DOSThe following paragraphs contain information that you should know before reading this appendix and using FirstMail: Documentation conventions - In this appendix, the names of one or more keys that you must press to perform the task described in the related text, are represented as <key_name> (that is, key names are enclosed in angle brackets). For example, MOREINFO="NONE"<F10> means you should press the F10 key, MOREINFO="NONE"<Delete> means you should press the Delete key, and MOREINFO="NONE"<Alt+A> means that you should hold down the Alt key and press the A key.Selecting a menu option - Either highlight the option (that is, move to the option you want by using the MOREINFO="NONE"<Up-arrow> or MOREINFO="NONE"<Down-arrow> key) and press MOREINFO="NONE"<Enter>, or press the letter that precedes the option. Getting Help - Press MOREINFO="NONE"<F1> at any time to get detailed information about the part of the program you are using. If a pop-up menu of relevant topics appears, just select the topic you want. Use the MOREINFO="NONE"<Up-arrow>, MOREINFO="NONE"<Down-arrow>, MOREINFO="NONE"<PgUp>, and MOREINFO="NONE"<PgDn> keys to scroll through the list. To exit from a Help screen, press MOREINFO="NONE"<Esc>.Selecting a message or an address from a list - Highlight an item using the MOREINFO="NONE"<Up-arrowMOREINFO="NONE"> or MOREINFO="NONE"<Down-arrowMOREINFO="NONE"> key and press MOREINFO="NONE"<Enter>. If small arrows appear near the top and bottom of the left border of the window, use the MOREINFO="NONE"<Up-arrow>, MOREINFO="NONE"<Down-arrow>, MOREINFO="NONE"<PgUp>, and MOREINFO="NONE"<PgDn> keys to scroll through the list. Selecting multiple items from a list - Highlight the first item and press either MOREINFO="NONE"<F5> or MOREINFO="NONE"<Space> (the space bar) to mark it (this places an asterisk (*) before the item); then do the same with the second item, and so on. You can mark all listed items at the same time by pressing MOREINFO="NONE"<Shift+F5>. After you mark the items, you can issue a command that affects all the marked items at the same time. Unselecting a marked item from a list - Marked items are preceded by an asterisk (*). To remove the asterisk from an item, highlight the item and press MOREINFO="NONE"<F5>. PAGENUM=75 ID="BP69"Sending a message - Press MOREINFO="NONE"<Ctrl+Enter> when you finish writing. Accepting and saving settings - By pressing MOREINFO="NONE"<Enter> in any pop-up window, you can accept the field you are in and move the cursor to the next field that contains settings you can change. To accept and save all settings (and return to the previous screen), press MOREINFO="NONE"<Ctrl+Enter>. RENDERAS="SECT1"Starting FirstMail for DOSBefore you run FirstMail, make sure that you have logged in to your NetWare file server and that your system administrator has loaded MHS Services. Type the following command at the DOS prompt and then press MOREINFO="NONE"<Enter>: FORMAT="LINESPECIFIC"MOREINFO="NONE"MAILWhen you run FirstMail, the Mail Options menu appears. The options that you are most likely to use at first are pointed out in IDREF="FM35342"Figure B-1.LABEL="B-1" FLOAT="0"ID="FM35342"Mail Options MenuFILEREF="options.tif"PAGENUM=76 ID="BP70"RENDERAS="SECT1"Quitting FirstMail for DOSYou can quit and return to the DOS prompt from anywhere in the program by pressing MOREINFO="NONE"<Alt+F10>. From the Mail Options menu, you can also quit by selecting the Q: Quit using FirstMail option, pressingMOREINFO="NONE" <Q>, or pressing MOREINFO="NONE"<Esc>.RENDERAS="SECT1"Using FirstMail for DOSThe following sections provide the basic information you need to start using FirstMail.RENDERAS="SECT2"Composing and Sending MessagesTo compose and send a message, either select the S: Send a mail message option from the Mail Options menu and press MOREINFO="NONE"<Enter>, or press MOREINFO="NONE"<S>. The Send Message: Editing Screen window appears (see IDREF="FM67202"Figure B-2).LABEL="B-2" FLOAT="0"ID="FM67202"Send Message: Editing ScreenFILEREF="send.tif"PAGENUM=77 ID="BP71"RENDERAS="SECT3"Addressing Your MessageIDXID="w4749"BOOK="_idx" COLLECTION="nw41" TIDREF="i109"
To address your message, press MOREINFO="NONE"<F2> when you are in the To header and select a recipient from the SMF Directory List (see IDREF="FM37966"Figure B-3). LABEL="B-3" FLOAT="0"ID="FM37966"SMF Directory ListFILEREF="address.tif"When you select one or more recipients from the SMF Directory List, FirstMail enters each recipient's electronic mail address in the To header.You can also type addresses in the To header. Refer to the Help screen for the To header for information about address format. PAGENUM=78 ID="BP72"RENDERAS="SECT3"Composing Your MessageType the text into the Send Message: Editing Screen. FirstMail formats your message automatically.RENDERAS="SECT3"Specifying Who Should Receive a CopyBefore you send your message, you can specify whether you want to receive a copy of it. You can also specify one or more recipients who should receive a Carbon copy (Cc) of your message.Press MOREINFO="NONE"<F9> in the Send Message: Editing Screen to display a list of additional headers and options (see IDREF="FM26930"Figure B-4). When you finish, press MOREINFO="NONE"<Ctrl+Enter> to return to the Send Message: Editing Screen.LABEL="B-4" FLOAT="0"ID="FM26930"Options For Your MessageFILEREF="cc_bcc.tif"RENDERAS="SECT3"Sending Your MessageTo send your message, press MOREINFO="NONE"<Ctrl+Enter> from the Send Message: Editing Screen. FirstMail sends the message and returns you to the Mail Options menu. PAGENUM=79 ID="BP73"RENDERAS="SECT2"Reading, Replying to, Forwarding, and Printing MessagesSelect either of the following options from the Mail Options menu to display your mail. To read your new messages, select the N: check for New mail option. (This option appears only when you have new mail.) To read messages that you read and saved, select the B: Browse mail messages option. A window similar to IDREF="FM52763"Figure B-5 appears.LABEL="B-5" FLOAT="0"ID="FM52763"Folder WindowFILEREF="browse.tif"PAGENUM=80 ID="BP74"The top of the window displays the name of the current folder. A folder is a mail file where you can organize and store your messages. FirstMail provides the Main folder and automatically puts messages there after you read them.When you select the B:Browse mail messages option, FirstMail always opens the folder that you were in last. If you want to change to another folder, press MOREINFO="NONE"<F10> to display a list of your folders. Select a folder and FirstMail displays a list of the messages in it.RENDERAS="SECT3"Reading MessagesTo read a message, select the message from the list in the New Mail or Browse Mail window. The message appears in a window like the one illustrated in IDREF="FM18750"Figure B-6. LABEL="B-6" FLOAT="0"ID="FM18750"Message WindowFILEREF="read.tif"PAGENUM=81 ID="BP75"RENDERAS="SECT3"Replying to MessagesTo reply to a message, select the message from the New mail or Browse mail window and press MOREINFO="NONE"<R>. The Select reply format window appears (see IDREF="FM41596"Figure B-7).LABEL="B-7" FLOAT="0"ID="FM41596"Select Reply Format WindowFILEREF="reply.tif"When you finish setting your reply options, press MOREINFO="NONE"<MOREINFO="NONE"Ctrl+EnterMOREINFO="NONE"> to display the editing window where you can type your reply.When you finish typing your reply, press MOREINFO="NONE"<Ctrl+Enter> to send it and return to the New mail or Browse mail window.RENDERAS="SECT3"Forwarding MessagesTo forward a message to someone else, select the message from the New mail or Browse mail window and press MOREINFO="NONE"<F>. The Forward message or file to window appears (see IDREF="FM30211"Figure B-8). PAGENUM=82 ID="BP76"LABEL="B-8" FLOAT="0"ID="FM30211"Forward Message or File WindowFILEREF="forward.tif"When you finish, press MOREINFO="NONE"<Ctrl+Enter>. If you set the Edit before sending? field to MOREINFO="NONE"N, FirstMail forwards the message and returns you to the New mail or Browse mail window. If you set it to MOREINFO="NONE"Y, the message is displayed and you can edit it, type additional text, or both. When you are ready to forward the message, press MOREINFO="NONE"<Ctrl+Enter>. FirstMail forwards the message and returns you to the New mail or Browse mail window.RENDERAS="SECT3"Printing MessagesIDXID="w4750"BOOK="_idx" COLLECTION="nw41" TIDREF="i3545"
To print a message to a printer, a print queue, or a file, select the message from the New mail or Browse mail window and press MOREINFO="NONE"<P>. The Print settings window appears (see IDREF="FM33853"Figure B-9). PAGENUM=83 ID="BP77"LABEL="B-9" FLOAT="0"ID="FM33853"Print Setting WindowFILEREF="print.tif"At first, you are likely to use only the Print to and PostScript? fields. If you need help about your printer, ask your system administrator. After you set your printing options for the first time, you can turn off this window so that it does not appear each time you enter the Print command. To do this, select the P: Preferences option on the Mail Options menu. From the Preferences menu, select the General Settings option and set the Suppress print dialog? field to MOREINFO="NONE"Y.Later, you can change your print setting by pressing MOREINFO="NONE"<Shift+F10> to display the Preferences menu and select the Print settings option. RENDERAS="SECT2"Organizing and Storing Your Messages in a FolderFirstMail provides the MainPAGENUM=84 ID="BP78" folder and automatically puts messages there after you read them. If you specify that you want to save a copy of the message you send, FirstMail automatically saves a copy of each message you write in the Copies to self folder. You can also create new folders and either move a message from the current folder into another folder or place a copy of a message into one or more folders. To change folders or add a new one, press MOREINFO="NONE"<F10> while you are in either the New mail or Browse mail window. The Select a folder window appears (see IDREF="FM24324"Figure B-10).LABEL="B-10" FLOAT="0"ID="FM24324"Select a Folder WindowFILEREF="select.tif"When you press MOREINFO="NONE"<Insert> to create a folder, you are prompted for a long name and a short name for your new folder. The long name is the descriptive name displayed in the Select a folder window and at the top of the New mail and Browse mailPAGENUM=85 ID="BP79" window. The short name is the 8-character name of the file where the messages are saved. It is the name that is displayed on the Mail Options menu. If you do not provide a short name, FirstMail provides one for you. After you create one or more folders, you can either move or copy a message to another folder (see IDREF="FM80816"Figure B-11). LABEL="B-11" FLOAT="0"ID="FM80816"Moving or Copying MessagesFILEREF="browse_b.tif"RENDERAS="SECT1"ID="FM32549"FirstMail for MS WindowsThis section describes how to start and learn to use FirstMail for MS Windows.PAGENUM=86 ID="BP80"RENDERAS="SECT2"Starting FirstMail from MS WindowsBefore you can use FirstMail for MS Windows, you need to perform the following tasks through the MS Windows Program Manager:MARK=BULLETCreate a program group for FirstMail Create a program item for WMAIL.EXE For instructions on how to complete these tasks, refer to your MS Windows documentation.When you finish these tasks, you can start FirstMail by clicking the FirstMail icon.RENDERAS="SECT2"Learning How to Use FirstMail for MS Windows and Getting HelpWhen you start FirstMail by clicking the FirstMail icon, the FirstMail window appears. All the information you need to learn how to use FirstMail is available through the online Help feature. The Help topics include information about how to do the following:MARK=BULLETCompose and send messagesRead and process messagesWork with foldersWork with distribution listsWork with address booksCustomize the way FirstMail operatesIn addition, the Help feature lists and describes all the menu options available on the menu bar and the button panel.You can display the online Help window either by selecting the CLASS=MENUITEM MOREINFO="NONE"Help option on the menu bar or by pressing MOREINFO="NONE"<F1MOREINFO="NONE">.