Liren Large Software Subsidy 11

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

/ Liren Large Software Subsidy 11 / 11.iso / n / n007 / 21.ddi / ADMIN.DOC next >

Wrap

Text File | 1993-07-30 | 64.8 KB | 1,877 lines

BASIC MHS ADMINISTRATION ------------------------ Novell, 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 manual 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. Trademarks Novell, NetWare and the N design are registered trademarks and FirstMail, NetWare Basic MHS, NetWare MHS, NetWare Loadable Module, and NLM are trademarks of Novell, Inc. Macintosh, AppleTalk, and AppleShare are registered trademarks of Apple Computer, Inc. Copyright (c) 1993 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. Portions Copyright (c) 1990-93, David Harris. May 1993 CONTENTS -------- 1 MANAGING THE BASIC MHS SERVER 1.1 Starting the Basic MHS Server 1.2 Reviewing The Log 1.3 Backing Up Your Server 2 MANAGING THE BASIC MHS DATABASE 2.1 Getting Started With the ADMIN Program 2.2 Managing Users 2.3 Managing Distribution Lists 2.4 Managing Applications 2.5 Customizing the Basic MHS Server Configuration 3 MANAGING FIRSTMAIL 3.1 Checking that All FirstMail Files Were Copied 3.2 Restricting User Accounts 3.3 File Naming Conventions 3.4 Setting Up FirstMail for DOS 3.5 Setting Up FirstMail For the Macintosh 3.6 Setting Up Bulletin Boards for DOS and Macintosh Users 4 DIRADM 4.1 DIRADM Syntax 4.2 Input File Format 4.3 Example Input File 5 MHSUSER BASIC MHS ADMINISTRATION ------------------------ The NetWare(R) Basic MHS(tm) product is part of Novell's NetWare MHS(tm) family of products. It provides message delivery among users on the same file server. Basic MHS users can create and submit messages with MHS-compatible electronic mail applications. The Basic MHS installation process also installs FirstMail(tm), an electronic mail utility. FirstMail, which is available in both DOS and Macintosh versions, is provided to help users on your server get started with NetWare Basic MHS. This manual is intended for the administrator of Basic MHS and of FirstMail. It contains detailed instructions for managing the Basic MHS server, the Basic MHS database, and FirstMail. It also contains information about the DIRADM and MHSUSER utilities, which are included with Basic MHS. (These utilities provide command-line access to the Basic MHS database.) The manual assumes that the administrator is familiar with NetWare and DOS. 1 MANAGING THE BASIC MHS SERVER ----------------------------- This section explains how to manage your Basic MHS server. Managing your server involves the following activities: * Starting the Basic MHS server. The Basic MHS server picks up messages submitted by users and delivers them to the recipients' mailboxes (see Section 1.1). * Reviewing the log (see Section 1.2). * Backing up your server (see Section 1.3). 1.1 Starting the Basic MHS Server ----------------------------- This section explains how to start the Basic MHS server so that it will begin delivering messages. 1. Ensure that CLIB.NLM, BTRIEVE.NLM and BSPXCOM.NLM are loaded on the file server. 2. Load BASICMHS.NLM by entering the following command: LOAD SYS:MHS\EXE\BASICMHS [-N<server>/<vol>:<path>\MHS\MAIL] [-S<nnn>] [-V<x><y>] NOTE: If you have set a search path to SYS:MHS\EXE on your file server, you need not include the full path to the NLM in this command. To load the BASICMHS NLM automatically when your file server starts, include this command in the AUTOEXEC.NCF on your file server. The command line parameters for BASICMHS are: -N<server>/<vol>:<path>\MHS\MAIL Use this parameter to identify the path to the MHS\MAIL directory if it is not located at the root of the SYS: volume. This path must be located on the same file server as Basic MHS. -S<nnn> Use this parameter to specify the minimum disk space (in KB) required for message delivery. When the amount of space available is less than the number specified for this parameter, BASICMHS suspends delivery, until more space becomes available. The default value is 200. -V<x><y> Use this option to determine what level of system messages will be logged and displayed on the file server console. Replace <x> and <y> with a number from 0 to 9. The <x> represents the level of verbosity for the file server console and <y> represents the level of verbosity of the log. The greater the number, the more messages will be displayed. The default value for <x> is 5; the default value for <y> is 3. Messages will not be displayed when the verbosity level is equal to 0. 1.2 Reviewing The Log ----------------- BASICMHS generates a log file, called BASICMHS.LOG, in the MHS\MAIL\PUBLIC directory. Events logged include start up, shutdown, and errors. Monitor the log file regularly. It is particularly useful when you are trying to track an error. The log file is in ASCII text format. You can print it or view it with a text editor. Each log entry consists of a date/time stamp, the system message number--preceded by a number sign (#)--and the system message text. Refer to the MESSAGES.DOC file for explanations of log messages. Basic MHS appends log messages to the end of the log file. The file continues to grow until you delete it. Once you have a sense of how long it takes the log file to grow past a manageable size, set up a schedule for deleting it. NOTE: You may find it useful to make a copy of the log file and keep it for a period of three to six months, in case you need to research an intermittent problem. Once you have copied the log file, you can delete it. 1.3 Backing Up Your Server ---------------------- Novell recommends that you back up the Basic MHS data files (especially the files in MHS\MAIL\PUBLIC) and user mailboxes (located in MHS\MAIL\USERS) using your standard file server backup procedures. WARNING: If you are using a version of Btrieve earlier than v6.0, ensure that BASICMHS and the ADMIN program are not running when you back up the data files. If they are running, the data files will be in an inconsistent state, and you will not be able to restore them. 2 MANAGING THE BASIC MHS DATABASE ------------------------------- The Basic MHS database contains USERS, DISTRIBUTION LISTS, APPLICATIONS, and SERVER CONFIGURATION information. You must define in the database each USER whose mailbox is to be serviced by your messaging server. Section 2.2 "Managing Users," explains how to add, change and delete users in your server's database. A DISTRIBUTION LIST is a group of users to whom users at your server can send messages. For example, "Managers" might be a distribution list containing John Smith and Anne Black. When users want to send messages to John and Anne, they address them to the distribution list, Managers. Section 2.3 "Managing Distribution Lists," explains how to add, change, and delete distribution lists in your server's database. An MHS-compatible APPLICATION is an executable software product that uses the message-delivery service provided by Basic MHS. For a complete list of available applications, refer to the "NetWare Messaging Solutions Guide," available from your Novell reseller. Section 2.4 "Managing Applications," explains how to register applications in your server's database, and how to change and delete application registrations. You can change your SERVER CONFIGURATION to customize the way your Basic MHS server operates. Section 2.5 "Customizing the Basic MHS Server Configuration," explains how to change your server configuration. Section 2.1 "Getting Started With the ADMIN Program," explains how to start the ADMIN program, which you will use to manage your server's database. 2.1 Getting Started With the ADMIN Program -------------------------------------- The ADMIN program is the server administrator's interface to the database. ADMIN is a DOS-based program that runs on a workstation. Use this program to manage the users, lists, and applications at your server. 1. Log in as Supervisor or Supervisor equivalent on the file server on which you installed Basic MHS. 2. If you are attached to more than one file server, or if you installed MHS\MAIL in a location other than SYS:MHS\MAIL, you must set the MV environment variable. To do so, enter the following command: SET MV=<mv_path> where <mv_path> is the full path to the MHS\MAIL subdirectory. The path must be in valid NetWare format (for example, SET MV=FS1/SYS:). Do not include the MHS subdirectory in the path. 3. Start the Btrieve requester by entering the following command: BREQUEST 4. Start the ADMIN program. ADMIN is located in the MHS\EXE subdirectory. If this directory is not in your NetWare search path, change into it. Enter the following command: ADMIN The Admin User Login entry box appears. 5. Enter "Supervisor" in the User Name field. You can enter the login ID of any Basic MHS user. However, if the user is not "Supervisor" or Supervisor equivalent, you will not be able to update the database. 6. Enter the user's NetWare password in the Password field. The Admin Functions menu appears. From this menu, you can choose the following options: Users To add, change, and delete users. Distribution Lists To add, change, and delete distribution lists. Applications To register, change and delete applications. Configuration To change the server configuration. NOTE: If you want to bypass the prompts for User Name and Password, you can enter the following commands at the DOS prompt: SET USR=<username> SET PWD=<password> where <username> is the login ID of a NetWare user, and <password> is the user's NetWare password. 2.2 Managing Users -------------- When a new user is added to your server, you must define that user in your server's database. When a user leaves your server, you must delete that user from the database. You can also change a user record (including the username) in the database. During installation, you can import users from the NetWare bindery. If you choose this option, all NetWare users who are not already messaging users will be added to the database. (Users are identified as messaging users if they have trustee rights to a path containing MAIL\USERS.) The bindery import feature creates long names from users' NetWare full names or login IDs, and it creates short names from the first eight characters of users' login IDs. NOTE: Some applications might have a different procedure for managing their users. If the documentation for your application gives instructions for managing users of that application, follow those instructions. 2.2.1 User Information Form The User Information form contains the following fields. User's Long Name (Required) The username, as defined when the user was added. The username is part of the user address, which can contain up to 253 characters. The name can contain any printable characters except the period (.), semi-colon (;), parentheses ( ( ) ), square brackets ( [ ] ), braces ( { } ); comma (,), at sign (@), and tab. (For example, John Smith.) User's Workgroup (Display only) The name of the workgroup to which the user belongs. User's Short Name (Required) ADMIN supplies a short name when you add a new user. To change the short name, enter up to 8 characters, including letters, numbers, and the following special characters: dollar sign ($), hyphen (-), and number sign (#). Personal Info (Optional) Select this field to display the Personal Information form. In this form, you can enter a Last name (32 characters); a First Name and an Initial (32 characters); a Generation Qualifier, such as Jr. or III (8 characters); a Title (24 characters); a Department (24 characters); a Phone Number (29 characters); and any Extra Information (100 characters). Applications (Required) Select this field to display the Application form. A user must have a default application, and can also have up to 4 other applications. MHS will deliver messages to the default application unless the sending application specifically requests delivery to another one. Select the default application and (optionally) up to 4 other applications from the list of registered applications. (To find out how to register applications, see Section 2.4 "Managing Applications.") 2.2.2 Procedure Select "Users" from the Admin Functions menu. The Users list appears. From this list, you can add, change, or delete user records. * To ADD a user record: a. Press <Insert>. The Add New User Entry box appears. b. Enter the name of the new user. The username is part of the user address, which can contain up to 253 characters. c. Enter information into the required fields. d. Press <Esc> and select "Yes" to save the new record. ADMIN prompts for the user's NetWare ID. It displays a default ID. e. Enter the user's login ID or accept the default login ID. * To CHANGE the name or profile of a user: a. Highlight the username and press <Enter>. The User Information form appears. b. Edit the form. c. Press <Esc> and select "Yes" to save the changes. NOTE: When you change the name of a user, ADMIN updates all distribution lists to which the user belongs. When you change a user's MHS short name, ADMIN changes the name of the user's MHS mailbox (the subdirectory containing the user's incoming mail). * To DELETE a user record: a. Highlight the user or, to delete multiple users, mark them by pressing <F5>. b. Press <Delete>. ADMIN prompts for confirmation. c. Select "Yes" to delete the user(s). ADMIN prompts, `Delete User's Mailbox.' d. Select "Yes" to delete users' mailboxes, and all their messages. Select "No" to keep users' mailbox and messages. NOTE: When you delete users from the Basic MHS database, ADMIN deletes them from any distribution lists to which they belong. 2.3 Managing Distribution Lists --------------------------- Defining distribution lists eliminates unnecessary typing. If users want to send a message to all managers and if there are 20 managers, it would be time-consuming to type all 20 names each time they send a message to these people. Each distribution list must have a list of members, which can contain users, other distribution lists, or both. This section explains how to add, change, and delete distribution lists for your users. NOTE: Some applications might have a different procedure for managing their distribution lists. If the documentation for your application gives instructions for managing distribution lists, follow those instructions. 2.3.1 Define Distribution List Form The Define Distribution List form contains the following fields. DList Long Name (Required) Enter the long name. The long name is part of the list address, which can be up to 253 characters long. The name can contain any printable characters except the period (.), semi-colon (;), parentheses ( ( ) ), square brackets ( [ ] ), braces ( { } ), comma (,), at sign (@), and tab. (For example, Sales Managers.) DList Workgroup (Display only) The workgroup to which the list belongs. DList Short Name (Required) ADMIN supplies a default short name. To change it, enter up to eight characters, including letters, numbers, and the following special characters: hyphen (-), dollar sign ($), and number sign (#). Description (Optional) Enter a description of up to 60 characters. 2.3.2 Procedure Select "Distribution Lists" from the Admin Functions menu. The Distribution List window appears. * To ADD a new distribution list: a. Press <Insert>. The Define Distribution List form appears. b. Complete the form. c. Press <Esc> and select "Yes" to save the new list. * To CHANGE the name or profile of an existing list: a. Highlight the list and press <F3>. The Define Distribution List form appears. b. Edit the form. c. Press <Esc> and select "Yes" to save the changes. * To DELETE a list: a. Highlight the list or, to delete multiple lists, mark them by pressing <F5>. b. Press <Delete>. ADMIN prompts for confirmation. c. Select "Yes" to delete the list(s). * To DELETE A MEMBER from the list: a. Select the distribution list from which you want to delete a member. b. Highlight the member you want to delete or, to delete multiple list members, mark them by pressing <F5>. c. Press <Delete>. ADMIN prompts for confirmation. d. Select "Yes" to delete the member(s). e. Press <Esc> to exit from the member list and select "Yes" to save the changes. * To ADD A MEMBER to the list: a. Select the distribution list to which you want to add a member. b. Press <Insert>. ADMIN displays a list of users and distribution lists in the Basic MHS database. c. Highlight the member you want to add or, to add multiple members, mark them by pressing <F5>. d. Press <Enter> to add the new member(s) to the list. e. Press <Esc> to exit from the member list and select "Yes" to save the changes. 2.4 Managing Applications --------------------- This section explains how to register applications with Basic MHS and how to change and delete application registrations. Read this section if you are installing or have installed an MHS-compatible application on your messaging server. You must register an application with Basic MHS if you want your server to deliver messages to that application. The installation process automatically registers MHS as an application. NOTE: Some applications might have a different procedure for application management. If the documentation for your application gives instructions for managing the application, follow those instructions. 2.4.1 Application Form The Application form contains the following fields. Application Description (Required) A description of the application. Enter up to 24 characters that describe the application. Application Short Name (Display only) The short name, as defined when the application was added. Maximum Number of Users (Display only) The maximum number of users this application will support; the value will be set when you install this application. Current Number of Users (Display only) The current number of users using this application. SMF Version (Required) The SMF version defined when the application was added. Refer to the application documentation to find out which version to select. The default value is SMF-71. 2.4.2 Procedures Select "Applications" from the Admin Functions menu. The Applications list appears. * To REGISTER a new application: a. Press <Insert>. The Define Application entry box appears. b. Enter information in the following fields. Application Description Enter a description of up to 24 characters. Application Short Name Enter the short name for the application. You can enter up to eight characters, including letters, numbers, and the following special characters: hyphen (-), dollar sign ($), and number sign (#). Refer to the application documentation to determine which short name to use. c. Press <Enter>. The Application form appears. d. Ensure the SMF version is correct. e. Press <Esc> and select "Yes" to save the new application. * To CHANGE an application: a. Highlight the application and press <F3>. The Application form appears. b. Edit the Application Description or SMF version. c. Press <Esc> and select "Yes" to save the changes. * To DELETE an application: a. Highlight the application or, to delete multiple applications, mark them by pressing <F5>. b. Press <Delete>. ADMIN prompts for confirmation. c. Select "Yes" to delete the application(s). 2.5 Customizing the Basic MHS Server Configuration ---------------------------------------------- After you use Basic MHS for a while, you might want to customize the way your server operates. You might want to do so for the following reasons: * To improve message delivery time. By default, the Basic MHS server checks for messages every 45 seconds. If you find that messages are being delivered too slowly, you can configure the server to check more often. * To reduce demand on the file server. The more frequently the Basic MHS server delivers messages, updates the EXTRACT file, and resynchronizes the database files, the greater the demand on the file server's resources. To reduce the demand, you can schedule each of these activities less frequently. * To improve the reliability of the Basic MHS database. If you find that user information changes frequently, you might want to synchronize the database and EXTRACT files more often to ensure this information is available to your users. * To improve the reliability of the directory EXTRACT file. The EXTRACT file is a text representation of the Basic MHS database. Application programs can access the EXTRACT file to provide users with pop-up pick-lists. If the pick-lists are out-of-date, you might need to update the EXTRACT file more frequently. NOTE: Periodically, Basic MHS also compares the date stamp on the Basic MHS database to the date stamp on the EXTRACT file. If the date stamp for the EXTRACT file is earlier than the date stamp for the database, Basic MHS updates the EXTRACT file. * If you have been using sender validation, but a new application does not support it (or vice versa). To change your server configuration, select "Configuration" from the Admin Functions menu. The Configuration form appears. Complete the form. When you are finished, press <Esc> and select "Yes" to save the changes. The Configuration form contains the following fields. Deliver messages every (Required) Indicate how long, in seconds, your server will wait before checking for queued messages. After delivering all queued messages, your server waits the amount of time specified in this field before checking for queued messages again. Enter a number between 10 and 21,600 (6 hours). The default interval is 45 seconds. Perform NSYNC every (Required) Indicate how often, in minutes, your server will synchronize the database files. Enter a value from 10 to 10,080 (7 days). The default value is 1440 (24 hours). Update EXTRACT every (Required) Indicate how often, in minutes, your server will update the EXTRACT file. Enter a value from 10 to 10,080 (7 days). The default value is 1440 (24 hours). Force Sender Validation (Required) Enter "Yes" if you want to enable sender validation. If the Force Sender Validation field is set to "Yes", your server checks the sender's name in the message to ensure that the sender is defined in the Basic MHS database. If the sender is not, it rejects the message. If the sender is, your server checks the file ownership of the message, to ensure that the owner of the message matches the NetWare user ID of the sender. Enter "No" if you do not want to use sender validation. Some applications do not support sender validation; the documentation for your messaging application will let you know whether it does. The default value is No. 3 MANAGING FIRSTMAIL ------------------ This section discusses how to set up FirstMail for both DOS and Macintosh users. It includes the following sections: * Checking that All FirstMail Files Were Copied * Restricting User Accounts * File Naming Conventions * Setting Up FirstMail for DOS * Setting Up FirstMail for the Macintosh * Setting Up Bulletin Boards for DOS and Macintosh Users Setting up FirstMail is easy. When you install Basic MHS, the FirstMail files for both DOS and the Macintosh are automatically copied onto your server. FirstMail uses the NetWare-created user accounts. Therefore, you do not need to create any home mailboxes for FirstMail users. FirstMail also provides a default configuration (for both the DOS and the Macintosh versions) and stores this information in the NetWare bindery. The default values should be adequate for running FirstMail at most organizations. 3.1 Checking that All FirstMail Files Were Copied --------------------------------------------- After you finish installing Basic MHS, make sure the following FirstMail files were copied into the SYS:\PUBLIC directory on your server: * MAIL.EXE * MAIL.HLP * NEWMAIL.EXE * FMCONFIG.EXE * FREBUILD.EXE * README.FM * USER.TXT * MAC-MAIL.EXE (Contains Macintosh files) Before you start FirstMail, verify that the \MHS\EXE directory is in the NetWare search path. If you installed the MHS\MAIL\USERS subdirectory in a location other than the default location (that is, at the root of the SYS: volume), make sure the MV variable points to the volume and directory where MHS\MAIL\USERS is located. After you install FirstMail for Macintosh, make sure that the correct path to MHS\MAIL\USERS is specified in the FirstMail Config file. 3.2 Restricting User Accounts ------------------------- Everyone who has a NetWare user account on the file server can use FirstMail. FirstMail uses the directory structure that NetWare creates for each user in SYS:MAIL. FirstMail places each user's new mail and previously-read mail in SYS:MAIL\<userID>, where <userID> is the user's NetWare User ID number. If you want to restrict some users from accessing FirstMail, you can use SYSCON to do so. To restrict access, you must create either of the following NetWare user groups: * MAILUSERS - If you create this group, the members of the group are the only users who CAN run FirstMail. or * NOMAIL - If you create this group, the members of the group are the only users who CANNOT run FirstMail. Whether you choose to create the MAILUSERS or NOMAIL group depends on the number of users in each group. For easy maintenance, create the group that has the fewest members. If neither group exists, all users are granted access to FirstMail. 3.3 File Naming Conventions ----------------------- Both FirstMail for DOS and FirstMail for the Macintosh use the same file naming conventions. FirstMail recognizes mail and other FirstMail-generated files by the following extensions: .CNM New, unread mail (only found in SYS:MAIL) .PMR Address book .PM! Address book index .PMM Mail folder .PMI Mail folder index file .PMF File attachment .PML Distribution list .PMS Signature file .PMU Keystroke macro .PMX Mail session record .PMZ Scrapbook record file .MAI Public Mail folder (subdirectories only) To learn more about FirstMail for DOS, read Section 3.4 "Setting Up FirstMail for DOS"; to learn more about FirstMail for the Macintosh, read Section 3.5 "Setting Up FirstMail For the Macintosh." To help users learn how to use FirstMail, provide your DOS users with a copy of "Getting Started with FirstMail for DOS" and your Macintosh users with a copy of "Getting Started with FirstMail for the Macintosh," which are in the "Getting Started with Messaging" manual. A more detailed user guide is available for each of the FirstMail programs. Refer DOS users to the SYS:\PUBLIC\USER.TXT file. Refer Macintosh users to the files, FirstMail Manual 1,2,3, and 4, which are in the FirstMail folder that Macintosh users install on their Macintoshes. 3.4 Setting Up FirstMail for DOS ---------------------------- When you install Basic MHS, FirstMail for DOS is automatically installed in the SYS:\PUBLIC directory on your server. The following sections describe how to reconfigure and customize FirstMail for DOS. 3.4.1 Reconfiguring the Default Settings FirstMail for DOS provides the following default values, which are applied the first time users start FirstMail. The default values should be adequate for most organizations: Preferences - General Preferences: Personal name: <NetWare_fullname> NetWare SMF/MHS Settings: SMF/MHS username: <NetWare_login_name> (first 8 characters) SMF/MHS mailbox name: <NetWare_login_name>(first 8 characters) My application name: FIRST Scan the MHS user dir:Y Change Home mailbox location: <NetWare_user_mailbox> FirstMail Configuration Parameters - NetWare MHS/SMF Interface: Default Workgroup: None. Basic MHS appends it if it does not exist. SMF-71 available: Y MHS path for DOS: <MV_variable> 3.4.2 Changing Parameters with FMCONFIG If users are experiencing problems and you want to verify or change the default settings, use the FMCONFIG.EXE utility as follows: 1. Change to the \PUBLIC directory and enter: FMCONFIG 2. Select the option "NetWare MHS/SMF Interface" to verify the following settings: * Default work group - (Optional) Enter the default workgroup for this server. * Use SMFSEND? - Set to N. * SMF-71 available? - Set to Y. * UTC time value - Enter your offset from GMT in the form -nnnn (for example, -0800). * MHS path for DOS - Set to your MV variable. 3. When you finish, press <Ctrl+Enter> and press <Y> when prompted for confirmation. 4. Select "X" to exit and save your configurations. 3.4.3 Changing Parameters in DEFAULTS.PM You can also reset the default values for the following parameters by creating a text file called DEFAULTS.PM (in the same directory as MAIL.EXE) and entering any or all of the following keywords and parameters: HOMEBOX <path_name> COPYSELF <option_letter> SCRATCH <path_name> where: * HOMEBOX is the location of all users' home mailboxes, as specified during the Basic MHS installation. If you want to change this location, specify a <path_name> in either NetWare or DOS format, with no trailing backslash (\). The directory must exist; FirstMail does not create it. An easy way to create a subdirectory for each user in the directory <path_name> is to imbed the string ~8 in the path. At runtime, FirstMail replaces this string with the first eight characters in the user's name. * COPYSELF sets the copy-self option for all users. You can specify <option_letter> as either Y, P, or N. If you want all users to receive a copy of all messages they send, specify Y. If you want FirstMail to prompt users whether to keep a copy, specify P. Otherwise, specify N and no copies will be kept. * SCRATCH is the temporary work area for FirstMail. If you do not specify <path_name>, FirstMail first searches for a TMP or TEMP directory. (If a TMP or TEMP directory does not exist, Firstmail uses the current directory.) If you specify <path_name>, it must be a path to a directory where all users have write permission. An easy way to create an individual subdirectory in the directory <path_name> for each user is to imbed the string ~8 in the path. At runtime, FirstMail replaces this string with the first eight characters in the user's name. NOTE: Case is not significant. Unrecognized keywords are ignored without error message or warning. Lines starting with a semicolon, space, or tab are treated as comments. 3.4.4 Customizing FirstMail for DOS You can customize FirstMail for DOS in the following ways: * Modify the system login script to provide new mail notification * Force FirstMail to use a particular drive letter * Disable access to DOS from FirstMail Modifying the System Login Script for New Mail Notification: During login, FirstMail will notify users that they have new mail, if you add the following lines to the system login script: #newmail if "%ERROR_LEVEL" > "0" then begin write "" pause end If the user has unread messages, NEWMAIL returns a non-zero errorlevel value, equal to the number of unread messages, and displays this number in a message to the user. The write statement prints a blank line and pauses to give the user a chance to read the message. (NEWMAIL returns immediately whether or not the user has new mail.) Forcing FirstMail for DOS To Use A Particular Drive Letter: When a user runs FirstMail, FirstMail creates a NetWare directory mapping using the first available unused drive letter. You can force FirstMail to use a specific drive letter by setting the PMDRIVE environment variable in the system login script to the desired letter. For example, to use drive M, add the following line to the system login script: DOS SET PMDRIVE = "M" Disabling DOS Access: If, for security reasons, you want to prevent users from using the <Ctrl+F10> command to exit FirstMail and use FirstMail's DOS shell, create an empty file named NODOS in the same directory as MAIL.EXE. 3.4.5 Troubleshooting FirstMail for DOS PROBLEM: FirstMail may not display on some monochrome or black and white monitors. RESOLUTION: If a user has a monochrome or black and white monitor and is unable to display FirstMail, add one of the following lines to the user's AUTOEXEC.BAT file: SET MMMODE=B (if the user has a color graphics adapter card) MODE=BW80 (if the user has a monochrome adapter card) PROBLEM: FirstMail fails to find its help file or see system address books when running either MAIL or NEWMAIL from the login script. RESOLUTION: Different versions of the NetWare login utility, LOGIN.EXE, do not process the "#" command in the same way when running login scripts. Try specifying the filename in the login script in uppercase characters (for example, "#NEWMAIL") or as a full pathname (for example, "#f:\public\newmail" instead of "#newmail"). 3.5 Setting Up FirstMail For the Macintosh -------------------------------------- FirstMail uses the directory structure that NetWare creates for each user in SYS:MAIL. This relieves you from the task of creating a mailbox for each Macintosh user. Additionally, your mail system is secure because control of and access to the mail system is controlled using standard user groups created with SYSCON; users have, at most, [C] create rights in other users' mail directories. FirstMail stores its configuration information in the NetWare bindery, which also provides security for your mail system. By default, mail is stored in each user's subdirectory in SYS:MAIL. New mail is always delivered to this folder, even if a user moves the home mailbox. Users can customize the defaults for their own FirstMail programs, including the mailbox location. 3.5.1 System Requirements FirstMail for the Macintosh requires NetWare system software 3.01 or later to be running on the NetWare file server. The SYS: volume of your file server must have the Macintosh name space added, and Macintosh users must be able to see the PUBLIC, MAIL, and LOGIN directories. Users must have the default NetWare rights in SYS:MAIL (that is, [C] under NetWare 386). Macintosh system software 6.03 or later must be installed on each Macintosh that runs FirstMail. 3.5.2 Required Set Up Before Users Can Install FirstMail Files The Basic MHS installation process automatically installs the files for FirstMail for the Macintosh in the SYS:\PUBLIC directory. Before users of FirstMail for the Macintosh can install FirstMail files on their Macintosh computers, do the following: 1. Configure the NetWare server for Macintosh access. 2. Run the file MAC-MAIL.EXE. MAC-MAIL.EXE is an executable file that unloads the self-extracting archive file "Firstmai.sea" onto the NetWare server (DOS system). Macintosh users copy "Firstmai.sea", which contains the files for FirstMail for the Macintosh, to their Macintosh hard disk. 3. Test that FirstMail is working correctly on a Macintosh by installing the FirstMail files on a Macintosh and starting FirstMail. See Section 3.5.3 "Installing FirstMail Files on the Macintosh for more information. IMPORTANT: If you changed the location of the MHS\MAIL\USERS directory, you must change the parameter in the "FirstMail Config" file that contains the path to MHS\MAIL\USERS directory. See Section 3.5.4 "FirstMail Configuration File Parameters" for information about how to change the path to the MHS\MAIL\USERS directory. 3.5.3 Installing FirstMail Files on the Macintosh Macintosh users must copy the FirstMail files to their Macintosh hard disk drive before they can use FirstMail. Provide your Macintosh users with the section "Getting Started with FirstMail for the Macintosh" (which is in the manual "Getting Started with Messaging") or the instructions in this section. Perform the following procedure at your Macintosh to copy the FirstMail files from the NetWare file server to your Macintosh hard disk drive. During this procedure, the files are changed to Macintosh format. 1. Select the "Chooser" command from the Apple menu. 2. In the "Chooser" window, select the AppleTalk zone that is appropriate for your file server. 3. Click on the AppleShare icon. A list of available file servers appears in the right-hand side of the window. 4. Select your file server. A dialog box appears. 5. Select "Encrypted Netware authentication." A dialog box appears. 6. Enter your NetWare username and password (if you have one) for that server in the appropriate fields. A dialog box appears. 7. Select the appropriate server volume. 8. Close the "Chooser" window and look on the desktop to confirm that the icon for the server volume you selected appears. 9. Double-click on the server volume icon. A window opens that lists the folders (directories) on that server. 10. Open the PUBLIC folder. 11. Copy the file named "Firstmai.sea" to the hard disk drive of your Macintosh. You do not need to create a FirstMail folder before copying the "Firstmai.sea" file to your Macintosh. A FirstMail folder is automatically created in the next step. 12. Double-click on the file "Firstmai.sea," which is now on the Macintosh hard disk drive. Double-clicking on the file "Firstmai.sea" generates a new folder on the Macintosh that is called FirstMail1.0. This new folder contains all files for FirstMail for the Macintosh. If you want to start FirstMail now, double-click on the FirstMail application. If you will be using FirstMail later, you will need to establish the connection to the NetWare file server at that time, then start FirstMail by double-clicking on the FirstMail application. 3.5.4 FirstMail Configuration File Parameters This section shows the default values for the FirstMail configuration parameters; these parameters are in the "FirstMail Config" file. The FirstMail folder that is installed on each Macintosh contains the "FirstMail Config" file. The data in the "FirstMail Config" file is stored in the NetWare bindery. The default values in the "FirstMail Config" file should work for most Basic MHS servers. You need to access this file only in the following circumstances: * If you changed the location of the MHS\MAIL\USERS subdirectory (which contains user mailboxes). Enter the new path in the "Path to base of NetWare MHS/SMF directory tree" field. (The DOS version of FirstMail uses the MV variable to point to the volume and directory MHS\MAIL\USERS; FirstMail on the Macintosh has to locate this directory from the path entered in the "FirstMail Config" file.) * If FirstMail is not running correctly on your Macintosh. Check that the values for the other parameters in the file match the defaults shown in this section. You must install the FirstMail files on a Macintosh before you can open the "FirstMail Config" file. (You open this file on the Macintosh.) You must supply your Supervisor password to open this file. Save your changes and quit the "FirstMail Config" file when you are done. The default values for the configuration parameters in the "FirstMail Config" file are as follows: Parameter in the General Setup Command: "Path to base of NetWare MHS/SMF directory tree": The value for this field is the directory path for the MHS\MAIL\USERS directory. The default for this field is <Server>.sys, where <Server> is the NetWare name of the Basic MHS server. <Server>.sys points to root of the SYS: volume as the directory path for the MHS\MAIL\USERS directory. If you installed the MHS\MAIL\USERS subdirectory in a different volume than the SYS: volume, you must change the path in this field. Parameters in the NetWare MHS/SMF Setup Command "Are you using an SMF-71 transport?": The default value for this parameter is yes (checked). This field must be set to yes. "Default workgroup": This field is blank by default. Leave this parameter blank. 3.5.5 Troubleshooting FirstMail for the Macintosh By default, NetWare MHS grants all users [CF] rights to the mail submission directory <mv>/MHS/MAIL/SND. Under some versions of NetWare for Macintosh, this particular combination of rights appears to result in Macintosh users being unable to access the directory at all. If you encounter this problem, you must create two NetWare groups with access to <mv>\MHS\MAIL\SND. The first group should contain your DOS MHS users and should be granted [CF] rights to the directory. The second group should contain only your Macintosh users and should be granted [C] rights only. 3.6 Setting Up Bulletin Boards for DOS and Macintosh Users ------------------------------------------------------ You can create FirstMail bulletin boards that are available to both DOS and Macintosh users by following these steps: 1. Create a subdirectory in the PUBLIC directory. You can assign any name to this subdirectory, but it must have the extension ".MAI" (for example BBOARD.MAI). 2. In this subdirectory, create a file called PMFOLDER.ID. Enter the name of the bulletin board as you want it to appear in the "Select a folder" window in the DOS version and in the list of mail folders in the Macintosh version. For example, PMFOLDER.ID could contain the line: SUGGESTIONS AND COMPLAINTS. IMPORTANT: Do not press <Enter> after typing the folder name. If you do, "<RETURN>" will be displayed after the folder name in the "Select a folder" window. All users will be able to view the messages in this bulletin board folder; however, before users can move messages to the folder, you must assign them RWC rights to the bulletin board subdirectory. 4 DIRADM ------ The DIRADM program provides access to many of the MHS functions available in ADMIN. With DIRADM, you can define, modify, and delete users and distribution lists. This section describes the DIRADM program and the command line parameters available in the Basic MHS environment. 4.1 DIRADM Syntax ------------- The syntax for the DIRADM program varies depending on whether the command is being used for input (that is, to add or update entries in the MHS database), or for output (that is, to output all or part of the MHS database to a file). Before running DIRADM, you must load the Btrieve requestor on the workstation you will be using. Use the BREQUEST command. Input Syntax DIRADM -I <input_file> [-C<n>] [-L<n>] [-N <mail_path>] Section 4.2 "Input File Format," describes the format of the input file. The output file is in the same format as the input file, except that the Preamble contains a Date attribute. Output Syntax DIRADM -O [<output_file>] -U<user>|-D<dlist> [-B | -F] [-C<n>] [-L<n>] [-N<mail_path>] The following table describes the command-line parameters for the DIRADM command. -I Runs DIRADM in input mode. -O Runs DIRADM in output mode. If you do not specify an output file, DIRADM displays the output to the screen. -U<user> Name of user(s) to be extracted. The user name can include wildcard characters (*,?). For example, to extract all users, enter "-U *". -D<dlist> Name of distribution list(s) to be extracted. The distribution list name can include wildcard characters (*,?). For example, to extract the distribution lists NSales and SSales, enter "-D ?Sales". -B Generate brief format output. The output will contain only the names of the extracted records. -F Generate full format output. The output will contain all information for the extracted records. -C<n> The console display threshold for DIRADM, where n is a number from 1 to 9. Replace n with the highest message priority to be displayed on the console. All messages with a priority level up to and including n will be displayed. (The lower the priority level of a message, the more serious the message; messages with priority level 1 are more serious than messages with priority level 2.) -L<n> The logging threshold for DIRADM, where n is a number from 1 to 9. Replace n with the highest message priority to be written to the log file. All messages with a priority level up to and including n will be appended to the log file. (The lower the priority level of a message, the more serious the message; messages with priority level 1 are more serious than messages with priority level 2.) -N<mail_path> The path to the MAIL subdirectory (for example, \MHS\MAIL). If you omit this parameter, DIRADM uses the MAIL environment variable (if it is defined), or the MV environment variable to find the path. 4.2 Input File Format ----------------- The input file used by DIRADM has the following format. [Preamble] Origin = <server_long_name> Version = 1 Type = Update [User] (Create | Delete | Replace) SMF-Name = <name> SMF-Short-Name = <short_name> Description = <description> Mail-Server = <server> Bindery = <login_id> Dflt-Doc-Prf = <preference> FullName = <full name> Title = <title> Phone = <phone> Department = <department> Default-App = <application> App1 = <application1> App2 = <application2> App3 = <application3> App4 = <application4> Extra-Info = <extra_info> [D-List] (Create | Delete | Replace) SMF-Name = <name> SMF-Short-Name = <short_name> Description = <description> Owner = <address> Administrator = <administrator> Moderator = <moderator> Dead-Letters = <address> Email-Addr = <address> Mail-Server = <server> SUGGESTION: When you Replace an entry in the Input file elements, include all the attributes, including those that are not changed. The easiest way to do this is to output the entries you want to change, edit the output file, and use it as an input file. IMPORTANT: In the input file, elements in brackets ([ ]) are required. You can replace square brackets ([ ]) with braces ({ }). Do not use both brackets and braces in an input file. You can include comments in the input file. Each comment line must begin with a semicolon (;). [Preamble] Precedes setup information for DIRADM. All input files must have a [Preamble] section. The Preamble contains the following attributes: Origin Name of the local messaging server. Version The current CMP version. Enter 1. Type The type of processing. Enter Update. [User] Precedes a user entry. You must indicate whether the entry is to be created, deleted, or replaced. A user has the following attributes: SMF-Name Name of the user, including the workgroup.This is the only attribute required for a Delete operation. SMF-Short-Name Short name of the user. Enter up to 8 characters, including letters, numbers, and the following special characters: -, &, #. Description A description of the user. Mail-Server The long name of the messaging server on which this user account is located. Bindery The user's NetWare login ID. Dflt-Doc-Prf Document preference of this user. The value can be up to eight characters long. FullName Full name of the user. Enter the FullName in the following format: surname, given-name middle-name/initial, generation-qualifier. For example, "Smith, John D., Sr." Title Job title of the user. Enter up to 24 characters. Phone Business phone number of the user. Enter up to 29 characters. Department Department or division to which the user belongs. Enter up to 24 characters. Default-App The user's default application. Messages will be delivered to the user's default application, unless the sending application specifically requests delivery to another application. App Up to four other applications used by the user. Extra-Info Extra information about the user. Enter up to 253 characters. An input file can contain multiple user entries. [D-List] Precedes a distribution list entry. You must indicate whether the list is to be created, deleted, or replaced. A distribution list has the following attributes: SMF-Name Name of the distribution list, including the workgroup long name.This is the only attribute required for a Delete operation. SMF-Short-Name Short name of the distribution list. Enter up to 8 characters, including letters, numbers, and the following special characters: -, &, #. Description A description of the distribution list. Mail-Server The long name of the messaging server on which this distribution list is defined. Owner Address of the user who owns this distribution list. Administrator The user who is authorized to add members to and delete members from the distribution list. Moderator The user who determines whether messages intended for a distribution list can be sent to it. Dead-Letters The address to which notification messages for a distribution list are sent. Email-Addr Address of the distribution list member, including the workgroup. To delete or rename an entry, enter this attribute only. An input file can contain multiple distribution list entries. A distribution list entry can contain multiple Email-Addr attributes. 4.3 Example Input File ------------------ [Preamble] Origin = LA-Bldg1 Version = 1 Type = Update ; adding a user [User] (Create) Name = Mary Adams SMF-Short-Name = MAdams Bindery = MAdams FullName = Adams, Mary S. Title = Sales Representative Department = Los Angeles Sales ; defining John, Leonard, and Jane as members of ; Managers list [D-List] (Replace) SMF-Name = Managers Email-Addr = John Smith@Acme Email-Addr = Leonard Morton@Acme Email-Addr = Jane Dixon@Acme NOTE: When you add users to a distribution list, you replace the existing list with the new list. Therefore, you must list both the new list members and the old list members. 5 MHSUSER ------- The MHSUSER program provides access to some of the functions available through ADMIN. With MHSUSER, you can assign applications to users, remove applications from users, and register and delete applications. This section describes the MHSUSER program and the functions available in the Basic MHS environment. NOTE: MHSUSER is included for compatibility with previous releases of NetWare MHS. It will become obsolete in a future release. All the MHSUSER functions (X-functions) have the same general syntax, as shown in the following sample command: MHSUSER -X<nn> <switches> The following table provides the syntax of the X-functions available in a Basic MHS environment. Displays the local messaging server configuration -X00 [-D<directory>] [-V] Adds or changes a user's application -X01 -A<application_name> -U<username> [-D<directory>] [-E<description>] [-O<owner>] [-V] [-Y] Deletes a user's application -X02 -A<application_name> -U<username> [-D<directory>] [-V] Lists a user's applications -X03 [-A<application_name>] [-D<directory>] [-U<username>] [-V] Verifies a user's application -X04 -U<username> [-A<application_name>] [-D<directory>] [-V] Registers an application, or changes an application's registration -X10 -A<application_name> -E<description> [-C<MHS_version>] [-D<directory>] [-M<maximum_number_users>] [-V] Deletes an application -X11 -A<application_name> [-D<directory>] [-V] Verifies the MHS Administrator -X62 -U<username> [-D<directory>] [-V] The following table lists the command-line switches for the MHSUSER command. -A<application_ name> Name of the application. Maximum length is eight characters. -C<MHS_version> Compatible version of MHS. Valid values are 70 and 71. -D<directory> The directory specified by the DOS environment variable MV, which is the parent directory of the MHS directory. -E<description> Up to 24 characters describing the application. This description need not match any previous description used. -M<maximum_number_users> Number of users for a managed application. This limits the number of users who can access a managed application to the number specified. -O<owner> NetWare bindery account to which rights will be assigned. If you omit this parameter, MHSUSER attempts to assign rights to a NetWare user whose name is specified with the -U parameter. If the username specified by the -U parameter is not a valid login name, the new user will not be defined. -U<username> The specified username. If the application is a managed one, MHSUSER adds the application name to the user's list of Other Applications. If the application is an unmanaged one, the application name will not appear in the user's list of applications. -V Display error report. You can redirect this information to a disk file or other DOS device using the DOS redirection command (>). -Y<use> Specify how a user can use an application being defined. If you omit this switch, and the application is an unmanaged application, then you must add a directory for the user of this application. If the application is managed, then you must define the application as Other Applications. If you have used all the four available Other Applications, then this switch fails. You can give the following values for use: 0 Add the application as preferred, and change the order of the existing applications by placing them after the preferred application. During this process, you can remove any empty application entries. If the user already has 5 applications, or the application that you specified is unmanaged, then this function fails. 1 Add the application as the first available, free, managed application for the user. If the user already has 5 applications, or the application that you specified is unmanaged, then this function fails.