Network Support Encyclopedia 96-1

home *** CD-ROM | disk | FTP | other *** search

/ Network Support Encyclopedia 96-1 / novell-nsepro-1996-1-cd2.iso / download / netware / ngm170.exe / NGM170.TXT < prev next >

Wrap

Text File | 1993-10-28 | 79KB | 1,670 lines

NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Upgrade for Global MHS 2.0 to 2.0b DOCUMENT ID: 200018.TID DOCUMENT REVISION: A DATE: 26OCT93 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: NGM170.EXE NOVELL PRODUCT and VERSION: NetWare Global MHS 2.0 ABSTRACT: This file updates current Global MHS v2.0 users to v2.0 RevB. This update includes numerous enhancements and fixes. Before you install this patch be sure you are using a compatible version of the CLIB.NLM (CLIB.NLM 311 Rev E or later). _________________________________________________________________ DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. _________________________________________________________________ Other: **************************************************************** DOCUMENTATION UPDATES **************************************************************** The information in this section clarifies information in the manuals and provides information that was too late to be included in the product manuals. ------------------------------------------------------------- Directory Synchronization ------------------------------------------------------------- 1) Enable Directory Synchronization on the Domain Hub First: If your messaging network has multiple Global MHS servers and you intend to enable directory synchronization (participation), enable directory synchronization at the directory synchronization domain hub first. Then, enable directory synchronization at the Global MHS domain members one at a time. NOTE 1: Wait until one domain member completes the process of becoming a participating member before enabling directory synchronization on the next domain member. Continue until all domain members are participating. NOTE 2: Do not enable directory synchronization for multiple domain members at the same time. For information on directory synchronization, see page 2-3 and Chapter 7 in the NGM Administration manual. 2) Full Reconciliation Directory Synchronization Schedule Enhancement: When an administrator makes a change to the database on one Global MHS server, Global MHS sends directory synchronization update messages to other participating servers. Update messages are sent at the time the change is made. Each participating Global MHS server sends reconciliation messages to the databases of all other participating servers. Reconciliation messages are summary messages. If a participating server needs more information about something in the reconciliation message (for example, because it didn't receive an update message because of a connection problem), that server requests more information. The schedule at which a particular server will send reconcilation messages is configured on a server-by-server basis. A server administrator can also "force" a reconciliation message to be sent. NOTE: Full reconciliation does not need to occur frequently because all changes are updated in all databases anyway. The directory synchronization schedule in Global MHS 2.0 has been enhanced to allow for a synchronization interval of more than a week. The maximum interval was previously one week in NGM 1.x. The Global MHS 2.0 directory synchronization schedule in NGMADMIN has a new field labeled 'Interval(weeks)', which can be set to a value between 1 and 52. The value in this field determines the number of weeks Global MHS will wait between directory synchronization events. Two new fields at the bottom of the synchronization schedule indicate the time and date of the last and next directory synchronization events. Unlike the NGM 1.x directory synchronization schedule, the Global MHS 2.0 directory synchronization schedule does not allow more than one weekday to be chosen at a time. Thus, in Global MHS 2.0, it is not possible to schedule synchronization more frequently than once a week. If you are upgrading from NGM 1.x, the default value for the interval field is 1 (week). If you doing a first-time installation of Global MHS 2.0, the default value for the interval field is 4 (weeks). See also, "Troubleshooting Directory Synchronization Problems," later in this file. ------------------------------------------------------------- Parameters For Regulating Message Flow ------------------------------------------------------------- Global MHS continually monitors the system for the following. a) Low Global MHS memory b) Low Netware system free cache memory c) Low free disk space Global MHS monitors each of the factors in the previous list according to values set in the NGM.CFG file for the following message flow thresholds: Stop-inbound threshold Stop-inbound-and-outbound threshold Resume-message-processing threshold For most systems, the default values for these threshold values are adequate. Parameters in the NGM.CFG file (described later in this section) control message flow thresholds. You can change the default values for these parameters. For example, if a server handles a lot of traffic and the server has more memory or a larger disk than the minimum required for Global MHS, increasing the thresholds will make the system more reliable. NOTE: Do not change the values to be less than the default values. This section describes the message flow thresholds and identifies the parameters used to set them for each of the system resources. When Global MHS detects that a particular resource threshold has been reached and shuts off that resource, Global MHS displays flow control status messages on the NetWare console and logs these messages in the log file SYS_LOG. Stop-inbound threshold: If this threshold is reached, Global MHS continues to process outbound messages but stops processing inbound messages. NOTE: The stop-inbound threshold must be higher than the stop-inbound-and-outbound threshold. Stop-inbound-and-outbound threshold: If this threshold is reached, Global MHS stops processing both outbound and inbound messages, effectively stopping message flow. Operator intervention is required at this point to take care of the problem, which may require adding more memory or deleting unneeded files from the hard disk. NOTE: The stop-inbound threshold must be higher than the stop-inbound-and-outbound threshold. Resume-message-processing threshold: This threshold is applicable only when Global MHS has reached one or both of the other two thresholds. When the resume-message-processing threshold is reached, Global MHS automatically restarts processing of inbound and outbound messages. In other words, Global MHS begins processing messages normally again. NOTE: The resume-message-processing threshold must be greater than the other two thresholds. Configuring Threshold Values: This section identifies the keywords (parameters) thatyou can use in the [NGM] section of the NGM.CFG to configure the message flow thresholds for Global MHS memory, NetWare system free cache memory, and free disk space. A) Setting thresholds for free Global MHS memory The amount you would increase these values is a factor of how much more Global MHS memory on your server than the minimum requirements specified in the Global MHS Installation documentation. For example, if the amount of Global MHS memory on your server is double the amount specified in the Global MHS documentation, you can double these values. THRESHOLD KEYWORD stop-inbound FREE-MEMORY-RESTRICT-BOUND= (Specify value in KB; default=100 KB). NOTE: If you increase this value, Global MHS stops processing inbound messages sooner (it gives more buffer). stop-inbound-and-outbound FREE-MEMORY-SHUTDOWN-BOUND= (Specify value in KB; default=50 KB). NOTE: If you increase this value to 100, Global MHS shuts down sooner. resume-message-processing FREE-MEMORY-RESUME-BOUND= (Specify value in KB; default is 200 KB). B) Setting thresholds for free NetWare system cache memory The amount you would increase these values is a factor of how much more memory on your server than the minimum requirements specified in the Global MHS Installation documentation. For example, if the amount of memory on your server is double the amount specified in the Global MHS documentation, you can double these values. THRESHOLD KEYWORD stop-inbound FREE-CACHE-RESTRICT-BOUND= (Specify value in KB; default is 250 KB) stop-inbound-and-outbound FREE-CACHE-SHUTDOWN-BOUND= (Specify value in KB; default is 200 KB) resume-message-processing FREE-CACHE-RESUME-BOUND= (Specify value in KB; default is 300 KB) C) Setting thresholds for free NetWare disk space The amount you would increase these values is a factor of how much more disk space your server has than the minimum amount specified in the Global MHS Installation documentation. For example, if the disk size of your server is 10 times the minimum disk size specified in the Global MHS documentation, you can increase these values by a factor of 10. THRESHOLD KEYWORD stop-inbound FREE-DISK-SPACE-RESTRICT-BOUND (Specify value in KB; default is 4096 KB) stop-inbound-and-outbound FREE-DISK-SPACE-SHUTDOWN-BOUND (Specify value in KB; default is 2048 KB) resume-message-processing FREE-DISK-SPACE-RESUME-BOUND= (Specify value in KB; default is 6144 KB) ------------------------------------------------------------- Passive Servers ------------------------------------------------------------- 1) Global MHS Can Be Installed on Passive Servers: This release of Global MHS supports installation of passive servers. To install Global MHS on a passive server, select the Passive Messaging Servers item in the This Server menu item. Press the INS (Insert) key to add a passive server. 2) Registering Passive Servers: When registering a passive server, be sure to specify, in the NetWare File Server field, the NetWare server on which the passive server will be installed. Also, ensure the NetWare server can login to the passive servers. Leaving the NetWare File Server field blank will cause the routing Global MHS server to exhaust all available NetWare server connections and message transfer to other servers via NIMP will cease. For more information, see page 8-17 in the NGM Administration manual. 3) When a passive server is registered in the NGMADMIN This Server option, Global MHS now automatically creates the appropriate message directories and necessary software (NETDIR.TAB file and MHS.LCK) on the passive server. Each Global MHS server can provide message delivery for up to eight passive servers. For information on registering a passive server, see the NGM Administration Manual. 4) Deleting Passive Servers: Before deleting a passive server which is slaved to the local Global MHS server, set the Flow Control values to NO in the NGMSMF Inbound Allowed and Outbound Allowed fields. 5) Passive Server Limitation: Although Global MHS limits the number of passive servers to eight in the current release, more than 8 passive servers may appear on the NGMADMIN Passive Messaging Servers screen. This situation can arise from use of the Global MHS upgrade utility (NGMUPGDE.NLM), which may create more than eight passive servers from a previous MHS installation. Although more than eight servers appear in the NGMADMIN screen, Global MHS still limits the total number of 'live' passive servers to 8. Global MHS delivers messages only to live passive servers. There is no indication which of the listed passive servers are 'live.' ------------------------------------------------------------- NGMADMIN Utility ------------------------------------------------------------- 1) When you change values in screen fields, those values are not saved until you press the "Esc" key to exit the form and confirm that you want to save the changes. 2) The Successful Connections field in the Statistics option displays the number of times that the \MHS\MAIL\SND directory has been accessed on the local server to pick up messages. For more information, see page 9-31 in the NGM Administration manual. 3) Resume/Suspend and Force Connection picklists now list all directly connected servers instead of only the polled asynchronous servers. 4) Picklists for workgroup subscription, domain hub, and Global MHS servers differ slightly from the documentation. NGMADMIN was enhanced to provide more picklists. Picklists were added to the workgroup subscription option and under the Force Directory Synchronization option. 5) Minor changes have been made in the presentation of data under the various sub-options of the Maintenance menu. Instead of SMF short names, NGM server names are now shown in the Statistics option. 6) Statistics can be reset on a per server basis. However, there is no option to reset statistics for all servers. 7) Log files are now sorted alphabetically. Old log files with no logging information (i.e., log files that only contain a title) are automatically deleted. 8) The Accounting file is now stored in directory \NGM\, instead of directory \NGM\LOGS\. Therefore, this file is no longer visible from the Log Files option in NGMADMIN. ------------------------------------------------------------- Additional Address Formats Supported ------------------------------------------------------------- Assign a unique priority to every address format configured in the Additional Address Formats Supported option. If two address formats have the same priority, incorrect routing may occur. For more information, see pages 8-13 and 8-14 in the NGM Administration manual. ------------------------------------------------------------- Users, Workgroups, and Distribution Lists ------------------------------------------------------------- 1) Deleting Users: When the administrator deletes a user using NGMADMIN, Global MHS deletes the user from the Global MHS database. However, Global MHS does not delete the MHS directory structure for that user. This feature enables an administrator to recover from inadvertently deleting users. It also facilitates moving a user mailbox from one server to another. To move a user mailbox, delete the user from the server, add the user to another server, then copy the mailbox files for the user to the other server. To completely delete a user, manually delete the MHS directory structure for that user as well as deleting the user through NGMADMIN. Before adding a new user with the same name as a deleted user, be sure to delete the MHS directory structure for that user name. Otherwise, the new user will inherit the old directory structure and messages. 2) User and DList Name Restrictions: An NGM user name, which consists of both a user name and a workgroup name, can be up to 253 characters. However, in the current release of Global MHS, the user name or DList name portion (the part that precedes the @ sign) must not exceed 64 characters. 3) When you configure workgroups or servers, be sure to fill in the Error Mailbox field. ------------------------------------------------------------- New Mail Notification ------------------------------------------------------------- New Mail Notification is a feature that displays a broadcast message when new messages arrive for a user. To receive the broadcast message, the user must be currently logged in and be actively able to receive messages via local or passive host delivery. By default, New Mail Notification is FALSE (disabled). To enable this feature, add the following line to section [NGMSMF] of the NGM configuration file SYS:\SYSTEM\NGM.CFG. NEW-MAIL-NOTIFICATION-ENABLED=TRUE NOTE: New Mail Notification only works on a per server basis. To disable New Mail Notification, add the following line to section [NGMSMF] of the NGM configuration file SYS:\SYSTEM\NGM.CFG on each server. NEW-MAIL-NOTIFICATION-ENABLED=FALSE You can also disable this feature on a per user basis by creating a file in the MHS user directory named QUIETMSG. For example, to disable this feature for user Joe, create and add the following file to Joe's MHS directory: \MHS\MAIL\USERS\JOE\QUIETMSG The file can be any length, including an empty file with zero bytes. ------------------------------------------------------------- Sender Validation ------------------------------------------------------------- Sender validation is a new feature that verifies the authenticity of the sender of a message. Sender validation ensures the sender of a message is logged in as that user. For example, a user will not be able to log in as one user and submit a message as another user. Global MHS matches the DOS or NetWare owner of a submitted message with the name in the "From:" header. By default, sender validation is TRUE (enabled). To disable this feature, change the sender validation line in section [NGMSMF] of configuration file SYS:\SYSTEM\NGM.CFG to read as follows: SENDER-VALIDATION-ENABLED=FALSE To enable sender validation, use: SENDER-VALIDATION-ENABLED=TRUE NOTE: Sender validation only works on a per server basis. This parameter only affects the local server. If a message is submitted by an imposter, Global MHS labels the message BAD (renames the message with a .BAD extension) and sends notification of the bad message to the administrator. Global MHS also logs a warning in the NGMSMF log file. Sender validation only verifies the authenticity of messages submitted to the \MHS\MAIL\SND directory on the local Global MHS server or a passive Global MHS server. These messages are either submitted by SMF applications, logged-in users invoking SMFSEND, or NGMADMIN, or are manually submitted by users who create and submit minimal submission messages. ------------------------------------------------------------- Document Translation ------------------------------------------------------------- 1) By default, Global MHS invokes an NLM named DOCXLT.NLM to perform document translation services (document translation is an optional service provided by third-party vendors). To change the default NLM name, change the following configuration parameter in section [NGMSMF] of the configuration file SYS:\SYSTEM\NGM.CFG. DOCUMENT-TRANSLATION-NLM-NAME=<file-name> For example, to set the NLM to DOC.NLM, use the following: DOCUMENT-TRANSLATION-NLM-NAME=DOC.NLM The default <file-name> is DOCXLT.NLM 2) By default, Global MHS waits up to 10 minutes for document translation of an attachment to complete. To change the default NLM time interval, change the following configuration parameter in section [NGMSMF] of the NGM configuration file SYS:\SYSTEM\NGM.CFG. DOCUMENT-TRANSLATION-RETRY-NUMBER=<minutes> For example, to set the time limit to 20 minutes, use the following: DOCUMENT-TRANSLATION-RETRY-NUMBER=20 (default=10) ------------------------------------------------------------- Changing the Length of Time Global MHS Checks for Messages ------------------------------------------------------------- Global MHS checks for messages in several directories periodically (for example, \SND, \QUEUES directories). By default, Global MHS spends a maximum of 5 minutes processing messages in a directory before switching to the next directory. This function means that each directory will get a turn. You can change the time that Global MHS spends in a directory. To change the time Global MHS spends in a directory, use the following configuration parameter in section [NGMSMF] of configuration file SYS:\SYSTEM\NGM.CFG. DIRECTORY-TIME-LIMIT=<seconds> For example, to set the time limit to 600 seconds (10 minutes), use the following: DIRECTORY-TIME-LIMIT=600 The default is 300 seconds (5 minutes). If you make the time interval too high, you will starving other directories of processing time. If you make the time interval too low, Global MHS will not complete processing of many messages before switching to the next directory. ------------------------------------------------------------ Applications ------------------------------------------------------------ 1) A default application called MHS is installed as an SMF v71 application. If your mail application is an SMF v70 application and it picks up messages from the MHS mailbox directory, you need to change MHS to an SMF v70 application. To change MHS to an SMF v70 application, choose NGMADMIN menu items This server, SMF Applications, MHS, and change the SMF Version to v70. 2) Use the Import Users from Bindery option provided with the NGMADMIN utility to import information from the Bindery, rather than using the utilities that may be provided with messaging applications. Use of the Global MHS Administration Utility will ensure that the security rights are set correctly for all users. For more information, see page 4-5 in the NGM Administration manual. 3) Compatible versions of BeyondMail: Global MHS distribution lists and delivery outside of a single server do not work with BeyondMail releases prior to BeyondMail version 1.10c. If you are a BeyondMail user, call Beyond Incorporated or your distributor to receive an update. 4) Compatible versions of Da Vinci Email Versions of Da Vinci for DOS Email prior to Da Vinci version 2.00K may not read mail attachments correctly. If you are a Da Vinci for DOS Email user, call Da Vinci Systems Corporation or your distributor to receive an update. 5) Global MHS does not support NetWare SMF v64 applications or gateways. ------------------------------------------------------------ Asynchronous Communications (NGMAMP) ------------------------------------------------------------ This section contains information about asynchronous communications. It includes a list of modems that Global MHS supports. ------------------------------------------------------------ Usage Guidelines (NGMAMP) ------------------------------------------------------------ 1) Before configuring asynchronous (modem) links, be sure to plan how to best connect your NGM servers with asynchronous links. Server-to-server logins over asynchronous links utilize NGM server short names, which must be unique for all servers in an NGM network. Since you will not be able to change the NGM server short name after installation, you must assign your names in advance. 2) When manually registering an MHS 1.5 or MHS 1.5C host as a contact server in a new foreign domain, be sure to select the Server Configuration menu and change the default SMF version to v70; otherwise, NGM-initiated delivery to the MHS host will fail. If message delivery fails, the log file for the asynchronous port (that connects to the MHS host) will contain the following warning: Warning #325, Negotiation failed. ... too many retries 3) Global MHS ships with AIO drivers for the following serial interfaces, which are used for modem connections: COM port Digiboard International serial I/O adapters Hayes ESP serial I/O adapter Newport Systems serial I/O adapters GateWay WNIM+ serial I/O adapter COMPUTON IntelliPort II serial I/O adapter This list is growing in number as more vendors submit their AIO drivers for Novell certification. For more information, refer to the AIODISK.DOC file on the NetWare AIO Drivers diskette or contact Novell Technical Support. NOTE: See section on AIO compatibility later in this readme ---- 4) Global MHS ships with support for the following modems. The corresponding modem definition file is enclosed in parentheses. Codex Motorola 3260 (codx3260.mdf) Codex Motorola 3220 (codx3220.mdf) Everex Evercom 24 (ever24.mdf) Everex Evercom 24E (ever24e.mdf) Generic Fax Modem (faxmdm.mdf) Global Village Communications 9600 (gvc96.mdf) Hayes compatible modems (hayes.mdf) Hayes Smartmodem 1200 (hayes12.mdf) Hayes Smartmodem 2400 (hayes24.mdf) Hayes Smartmodem Optima 24 (optima24.mdf) Hayes Smartmodem Optima 96 (optima96.mdf) Hayes V-Series Smartmodem (hayes96v.mdf) Hayes V-series Smartmodem 2400 (hayes24v.mdf) Hayes V-series ULTRA Smartmodem 9600 (ultra96.mdf) Intel 2400EX (intel24.mdf) Intel 9600EX (intel96e.mdf) Intel SatisFAXtion (intelfax.mdf) Megahertz 2400 Pocket Fax/Modem (mhz24.mdf) Megahertz 2400e Pocket Fax/Modem (mhz24e.mdf) Microcom QX/4232hs and QX/4232bis (mcom4232.mdf) Microcom AX/2400c (mcom24c.mdf) Multi-Tech MultiModem 932ba (mtech96.mdf) Multi-Tech MultiModem 224ba (mtech24.mdf) NEC N9631 (nec9631.mdf) Null modem (nullmdm.mdf) Practical Peripherals 9600SA (prac96sa.mdf) Practical Peripherals 2400SA (prac24sa.mdf) Supra FaxModem V.32bis (supra.mdf) Telebit T1600 (t1600.mdf) Telebit T1000 (t1000.mdf) US Robotics Courier 2400 (usr24.mdf) US Robotics Courier 2400e (usr24e.mdf) US Robotics Courier HST, Dual, and V.32bis (usrhst.mdf) UDS 3225 (uds322x.mdf) Zoom v.32 (zoom96.mdf) Zoom v.32 Turbo (zoom96t.mdf) Use the special modem definition file, nullmdm.mdf, to configure non-modem connections, i.e., servers connected with a "null modem" serial cable. Each modem type in an NGMADMIN picklist corresponds to a modem definition file in directory <NGM-root-dir>\ASYNC\MODEMDEF. As Novell continues to expand the list of supported modems, newly certified modem definition files will be made available from the locations mentioned at the end of this document. To update your server with new or enhanced modem definition files, copy them to this directory. 5) Global MHS ships with support for the CompuServe Public Hub. The hub script file is CSERVE.HST and it can be found in the directory <NGM-root-dir>\ASYNC\SCRIPTS. This is also the only script available on a NGMADMIN picklist for Hub Login Script. Compuserve hub script (cserve.hst) Note that Novell (NHUB) and Pacific Bell are two other "public hubs," but these hubs do not require hub login. Therefore, no hub script file is provided or required. 6) Global MHS ships with support for the following Public Data Networks (PDN)for gaining access to the CompuServe Public Hub. The corresponding network script file is enclosed in parentheses. Compuserve direct connection (cserve.net) DataPac (datapac.net) Datex-P (datex-p.net) Dialplus (dialplus.net) FALNET (falnet.net) FENICS (compupas.net) Infonet (infonet.net) LATA access for CT (latact.net) LATA access for DE, NJ, and 3 cities in PA (latadenj.net) Telenet (telenet.net) TELEPAC (telepac.net) TTNNET (ttnnet.net) Tymnet (tymnet.net) Each script in an NGMADMIN picklist for Network Login Script corresponds to a network script file in directory <NGM-root-dir>\ASYNC\SCRIPTS. As Novell continues to expand the list of supported network scripts, newly certified network script files will be made available from the locations mentioned at the end of this document. To update your server with new or enhanced network script files, copy them to this directory. 7) The asynchronous outbound links for public hubs CSERVE and NHUB in the default installation are provided as examples. If you do not want to route messages to CSERVE or NHUB, be sure to delete these servers that are located in the Foreign Domain "Public Hubs." To delete these public hubs, first delete the links to these public hubs with NGMADMIN. Choose menu This Server, Server-to-Server Links, Outbound Async Link, and select the public hubs. Press the DEL (Delete) key to delete the links. Return to the main menu and choose Foreign Domains. Press the DEL key to delete the public hubs. However, if you plan to route messages to CSERVE or NHUB, be sure to enter appropriate information, such as the telephone number for Compuserve or NHUB. At the time of this release, CSERVE handles only SMF Version 70 mail format, which is the pre-configured value for this server. When CSERVE is upgraded to handle SMF Version 71, you should modify the associated SMF Versions. To modify the CSERVE SMF version, choose Foreign Domains, Public Hubs, Messaging Servers, CSERVE, Server Configuration and select SMF Version from the form. You will see a pick-list of versions. Choose "Version v71". For more information, refer to the section "Configuring an Async Link to CompuServe" in the Connecting NGM to CompuServe Mail Hub manual. 8) Inbound and outbound asynchronous passwords for server-to-server logins over asynchronous (modem) links are optional. CompuServe does not use these passwords. Instead, the password supplied to you by CompuServe is required in the Hub Service Login form. 9) Outbound Async Links configurations have a field, Optional Modem Commands, for special outbound connections such as international calls. For example, an administrator who has in-depth knowledge of modems can use this field to enter a modem command to specify guard tones when calling within or to Europe. See "Troubleshooting Asynchronous Communications," later in this file, for information about troubleshooting problems with asynchronous communication. ------------------------------------------------------------- Compatible Versions of AIO ------------------------------------------------------------- The following versions of AIO (not the AIO Driver NLMs) are compatible with Global MHS: Version 1.02 (shipped with Global MHS 2.0a) Version 5.0 (shipped with NetWare 3.12 and also with Global MHS 2.0b) We do not recommend that you install the first release of NetWare Connect with this version of Global MHS. However if you have over- riding considerations, contact Novell Labs to obtain the proper version of the AIO Driver NLM for your serial I/O adapter and then follow the instructions given below. ------------------------------------------------------------- Preparing Global MHS to co-exist with NetWare Connect. ------------------------------------------------------------- If you install NetWare Connect, you must use the version of AIO that is shipped with it - Version 2.0. You must also use the appropriate AIO Driver(s) shipped with NetWare Connect, not the ones shipped with Global MHS. If you have installed NetWare Connect prior to installing Global MHS, you must decline the Global MHS installation prompt to overwrite the AIO NLM that was installed by NetWare Connect. If you have installed Global MHS prior to installing NetWare Connect, you must first delete the Configured Async Ports using the Global MHS Admin - NGMADMIN - as described below. Then follow the procedures to configure the serial (AIO) ports. If Global MHS has been installed and configured "before" NetWare Connect 1.0 is installed, perform the following steps: 1 - Start Global MHS (by loading NGM) and then load the Administrative utility, NGMADMIN. 2 - Verify that messages are not being transferred via modems at this point in time. 3 - Select "Configure Asynchronous Ports" from the This Server menu, select each configured port, and write down the parameters such as modem type, speed, etc. 4 - Delete each port that appears in the "Configured Ports" list by selecting each port and then pressing the delete key. 5 - Exit NGMADMIN and unload Global MHS (by unloading NGM). Follow the procedure described in the Global MHS Administration manual. 6 - Manually unload any AIO Driver(s) and then the AIO NLM. 7 - Install the NetWare Connect product using the procedures described in the NetWare Connect Administration Guide. ------------------------------------------------------------- Configuring serial AIO ports for the AIO shipped with NetWare Connect ------------------------------------------------------------- Perform this procedure prior to using Global MHS after NetWare Connect has been installed. 1 - Manually load the AIO NLM and the appropriate AIO Driver as described in the NetWare Connect Administration Guide. 2 - Load the AIOCON utility installed by NetWare Connect. 3 - Using AIOCON, configure each of the ports (to be used by Global MHS) with the "Configure Ports" selection on the Communication Port Options menu. Specify the appropriate modem type and set the Link Parameters to eight data bits, no parity, and one stop bit. 4 - VERY IMPORTANT: Select "Applications Allowed" in the Port Configuration menu and use the insert key to add the application name AIO. If the port is to be used by Global MHS, use the delete key to remove the application name CONNECT. Repeat this step for each port to be used by Global MHS Async. 5 - You are now ready to configure (or reconfigure) the AIO ports using the Global MHS Administrative utility, NGMADMIN. Follow the procedure described in the Global MHS Administration Manual to Configure Async Ports. If you performed the procedure above, "Preparing Global MHS to coexist with NetWare Connect", use the parameters that were written down in step three of that procedure. ------------------------------------------------------------ New/modified Async Configuration Parameters for Global MHS 2.0b ------------------------------------------------------------ SYSTEM\NGM.CFG [NGMAMP]: Allow-Message-Exchange-With-Unknown-Users (default = FALSE) Since remote user messages are submitted into the MHS\MAIL\QUEUES directory, which does not enforce sender validation, setting this option to TRUE might allow "bogus" remote users to submit "bogus" messages. However, this option allows remote users to submit messages into public hubs that do not have configuration information on all users. Filter-Banner-File (default = TRUE) Non-printable characters from the received BANNER.TXT file are not written to the port-specific log file unless the value is explicitly set to FALSE. Suspend-Queue-After-Retry (default = 15) retries Range of values is 1 to 2440. The number of retries is checked after an error has occurred trying to deliver a message. Polling connections are not affected by this suspension. Wait-For-Idle-Delay (default = 300 seconds) Specfies the duration of time in seconds before the connection is terminated due to lack of progress in message transfer. FORWARD.SMF file: Remote-Applications: (default = <preferred application>) Any number of application names, separated from one another with a comma, can follow the "Remote-Applications" keyword. This option applies only to the support of Part-Time Remote users of NetWare Remote MHS. For more information, see the MHS Administrator's Guide for Connecting to NetWare Remote MHS. TROUBLESHOOTING ------------------------------------------------------------ General Troubleshooting ------------------------------------------------------------ By default, NetWare allows logins to other NetWare servers. If your Global MHS server cannot deliver messages to another server, ensure your AUTOEXEC.NCF file contains the following line: set reply to get nearest server=on This is a NetWare parameter that is accessible by using the set command at the server console prompt. ------------------------------------------------------------ Troubleshooting in Low Memory Situations ------------------------------------------------------------ 1) If the SMF log file contains messages that indicate address translation attempts are failing, or the NetWare console displays messages that indicate Global MHS is unable to allocate xxxx bytes, you may need to increase the amount of memory allocated by Global MHS. To increase the amount of Global MHS memory, also known as NAAMM memory, add the following line to section [NGM] in file SYS:\SYSTEM\NGM.CFG, then unload and reload Global MHS. Maximum-Alloc-Memory=xxxx where xxxx is the number of 1024-byte blocks. For example, to increase the amount of NAAMM memory to 3 MB, add the following line: Maximum-Alloc-Memory=3072 When selecting a value for the NAAMM memory, keep in mind the NAAMM memory is not available for use by other NLMs. For more information on NetWare memory allocation, refer to the NetWare Version 3.11 Installation manual. The default NAAMM memory is 2 MB, which is adequate for most installations. For more information, see section "Parameters for Regulating Message Flow," earlier in this file. 2) If the NetWare server frequently encounters a low Global MHS memory condition, unload Global MHS, increase the value of the Maximum-Alloc-Memory parameter in section [NGM] of file NGM.CFG, and restart Global MHS. The default value for Maximum-Alloc-Memory is 2048 KB. The following example resets the amount of Global MHS memory to 3064 KB (3 MB). [NGM] Maximum-Alloc-Memory = 3064 If the system encounters a low NetWare free cache memory condition, try unloading unneeded NLMs until enough space is released to restart message processing (Resume-message processing threshold). (See "Parameters for Regulating Message Flow," which is earlier in this file.) The first candidate to unload is NGMADMIN. Also, try unloading other NLMs. If you can free enough memory, Global MHS automatically re-enables message processing. If this action does not work, try downing the server and bring it back up. If you continue to have problems with low free cache memory, you may need to purchase more RAM memory for your NetWare server. If the system encounters a low free disk space condition, do not unload Global MHS. Delete unnecessary files and purge them until the disk free space enable threshold (Resume-message processing threshold) is exceeded. ------------------------------------------------------------- Troubleshooting Directory Synchronization Problems ------------------------------------------------------------- 1) If you have a problem enabling directory synchronization at a Global MHS domain member, use the following check list to determine the cause of the problem. Also, scan the NGMDSYNC log files at the domain member and domain hub. a) The directory synchronization process may still be processing data. If the link between the member and the hub is fast (e.g., NIMP link) and the load on the servers is light, you can expect the state of the domain member to change from "Install message sent to the Domain Hub" to "Install Reply Received from Domain Hub" within 10 minutes. You can also expect the state to change to "Domain Information Received from the Hub" within the next 10 minutes. The length of time to exchange all user information between all members of your domain depends on the size and connectivity of your messaging network. For example, if your domain has a large community of users and many servers, directory synchronization may take considerably longer. Also,if the link between a member and the hub is over an asynchronous link, the length of time to become a participating server will increase. Another factor is the scheduling policies of the asynchronous links. b) You may have entered either the Domain Name or the Domain Password incorrectly. If these values are incorrect, the domain hub will ignore your requests to become a participating member. If this occurs, run NGMTOOLS to change your server back to a non-participating state. This process may take several hours for member servers with a large number of users, workgroups, and servers. For information on using NGMTOOLS, review the NGMTOOLS.TXT file in directory \NGM\BIN. Alternatively, press the F1 key to display context-sensitive help. c) You may not have configured the link(s) to the domain hub correctly. Ensure that a test message can be sent in both directions between the member and the hub. If you find that you have incorrectly configured the link, correct the problem, and retry the queues to continue directory synchronization. Directory synchronization messages can be easily distinguished in the queues by the recipient name, which starts with "nme-cmp-". If you use an asynchronous link to reach the domain hub, ensure that messages generated at the hub will be sent back to the domain, either by enabling polling on the link or configuring a link for each direction. d) If the links between the hub and the member are set up correctly and the queues do not have pending directory synchronization messages, and participation takes an inordinate amount of time, run NGMTOOLS at every participating server in your domain, including the new member, to change the state of the new member to non-participating. Then, restart the process. e) If the previous steps do not correct your problem, restore all participating servers in your domain and the new member from your latest backup. Restore the two directory trees that contain Global MHS: (1) the directory specified as "NGM-directory" in file SYS:\SYSTEM\NGM.CFG, (2) the directory specified as "MHS-directory" in file SYS:\SYSTEM\NGM.CFG. 2) While a server is converting to a participating server, transfer of messages can be disrupted temporarily. This can occur because directory database information is being shared between servers over the same message transfer links (NIMP or NAMP links). When directory synchronization completes, transfer of user messages resumes. While a server is converting to a participating server, user messages that reside in protocol module queues may not be delivered. If this occurs, send the messages by selecting Verify Queue in the Queues menu item, which is in the Maintenance menu of the NGMADMIN utility. For more information, see page 9-20 in the NGM Administration manual. ------------------------------------------------------------ Troubleshooting Asynchronous Communications ------------------------------------------------------------ 1) When using the COM port driver, heavy disk activity may cause retransmission of data over an asynchronous link. If this occurs, NGMAMP log files may reflect one of the following conditions: send timeout, receive timeout, CRC errors, etc. To correct this, Novell recommends the use of an intelligent serial I/O adapter. For more information, refer to the Installing NGM manual. 2) If NGMAMP-related log files indicate a failure to establish a outbound connection with a specific remote server, try disabling Modem Negotiation or selecting a lower Modem Speed in the Outbound Async Link configuration. 3) If NGMAMP cannot establish a connection, try increasing the Verbosity Level to 9, to capture more log information for the log file that is associated with the asynchronous port. Then, force a connection by invoking Force a Connection under the Maintenance menu and scan the log file for the log event "Modem Response ...". If a sequence of periods follow this entry and no characters are listed (typically "ATZ 0d 0a ..."), NGMAMP is not receiving characters from the modem. Check the following items: (a) Is the AIO Driver for your server hardware loaded? For information on adding and configuring an AIO driver, refer to Chapter 4 of the Installing NGM manual. (b) Does your port appear in the Configured Asynchronous Ports menu? For information on adding and configuring a port, refer to Chapter 6 of the NGM Administration manual. (c) If this is an external modem, are the required serial handshake signals connected to your modem? Is the TR (Terminal Ready) LED illuminated? Does the SD (Send Data) LED flicker when NGMAMP tries to initialize your modem? Check your serial cable and AIO driver configuration. If all conditions listed above are met, then you should follow one of the procedures described below to force NGMAMP to re-initialize the modem. 4) You can force NGMAMP to re-initialize a modem by either: o cycling power on a modem o invoking Reset Asynchronous Ports from Maintenance menu o reloading NGMAMP.NLM Cycling power on a modem does not always work and only applies to external modems. Reset Asynchronous Ports enables you to selectively reset individual modems (associated with the port). Be sure to wait for the modem Send Data LED to flicker before continuing. Reloading NGMAMP.NLM always reinitializes all modems. The procedure to reload NGMAMP.NLM follows: (a) In the Maintenance Flow Control screen, set Inbound Allowed and Outbound Allowed to "No" for the NGMAMP module. Confirm the change by exiting the screen. (b) Wait for all modem activity to cease; the CD (Carrier Detect) LED's are off and the SD (Send Data) LED's stop flickering. (c) Exit NGMADMIN. (d) UNLOAD NGMAMP. Follow the instructions on the system console screen. (e) LOAD NGMAMP again. Step 3 reinitializes all modems. SOLUTION Self-Extracting File Name: NGM170.EXE Revision: A Files Included Size Date Time \ NGM170.TXT (This File) PATCH.EXE 78129 01-19-93 12:18a FSERIAL.EXE 13314 10-06-93 12:13p README.UPG 11601 10-11-93 12:28p NGM20B.RTP 700341 10-14-93 10:00a PATCHNGM.BAT 2887 10-14-93 11:00a Installation Instructions: BEFORE YOU INSTALL Global MHS 1) Be sure the time zone of your NetWare server is set correctly. Insert the SET TIMEZONE command in the AUTOEXEC.NCF file before loading CLIB.NLM. For information on setting the time zone, see the NetWare Version 3.11 System Administration manual. 2) The compatible versions of Global MHS and Global MHS optional protocol modules are shown below: NetWare Global MHS 2.0b is compatible with: NGMSMTP 1.0 and 1.0b NGMSNADS 1.0b and 1.0c NetWare 2.0 is compatible with: NGMSMTP 1.0 NGMSNADS 1.0b 3) BEFORE YOU INSTALL Global MHS, BE SURE YOU ARE USING A COMPATIBLE VERSION OF CLIB.NLM Novell recommends that Global MHS 2.0 users use CLIB.NLM 3.11 revision E (Feb 3, 1993), or later. CLIB.NLM 3.11 revision E is a new version of CLIB. This version is not the standard version shipping with NetWare 3.x. CLIB.NLM 3.11 revision E is installed into directory \NGM\BIN during the Global MHS installation procedure. 4) CLIB revisions and their identifying attributes are as follows: ----------------------------------------------------- Version Date Size Time ----------------------------------------------------- CLIB 3.11b Sep 4, 92 261,863 6:49p CLIB 3.11c Nov 20, 92 266,432 10:46a CLIB 3.11d Dec 16, 92 267,068 7:33a CLIB 3.11e Feb 3, 93 269,642 1:00p ----------------------------------------------------- NOTE: Do not use CLIB 3.11c with Global MHS. 5) BEFORE YOU INSTALL Global MHS, BE SURE YOU ARE USING A COMPATIBLE VERSION OF BTRIEVE.NLM Global MHS 2.0 works with either BTRIEVE 5.15 or BTRIEVE 6.0b. Novell recommends that you upgrade to BTRIEVE 6.0b if you are using an earlier version of BTRIEVE. BTRIEVE 6.0b is automatically installed into directory \NGM\BIN during the Global MHS installation procedure. When enabling the new BTRIEVE, you may want to copy the BTRIEVE files to SYS:\SYSTEM. 6) When loading BTRIEVE 6.0b, be sure to load BTRIEVE.NLM with the page size set to 4096, as shown in the following command, before installing Global MHS. Global MHS requires the page size be set to 4096. LOAD BTRIEVE -p=4096 Remember to update your AUTOEXEC.NCF file with the -p=4096 parameter. 7) In order to run the DIRADM and SMFSEND utilities, you must load BPPXCOM.NLM. BSTART.NCF is a batch file tht loads BSPXCOM.NLM and BTRIEVE automatically, with the appropriate parameters. 8) Global MHS 2.0 is not compatible with BTRIEVE 6.0. Do not use BTRIEVE v 6.0 with Global MHS. Use of BTRIEVE 6.0 can cause loss of data. 9) PATCH311.NLM is a dummy NLM that is provided because BTRIEVE 6.0b requires access to PATCH311.NLM on the search path. NOTE: This release of BTRIEVE for Global MHS 2.0 does not include the BTRIEVE 6.0b Requesters (DOS, Windows, and OS/2) or the Roll Forward utilities (DOS, Windows, and OS/2). If you are using the file server as a database server, you will need to download these Requesters and utilities from NetWire. For more information about the BTRIEVE components, see the BTRIEVE Readme file (README.BTR) in directory \NGM\BIN. 10) When Global MHS installs from diskettes, the installation program creates a database that conforms to the format of the currently installed BTRIEVE. For example, if your server is executing BTRIEVE version 5.15, Global MHS creates a version 5.15 BTRIEVE database. If you want to use the BTRIEVE 6.0b or later that is installed into directory \NGM\BIN, ensure that your NetWare search path is set correctly to access this version of BTRIEVE. Then, run the BREBUILD.NLM utility that is provided in \NGM\BIN to convert the following Global MHS databases to version 6.0b BTRIEVE databases. \MHS\MAIL\PUBLIC\NAMES.DBF \MHS\MAIL\PUBLIC\ROUTES.DBF 11) BTRIEVE revisions and their identifying attributes are as follows: ----------------------------------------------------- Version Date Size Time ----------------------------------------------------- BTRIEVE 5.15 Aug 4, 92 66,688 1:23a BTRIEVE 6.0 May 7, 92 144,922 9:40a BTRIEVE 6.0b Dec 1, 92 146,258 11:06a ----------------------------------------------------- ------------------------------------------------------------ Location Of Netware Global MHS Directories ------------------------------------------------------------ For information about the locations of the NGM and MHS directory trees, refer to the "NGM-directory" and "MHS-directory" values in file SYS:\SYSTEM\NGM.CFG. The default values of these directories are: NGM-directory=SYS:\NGM MHS-directory=SYS:\ ------------------------------------------------------------ Unloading the Global MHS Software Successfully ------------------------------------------------------------ There may be times that you may need to unload the Global MHS software, for example, before bringing the NetWare server down. First unload NGMADMIN.NLM. Then enter the following to unload NGM.NLM: UNLOAD NGM at the NetWare server console. The server console displays the following warning message: Do you want to unload anyway? Be sure to answer 'N' (No) to allow Global MHS to complete normal clean-up processing, which can take several minutes. Global MHS unloads whether you answer Yes or No; if you answer No, Global MHS then unloads as soon as it can safely do so. WARNING: If you: (a) answer Yes, OR (b) answer No and do not wait until NGM.NLM has unloaded, your server may abend or damage your file system. ------------------------------------------------------------ Upgrading MHS 1.5 Hosts ------------------------------------------------------------ If file NETDIR.TAB contains blank full names, NGMUPGDE.NLM (Global MHS upgrade) uses the short name (Name8) as: a) local part of the NGM name, and b) default value for the full name This configuration results in Global MHS sorting the EXTRACT file according to the short name. Filling in full names in NETDIR.TAB is not required. However, Novell recommends use of the full name in NETDIR.TAB, prior to Global MHS upgrade. (Full names for users are added through the "User at this host" form in the Directory Manager. See the NetWare MHS Installation and Operation manual for more information. 2) Upgrading An MHS 1.5 Host with Queued Mail: Global MHS uses a new naming convention for queued message filenames. If you upgrade an MHS 1.5 host that has queued mail, you will need to manually rename the filenames of the queued messages. To upgrade a queue filename to the new Global MHS naming convention, you will need to add the character '#' to the beginning of the suffix of each queue filename. For example, assume an upgraded MHS host contains the following files in the QUEUES directory. \<MHS-root-dir>\MAIL\QUEUES\SERVER1.0 \<MHS-root-dir>\MAIL\QUEUES\SERVER1.000 \<MHS-root-dir>\MAIL\QUEUES\SERVER1.001 \<MHS-root-dir>\MAIL\QUEUES\SERVER2.0 \<MHS-root-dir>\MAIL\QUEUES\SERVER2.000 You will need to rename these files to the following filenames: \<MHS-root-dir>\MAIL\QUEUES\SERVER1.# \<MHS-root-dir>\MAIL\QUEUES\SERVER1.#00 \<MHS-root-dir>\MAIL\QUEUES\SERVER1.#01 \<MHS-root-dir>\MAIL\QUEUES\SERVER2.# \<MHS-root-dir>\MAIL\QUEUES\SERVER2.#00 The DOS RENAME command provides an easy method to upgrade the queue filenames to the new Global MHS naming convention. For example, to rename the *.0 and *.00 files, use the following DOS commands. RENAME *.0 *.# RENAME *.000 *.#00 ... These commands will rename the *.0 and *.000 files for all servers. If you also have *.01, *.02, ..., files in the QUEUES directory, repeat the RENAME command as necessary. ------------------------------------------------------------ Upgrading a Basic MHS Server to Global MHS ------------------------------------------------------------ The BASTONGM.NLM is used to: - Convert a Basic MHS server to a Global MHS routing server - Convert a Basic MHS server to a Global MHS passive server If BASTONGM.NLM encounters a situation where a user or distribution list long name or short name already exists in the database into which you are trying to add it, BASTONGM.NLM creates a new workgroup (a "conflicts" workgroup). (This is done to preserve the Basic MHS information.) The name of the "conflicts" workgroup is in the following form: shortnameofserver-conflicts.root workgroup If BASTONGM.NLM tries to add the user or distribution list to the conflicts workgroup, but encounters a short name conflict because another user in a workgroup on the same server has that short name, BASTONGM.NLM will generate a new short name and and a mailbox for the user, and add a new entry to NETDIR.TAB. Upgrade and Conversion Statistics: Messages about the upgrade or conversion will be written to the log file. Based on the statistics it gathers, BASTONGM.NLM determines whether a successful, partial, or failed upgrade occurred. If the upgrade only partially executed or it failed, consult the log file to determine whether you should execute BASTONGM.NLM again. A. Steps to Convert a Basic MHS Server to a Global MHS Routing Server 1) Run NGMINS.NLM on an already-configured Basic MHS server. (Type LOAD NGMINS at the server console prompt.) Follow the instructions on the console. NGMINS will add an autoload bastongm statement to the NGM.CFG file. 2) Load NGM; this will autoload all the other NLMs, including BASTONGM.NLM. NOTE: If the upgrade does not execute successfully, you will be prompted to reload BASTONGM.NLM. You might want to check the log file to determine the cause of the problem before reloading BASTONGM.NLM. B. Steps to Convert a Basic MHS Server to a Global MHS Passive Server IMPORTANT: Conversion of a Basic MHS server to a Global MHS passive server might take a while to complete, depending on the number of distribution lists and users on the Basic MHS server. Allow the conversion process to complete before creating another passive server. 1) Run NGMADMIN on the master Global MHS server. 2) Select the This Server option, then the Passive Messaging Servers option. Configure the Passive Server form as you would when configuring any other server as a passive server to your Global MHS server. When filling out the fields, specify the Basic MHS directory as the value for the MHS the MHS Directory Area field. DO NOT SPECIFY A CONFLICTS WORKGROUP AS THE DEFAULT WORKGROUP! NOTE: If the conversion does not execute successfully, you will be prompted to reload BASTONGM.NLM. You might want to look in the log file to determine the cause of the problem before reloading BASTONGM.NLM. Solution Specifics: This section contains information about changes were made for Global MHS version 2.0b. 1) NGMSMF, the MHS INET module, now delivers mail concurrently to multiple remote destinations. Previously, NGMSMF delivered mail to remote servers sequentially. See "NGMSMF Now Delivers Remote Mail Concurrently," in this section. This section contains information about changes for the NGMSMF module status that is shown in the Flow Control option. 2) The NetWare login name is now linked with the MHS short name. See "New Parameter For Linking Netware Login Name With the MHS Shortname" in this section. 3) You can now import a group other than the group EVERYONE from the Bindery. See "New Parameters Added For Importing A Group Other Than Everyone From the Netware Bindery" in this section. 4) New attributes were added to the [User] input file element of the DIRADM utility. See "New Attributes For The User Element In The DIRADM Utility" in this section. 5) For SMF v70 addresses that contain .email as the application extension (for example, john.email@Acme), Global MHS now sends the message to the user's preferred application. 6) For messages sent to another Global MHS server through an MHS 1.5 host, Global MHS now replaces -SMF71- in the username of the From address with a shortname. See "Global MHS Now Inserts a Short name in Messages Routed Through MHS 1.5 Hops" in this section. 7) The names of the prompts on the Schedule Information form in the Scheduling Policies option were changed. See "Names of Prompts for Scheduling Asynchronous Links Were Changed" in this section. 8) If you are installing Global MHS 2.0b for the first time, Global MHS will automatically load NGMEXTRC.NLM. If you are applying the Global MHS 2.0b patch, you must manually load NGMEXTRC.NLM. Also add an autoload statement for NGMEXTRC.NLM in the NGM.CFG file so that NGMEXTRC.NLM will be automatically loaded in the future. See "NGMEXTRC.NLM is Automatically Installed With a New Install" in this section. 9) For servers to which Global MHS connects via asynchronous links, Global MHS now automatically suspends delivery attempts to that remote server when the number of delivery attempts specified in the NGM.CFG file is reached. See " Automatic Suspension of Delivery Attempts" in this section. 10) NGMAMP now supports the rejection of messages that contain the Expiration-Date SMF header option. Messages that are in a suspended or misconfigured queue are excluded from this check. 11) Starting with this version, users addressing mail to CompuServe for store-and-forward message relay must always use the "user@workgroup" form of addressing. (Previous versions of Global MHS allowed a user to address mail to either "user@server" or "user@workgroup" when sending mail to CompuServe for store-and-forward message relay.) 12) A "Reset Asynchronous Ports" menu selection was added to the Maintenance Options menu. 13) The Routing Server field was added to the Workgroup Configuration form and the Workgroup Owner field was renamed to the Master Copy Server field. See "New Fields on the Workgroup Configuration Form" in this section for details about the use of these fields. 14) New parameters are available in the FORWARD.SMF file that provide more flexibility for users who want to forward their messages to other users. See "Parameters Added to the FORWARD.SMF File for Forwarding Mail" at the end of this section. ------------------------------------------------------------ NGMSMF Now Delivers Remote Mail Concurrently ------------------------------------------------------------ NGMSMF, the MHS INET module, now delivers mail concurrently to multiple remote destinations. This change has significantly improved message delivery time. Previously, NGMSMF delivered mail to remote servers sequentially. In addition to this change in functionality, the status screen in the Flow Control option now displays connection information more precisely, as described below. The NGMSMF module now shows data that applies ONLY to local delivery, and the SMF gateways and passive servers associated with your server. Previously, the NGMSMF module showed data that pertained to both local delivery and remote delivery. The NGMIMP module shows data that applies to concurrent delivery of SMF-based messages to remote servers. ----------------------------------------------------------- New Parameter For Linking Netware Login Name With the MHS Short Name ------------------------------------------------------------ By default, Global MHS uses the first eight characters of the Bindery name (NetWare Login Name) to create the MHS user short name. This default is set in the following parameter in the NGM.CFG file: USE-NETWARE-LOGIN-NAME=TRUE Novell recommends that you leave this parameter set to TRUE unless you have a specific reason for wanting the NetWare login name and MHS user short name to be different. The following examples show the types of MHS short names that Global MHS will create if you set this parameter to FALSE. If the login name is JOHN and the fullname is JOHN HOLLISTER SMITH, Global MHS would create an MHS short name of JHSMITH. If the login name is JOHN and the fullname is JOHN SMITH, Global MHS would create an MHS short name of JSMITH. ------------------------------------------------------------ New Parameters Added For Importing A Group Other Than Everyone From the Netware Bindery ------------------------------------------------------------ Global MHS provides an option, Import Users from Bindery, which you can use after installation to automatically create user accounts and mailboxes for NetWare users on your server. (Global MHS converts a Bindery user's NetWare login name to an NGM (MHS) short name and the user's fullname to an NGM long name.) By default, Global MHS creates user accounts and mailboxes for all users in the Bindery group EVERYONE and assigns those users to the default workgroup for the Global MHS server. You can change either or both of these default settings by changing the following parameters in the NGM.CFG file. BINDERY-GROUP-TO-IMPORT=sales {default is EVERYONE} You can change the value of this parameter to a specific group. NGM-WORKGROUP=sales.Acme {default is the server's default workgroup} You can change the value of this parameter to any workgroup that the server owns or to which it subscribes. ------------------------------------------------------------ New Attributes For The User Element In The DIRADM Utility ------------------------------------------------------------ Three attributes were added to the [User] input file element in the DIRADM utility so you can specify a user's Bindery login name and applications. The attributes that were added are: ATTRIBUTE DESCRIPTION Bindery User's Bindery login name. Default-App User's preferred application. App1 User's other applications, 1 - 4. For example: [PREAMBLE] Origin=server1.Acme Version=1 Type=Update Date= [User] SMF-Name=Admin@Acme FullName=Acme Title=Admin for server1 SMF-Short-Name=Admin@Acme Bindery=Admin Default-App=MHS Mail-Server=server1.Acme [User] SMF-Name=john smith@Acme FullName=smith, john SMF-Short-Name=johnsmit Bindery=johnsmit Default-App=DVSEMAIL App1=MHS Mail-Server=server1.Acme ------------------------------------------------------------ Global MHS Now Inserts a Short Name in Messages Routed Through MHS 1.5 Hops ------------------------------------------------------------ Previously, a message routed through a MHS 1.5 hop sometimes showed -SMF71- in the From address when it was delivered to the Global MHS recipient. Global MHS now uses information in the extended address field to form a shortname and puts that short name in username portion of the From address. The recipient can reply to the message unless the recipient's application strips the extended address from the message header. NOTE: The short name that Global MHS inserts is not necessarily the same as the MHS short name configured for the user in Global MHS. The recipient cannot use the short name to send a message later. ------------------------------------------------------------ Names of Prompts for Scheduling Asynchronous Links Were Changed ------------------------------------------------------------ The prompts on the Scheduling Information form (accessed through Local Domain-->Scheduling Policies-->Configuration options) were changed as follows: NEW PROMPT OLD PROMPT When messages are pending Connect if a message has been Forced Connection Interval waiting for more than (minutes): OR if the number of messages queued Connection Threshold is greater than: When no messages are pending Poll for incoming messages once Polling Interval every (minutes) However, don't connect more than once Connection Interval every (minutes): Upon connection failure retry every Retry Interval (minutes): Reject if message cannot be delivered Non-Delivery Interval within (days) ------------------------------------------------------------ NGMEXTRC.NLM is Automatically Loaded with a New Install ------------------------------------------------------------ SMF-based messaging applications typically provide a list of message recipients. NGMEXTRC.NLM must be loaded for the applications to obtain the user information for their Address books. If you are doing a fresh install of Global MHS 2.0b, Global MHS will automatically load NGMEXTRC.NLM. If you are applying the Global MHS 2.0b patch, you must manually load NGMEXTRC.NLM and also add the following autoload statement to the NGM.CFG file in the [NGM] section so that NGMEXTRC.NLM will be automatically loaded in the future. AUTOLOAD=NGMEXTRC.NLM ------------------------------------------------------------ Resetting Of a Port Modem, or Connection ------------------------------------------------------------ A "Reset Asynchronous Ports" menu option was added to the Maintenance Options menu in Global MHS 2.0b. This option requests an immediate "reset" of a port/modem/connection, whether it is inactive or active. ------------------------------------------------------------ Automatic Suspension of Asynchronous Delivery Attempts ------------------------------------------------------------ For remote servers reached via asynchronous links, Global MHS now automatically suspends delivery attempts after the number of attempts specified in the NGM.CFG file has been reached. This value is specified in the Suspend-Queue-After-Retry parameter in the [NGMAMP] section. The default value for this parameter is 15 (retries). After you fix the cause of the problem, use the Resume/Suspend Connectivity option on the Maintenance menu to resume connectivity to the remote server. NOTE: Polling connections are not affected by this suspension. ------------------------------------------------------------ New Fields on the Workgroup Configuration Form ------------------------------------------------------------ The field Routing Server was added to the Workgroup Configuration form and the field Workgroup Owner was renamed to Master Copy Server. The meanings of these fields are shown below: FIELD DESCRIPTION Master Copy Server The name of the Global MHS server whose administrator can edit the information. Routing Server The NGM name of the Global MHS server or non-Global MHS server that has the most knowledge of how to reach the users in the workgroup. The following examples will help you determine the appropriate value for each of these fields: Example 1: You add a new workgroup to your server (GMHS1) -------- | GMHS1 | <-- Server GMHS1 adds workgroup xyz.Acme -------- Server GMHS1 is the Master Copy Server and the Routing server. Example 2: All Global MHS servers are participating servers and share a workgroup -------- -------- | GMHS1 | | GMHS2 | <-- Your server, GMHS1, added workgroup -------- -------- xyz.Acme so is the Master Copy Server. -------- -------- | GMHS3 | | GMHS4 | Assume that GMHS2, GMHS3, and GMHS4 -------- -------- now subscribe to workgroup xyz.Acme. GMHS1's administrator is the only person who can change the configuration of workgroup xyz.Acme, since GMHS1 is the Master Copy Server. For each subscribing GMHS server, the software automatically enters the name of the Master Copy Server (in this case GMHS1) in the Workgroup Configuration form. The software automatically enters the subscribing server's name in the Routing Server field, since each participating Global MHS server that subscribes to a workgroup has information in its database about all users in that workgroup. Example 3: Upgrading MHS 1.5 Hosts that Are Part of a Multihost Workgroup ---------- ---------- A | MHS 1.5 | | MHS 1.5 | C <-- Workgroup-wide Router ---------- ---------- --------- B | MHS 1.5 | Assume that you want to upgrade --------- all three MHS 1.5 hosts to be Global MHS servers. You might choose to first upgrade an MHS 1.5 host that is NOT the Workgroup-wide Router (in this example, host A or B). If B was the first MHS 1.5 host to be upgraded, B would add the workgroup, and thus be the Master Copy Server. In this scenario, B does not have knowledge of the users on host A, so the administrator of B would enter host C (the Workgroup-wide Router) as the Routing Server for the workgroup. Once all three of the MHS hosts are upgraded and participating in directory synchronization, each would be a Routing Server for the workgroup. (For Server B, directory synchronization automatically changes the value of the Routing Server field from Server C to Server B.) Example 4: A Global MHS Host Registers a Workgroup for an SMTP Host -------- -------- | GMHS1 | | SMTP1 | Your server, GMHS1, registers -------- -------- workgroup smtp.Acme for SMTP host SMTP1. GMHS1 is the Master Copy Server; the software automatically enters the name of the Global MHS server who is registering the workgroup for the SMTP host. (Previously, for such a scenario, the SMTP host's name was to be entered in the Workgroup Owner field of the Workgroup Configuration Form.) The Routing Server can be either the Global MHS server or the SMTP host, depending on which computer has the most knowlege of how to reach the users in the workgroup. If, for example, all of the SMTP hosts users were registered in the GMHS1 database, GMHS1 would have enough knowledge of how to route to the users. In this case GMHS1 could be specified as the Routing Server. If only a small number of SMTP users were in the GMHS1 database, the SMTP host would have greater knowledge of how to route to the SMTP users. In this case, enter the NGM server name of the SMTP host as the Routing Server. ------------------------------------------------------------- Parameters Added to the FORWARD.SMF File for Forwarding Mail ------------------------------------------------------------- This section contains information about new parameters that can be used for the FORWARD.SMF file and about the syntax for the file. NEW PARAMETERS: The Forward-To parameter in the FORWARD.SMF file is used to specify another user(s) to whom the user's mail is to be sent. For example, a user going on vacation might want to forward all mail to a colleague while on vacation. Two additional parameters, "Redirect-to:" and "Local-copy:" are now available to give users more flexibility when forwarding their mail to another address. Redirect-to Parameter When a user uses the the Forward-To command to specify the person(s) to whom the mail is to be forwarded, that person(s) is not able to reply to the message. If the user wants the person (to whom the mail is being forwarded) to be able to reply to the messages, the user should use the "Redirect-to:" parameter instead of the "Forward-to:" parameter. NOTE: Both the "Forward-to:" and Redirect-to:" parameters can be specified in the FORWARD.SMF file at the same time. Local-copy Parameter A user can request that a copy of a forwarded message left in the user's mailbox by entering the "Local-copy:" parameter in the FORWARD.SMF file. If the "Local-copy:" parameter is not present in the FORWARD.SMF file, no copy of a forwarded message is kept in the requesting user's mailbox. This is the case for messages forwarded with either the "Forward-to:" or "Redirect-to:" parameter, or both. NOTE: If the "Local-copy:" parameter is used, it applies to both the "Forward-to:" parameter and the "Redirect-to:" parameter. That is, if the user enters both "Forward-to:" and "Redirect-to:" the user cannot specify a local copy be kept for messages sent to addresses listed in the "Forward-to:" parameter but not the "Redirect-to:" parameter and vice versa. Values for the parameters are shown below. All values are case- insensitive. Forward-to: <AddressList> Redirect-to: <AddressList> where <AddressList> is any SMF v71 address; addresses must be separated by comments. Local-copy: <True | False> Example FORWARD.SMF File for user JSMITH: Forward-to: Jane Doe@sales.Acme <-- Jane Doe cannot reply to the message. Redirect-to: Chris Smith@sales.Acme <-- Chris Smith can reply to the message. Local-copy: True SYNTAX FOR THE FORWARD.SMF FILE: You cannot put a blank line between keywords in the FORWARD.SMF file. The system interpretes a blank line as an end-of-file marker and will not read anything below the blank line. Keywords must start at the beginning of the line (in column 1). Continuation lines are allowed. A continuation line must start with one or more blank or TAB characters. ------------------------------------------------------------- IF YOU HAVE QUESTIONS ABOUT NETWARE GLOBAL MHS ------------------------------------------------------------- If you have questions on NetWare Global MHS (NGM), call Novell Technical Support (800-NETWARE, outside the U.S., call 801-429-5588). There are several places where information and updates to supplementary files for Global MHS, such as modem definition files, will be available. These locations include Novell's anonymous FTP site at ftp.novell.com, LIBRARY @ NOVELL, the NetWire forum on CompuServe, and Novell Technical Support.