ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / MISC / NETWORK / PMAIL224.ZIP / GUIDE.EXE (.txt) < prev next >

Wrap

David's Readme Compiler Executable | 1992-01-25 | 80.7 KB | 1,073 lines

>V r" H9D0} G H I O P Q v YYG;> LLVW3 0RY_^ <Ar ,@ _^_^] YYF;v ;Dz~ '2(2((( (2(?(!(U H I K M P Q0. DF_^] YY9|,uK ;D@ui ;DDu2 H9D0~ 9D<| u Y;D2v H9D0u YY_^] YY_^] Y;D2wK t0Nt- !r.RP !r$RP u/SQR [C[J[O[ Zx[V[Z[^[ \D\d\ [[XP3 Turbo C++ - Copyright 1990 Borland Intl. Null pointer assignment Divide error Abnormal program termination %-50.50s Print this section Ready printer and press a key (ESC to cancel) ---- Printing ---- PgUp/Dn: =print Line %d of %d Readme error: no attached data. Topics MMMODE ; < = > ? @ A B C D T U V W X Y Z [ \ ] G O w u R S s t EAEIIOOUUYIOU Insert paper in printer then press a key (<ESC> cancels print) Printer error The printer on LPT%d: is confused out of paper off line Correct then press a key or hit <ESC> to cancel print Insert Paper <ESC> key pressed: Please confirm cancel/quit Accept this data? Insufficient disk space There is not enough space on the target disk to receive the file(s): please replace the disk with another formatted disk, then press any key to retry, or <ESC> to cancel !!!!! @@@@@@@@@@@@@@@ @@@@@@@ @@@@@@ @@@@ (E(E(E (null) Data file generated by RCOM. Pegasus Mail version 2.2 guide IMPORTANT info for current users Information about Pegasus Mail New features in Pmail 2.2 Installing Pegasus Mail PMIMPORT - importing addresses Other utilities supplied Ordering Pmail manuals Finding the Pmail version Sites using Pmail 2.1c Sites using Pmail 2.2 (R2) Sites using Pmail 2.2 (R3) Converting system address books About Pegasus Mail Contacting the author The Charon SMTP Gateway Acknowledgments Pegasus Mail Source Code About this guide... Spelling checker New address book format and aliases Multiple attachments to messages Keystroke macros New mail filtering rules File-based mail folders Deleted message tracking User-defined mail gateways New control groups Other changes and features System requirements Installing Pegasus Mail TEMP and TMP variables Modifying NET$LOG.DAT Enabling extended options for users Enabling delivery between servers Enabling SMTP mail via Charon Novell MHS and Pmail Installing Pmail for use with MHS User-settable MHS options Personal names and MHS Recommendations for installation How Pmail interacts with MHS Notes on this release What is PMIMPORT? How to use PMIMPORT Tagged import/export format Sample input file PMGRANT.EXE PMAIL.ICO/.PIF MAILDIR.EXE Pegasus Mail Manuals Ordering manuals Orders from Europe Upgrading existing manuals Pegasus Mail Manuals - Order Form You can find out what version of Pegasus Mail you are using at any time while the program is running by pressing <Alt-A> For what it's worth, the snake's name is Sammy If you currently use Pegasus Mail, please note that you install PCONVERT.EXE in the same directory as PMAIL.EXE for the new version to operate. This is essential!! Users must have sufficient free space on the drive where their home mailbox is located prior to running PCONVERT. They will require 150% of the total size of their current mailbox free, although this is a one-off requirement during conversion, and the surplus can be revoked when the process is complete. PCONVERT does NOT handle out-of-disk conditions gracefully! Please note also that the spelling dictionary files (PMDICT.PMD, COMMON.PMD, and PMDICT.NDX) must be installed in the same directory as PMAIL.EXE if you want to use Pmail 2.2's spell-checker. Pmail 2.2 (R3) is what I consider the official release version of Pmail 2.2. It is the first release to be made outside one or two selected sites. (R3) fixes the following problems in (R2): Autoforwarding from Local to Internet mail now works. One or two windows not closing correctly and trashing the screen have been corrected. Errors in sorting by date have been corrected. Note that this fix will not show in mailboxes which have already been converted. Sending ASCII files now works again - a message is generated for each ASCII file instead of a file transfer. You can mix ASCII and non-ASCII transfers in the same batch. Problems with high bits being stripped from messages when mailing from the command line have been fixed. (R3) also adds a couple of "finishing touches": When printing, headers are now tidied if you have this option set (toggled using 'H' in the message reader). Sites using MHS will find that the <F2> key will now list local MHS addresses as well as local NetWare usercodes. Pmail 2.2 (R4) stabilises (R3). Several small bugs have been fixed, and one significant change made: In previous versions of Pmail, you COULD NOT edit system address books from within Pmail. (R4) explicitly allows you to do so, provided the book has fewer than 1500 entries. In fact, if you have system address books created using an earlier version of Pmail 2.2, you open them from within Pmail to build the new index structure. Until you do this, users will NOT be able to access the book! Alternatively, you can import and export the book using PMIMPORT - this will also build the index. Pmail 2.2 sorts address books by KEY, but has a new option in the address book manager to allow you to choose to sort by name as well. Speed search will work on whatever you are currently sorting by - so if you are sorting by key, then speed search will work on the key field. You can convert any system address books you created for Pmail 2.1c or earlier by issuing the command: PCONVERT <filename> <filename> is the name of the system address book and can include a full path specification in either DOS or NetWare filename format. Welcome to Pegasus Mail, v2.2 Pegasus Mail is an electronic mail system for use with Novell NetWare (versions 2.15A and later): it is a fully-fledged mailer, one of its more unusual characteristics being that it is free - not shareware, but free. You can use it without charge, restriction or obligation on as many servers as you wish. I do sell manuals for the program, in order to support development costs, but manual purchases are strictly optional. An order form for manuals is provided in this guide - please print it out and attach it to your order form or cheque if you place an order. Pegasus Mail requires DOS 3.0 or later and 384KB RAM on the DOS workstation to run, and runs fine from within MS-Windows (a Windows version is planned for future release). A Windows .PIF file and Icon is provided with this release. Pegasus Mail has been tested under NetWare 2.12, NetWare 2.15A-C, NetWare 386 3.0, 3.1 and 3.11. It will run on any station equipped with any version of IPX and NETx, on any network topology. I give Pmail away for a number of reasons, very few of them logical. One of the main reasons, however, is the intense satisfaction I get from knowing that people like using it. I am very receptive to comments and criticisms about Pmail, and intend to support it for as long as people want to use it. The best way to reach me is by e-mail: if you have access to the Internet, my address is david@otago.ac.nz. From CompuServe, you can mail to me as >internet:david@otago.ac.nz. I am not currently addressable via MHS, but hope to be in the future. If you wish, you can fax me at either (+64) 3 453 6612 or (+64) 3 479 8577. I can be phoned at (+64) 3 453 6880, but please remember that New Zealand is GMT+1200... I am generally pretty grumpy about being woken at 4am by ANYONE! Because of the volume of information I have to deal with, faxing me, or sending me paper mail will generally not elicit a fast response - I apologise in advance for this, but there's only so much one person can do. My postal address is: Pegasus Mail, c/- David Harris, P.O. Box 5451, Dunedin, New Zealand. Pegasus Mail can talk to UNIX and other TCP/IP based hosts via the Charon SMTP gateway from Clarkson University. Developed by Brad Clements , and a product of Clarkson University, Charon is a dedicated server which can service mail on up to 8 NetWare servers simultaneously. Pmail and Charon were developed with each other in mind, and work very well together. Interaction is via NetWare Print Queues, which makes for easy management (using the NetWare PCONSOLE utility). Charon uses Packet Drivers to talk both TCP/IP and IPX at the same time, and requires the use of MX entries on a BIND/DNS system to operate to best effect. It supports aliasing, has a Finger server, and supports remote management via Telnet. Charon is available via anonymous FTP from omnigate.clarkson.edu (128.153.4.1) in /pub/cutcp/charon-3.0/charon.zip. Charon is free software. Pegasus Mail has been in widespread use since June 1990. Since that time, various people have had a significant influence on its growth and acceptance in the e-mail community. The following list is by no means complete, and I apologise to anyone whose name I have missed - it is not for lack of appreciation, believe me! Brad Clements , Clarkson University, for working hard and without much thanks on the excellent Charon 3.x SMTP gateway which Pmail knows how to use. Brad's ongoing influence on Pmail is beyond estimation. Wyatt Barbee and Jon Fujiwara , for maintaining the users group, and for keeping the Splicer FTP server running. Janet Perry, Manoj Goel and Lou Leporace from Novell Inc, who have helped in many, many ways. Steve Dart, Ton Roovers, Douwe Fokkinga, Steve Yoman, Dave Lange, Brendan Boerner, John Baird and the other people who helped test the system (and put up with all the headaches!). And to all the sites who have purchased manuals: this financial support has been critical in allowing me to continue supporting and enhancing Pegasus Mail. I have never previously released Pegasus Mail source code, for a number of reasons, including: The desire to ensure that exactly one, consistent product is available on the market, rather than hordes of variants. Human nature: so much of me has become tied up in Pegasus Mail that I have become extremely jealous and possessive of it. I recognise, however, that many sites may be concerned about ongoing support and the possibility of maintenance in the event of my ceasing to support Pmail for whatever reason (I stress the unlikeliness of this). In an attempt to accommodate these sites, I have attempted to devise a licensing agreement which could allow them access to the source code. Unfortunately, because of the nature of US Law, it has not been possible to find an enforceable non-disclosure agreement which would permit such a license. The costs of enforcing a breach are beyond anything which might be remotely considered reasonable. As a result, it is not possible for me to consider releasing source code at this stage. Blame the rapacity of the legal profession! This user guide was created entirely using another of my programs, called David's Readme Compiler (DRC). DRC allows you to take a simple text file and "compile" it into a single .EXE file which you can include with your program. This reduces the number of files you need to supply. DRC allows you to create hierarchical sub-topics nested arbitrarily deeply and to control text attributes and colour. It also has a mode which leaves the screen undisturbed, so you can run it as a help system from inside other programs. DRC is totally free , no catches, gotchas or gimmes. You can get it via anonymous FTP from risc.ua.edu in /pub/network/pegasus/drc.zip. Drc.zip can also be found at splicer.cba.hawaii.edu in the directory /files/pegasus. I hope to make it available on CompuServe when I get the time. Pmail 2.2 incorporates a 60,000 word spelling checker which can be invoked in any editor within Pmail. The dictionaries provided with the distribution are currently only a UK-English version: a US English version (you know, where all the words are misspelt, like "color"... hey, I'm kidding - really!) will be available in Feb. or March 1991. To invoke the spelling checker, move the cursor to the point in the message or file at which you want spell checking to start, then press <^KL> (this combination can be remapped using PMKB, of course). The screen will split, and Pmail will check each word. When it encounters a word not in any of its dictionaries, it will show it to you in context and allow you to alter it. You can also add the word to your user dictionary, or ignore the word. Pmail can offer suggestions for the correct word, although at this stage the facility is rather limited (it will offer no valid suggestions if any of the first three letters is wrong). The address book format in Pmail 2.2 is radically different from the one in previous versions. Existing address books will be converted to the new format the first time you run Pmail 2.2. The new format keeps much more information about addressees, including postal and delivery addresses, phone and fax numbers and so on. As well, the name field in the new address book can be used as an alias for a user. This means that you can create an entry for "Joe Bloggs" then enter "Joe Bloggs" in the TO field of a message. Pmail will automatically lookup the name at the time it sends the message, and use the address it finds in the address book entry. Large system address books will load almost instantaneously under Pmail 2.2, although screen update may be a little slower. Large personal address books (> 75 entries) will take a while to sort, insert and delete entries. Pmail 2.2 allows you to send up to 64 files with one message. The "send a File" option on the main menu is familiar except that now there is a list in the window. Enter an addressee and a subject, then press <Ins> to add files to the list. You can use wildcard characters (* and ?) in filenames to select several at once. You can send files from any mixture of directories. Setting "ASCII file?" to Y will stop Pmail from applying UUENCODING to the file if it is sent via an SMTP system. The new attachment scheme is upwardly compatible with messages sent using previous versions of Pmail - no conversion of your old messages is needed. As well, problems sending the same file several times which existed in previous versions have been eliminated. Attachment handling should be much more reliable under v2.2. Pmail 2.2 allows you to record macros, or sequences of keystrokes, which you can then playback later. Macro size is limited only by available disk space. To define a macro , press <Alt-U> then any other key on the keyboard - this key will be the activator for the macro. A small window will open asking for a descriptive name for the macro - this is used later if Pmail needs to list the macros available. You do not have to enter anything here, but if you intend to use the macro repeatedly, it's worth going to the trouble of choosing a meaningful name. Now, Pmail is recording every keystroke you press: do whatever you need, then press <Alt-U> again to end macro definition. To play a macro back , press <Ctrl-U> then the activation key you gave when defining the macro. Pmail will play back every key in the macro quite literally. If you pause longer than 1.5 seconds between the ^U and the activation character, Pmail will offer you a list of the macros available for you to choose from. Stop codes : you can make a macro pause at particular places during playback by pressing <Alt-P> while defining the macro, at the place you want the macro to pause. Definition pauses, and you can type anything you like until you press <Alt-P> again. When playing back, the macro will pause at the <Alt-P> and allow the user to type anything necessary, until <Alt-P> is again pressed, whereupon the macro will start playing again. Stop codes are useful for generating forms, or for pausing to allow a particular field to be entered. System macros : you can create system macros by copying the macro file (identifiable by the .PMU extension) into the same directory as PMAIL.EXE. WARNING: do NOT change the name of the macro, since it is what Pmail uses to tie the key pressed to the macro file. A new preferences option has been added which allows you to automate the processing of your new mail. You can define rules which Pmail will apply to each new message. Rules are of the general form: If these fields contain this, then do this. The fields you can select on are any or all of To:, From:, CC:, Subject: or Reply-to:. The possible actions are Copy, Move, Delete, Print, Forward, Extract or Append. You can define multiple rules for the same contents, which allows you to forward a message, then copy it to another folder, then delete it. Rules are applied strictly in sequence. Once a message is deleted or moved, no further rules will be applied to it. Earlier versions of Pmail stored messages as files in subdirectories: Pmail 2.2 uses single files as folders, much like archives in previous versions. This has a number of important effects: Much less disk space is occupied by messages: for instance, in a site with 100 users each with 100 messages, you would expect to save nearly 20MB in disk space. Many fewer directory entries are used on the server: this is very important in NetWare 2.x systems. Folders load vastly faster than they did in previous versions: a folder which previously took 25 seconds to load (372 message) now takes 2 seconds. Archives are obsolete: in fact, PCONVERT will convert archives to folders automatically. This simplifies the user interface. A new preferences option (under General Preferences) allows you to tell Pmail to save deleted messages temporarily to a special system folder called "Deleted messages". You do not need to create this folder - Pmail will create it when it needs to. All messages deleted during a session will be moved to this folder: when you exit from Pmail, the folder and its contents will be deleted automatically, and permanently. Up until you exit, you can browse the "Deleted messages" folder like any other, moving messages to other folders if you wish - effectively "undeleting" them. Under Pmail 2.2, you can define your own mail transports (for instance, UUCP) and tell Pmail how to interact with them. This allows sites with specialised mail needs to develop their own gateways to them. It is also necessary if you want to run Pmail on a non-NetWare LAN, or standalone (not quite implemented yet). User-defined gateways are accessed in Pmail using the NetWare-style SERVER/USER notation, except that the gateway name replaces the server name. USER can be any address valid to the gateway. To define a gateway, run PCONFIG and choose "create a User-defined gateway" from the main menu. A list, not unlike the server access list, will appear showing any gateways you have defined. Press <Ins> to define a new gateway, or select an existing one and press <Enter> to edit it. Gateway name: This is the name by which users will know this gateway. It should follow legal NetWare naming rules, and cannot contain spaces. New mail path: This is either a full path to a location where Pmail is to find new mail, or else the name of a program to run when checking for new mail. You can enclose the placeholder in the string to represent the first eight characters of the user's name, but the placeholder can be absent if you wish. Note that Pmail will assume that ALL mail in this directory is for the current user - it will not search among messages for various users. If your transport places new mail in the mail directory each user has in SYS:MAIL, using a .CNM file extension, then you do not need to enter anything in this field. Is ^ a program to run? Enter 'Y' if "New mail path" is a program name rather than a directory name. Gateways which require a program to be run to retrieve new mail will not be polled periodically - rather, the "check for New mail" option will remain permanently on the main menu, and the program will only be run when that option is selected. New mail search mask: This is a DOS filename pattern which Pmail is to use when searching the New mail path for new mail. New mail messages will be rewritten in the user's home mailbox using the normal Pmail naming convention prior to reading, but they need not be in this format as written by the gateway. Outgoing mail path: The name of the directory in which Pmail should create outgoing mail messages. Again, you can use the placeholder in this string to indicate that the first 8 characters of the user's name be substituted. Run for outgoing mail: If you enter a program name in this field, Pmail will run it every time it sends new mail to the gateway. The program must not interfere with the screen. If you place the special string anywhere in this field, Pmail will substitute the name of the output message file it has created. This allows you to pass the name of the message to your gateway process. Filename format: This field allows you some control over the file- names Pmail will use when creating outgoing messages. You can specify any string you wish, and may use the placeholder %d up to two times in the string. Each %d will result in a substitution of four random hexadecimal digits. Run to validate address: You can provide a program which Pmail will call to validate that an address is correct. If you do so, enter it in this field. The program will be called with the address on the command line, must not disturb the screen, and must return 0 if the address is invalid, or non-zero if the address is OK. If nothing is entered in this field, no attempt will be made to validate addresses. Accepts SMTP addresses: If your gateway accepts messages using standard internet address formats, set this flag to 'Y'. If Charon is not installed on your system and a user enters a standard internet address, Pmail will examine all available gateways, and will pass the message to the first with this flag set. This allows users to send internet mail using normal addressing, rather than having to send it specifically via a gateway using the SERVER/ADDRESS format. Simple message headers: Pmail can write messages with extra pre- parsed address information at the beginning of the message. This information is line-based, using line number as a key. Gateways which read simple message headers must read until a totally blank line is encountered, then send the remainder of the message, which will be normally formatted. At present, two lines are defined in the simple headers, although others will certainly be added: Line 1: The recipient of this message (not necessarily the same as the To: field) Line 2: Contains 'Y' if this message has attachments. Lines without values will contain a single space. Addresses are already parsed. Since the format is intended to be extensible, gateways which understand simple headers must ignore lines they are not written to use, and must read until the blank line. UUencode attachments: If 'Y', then Pmail will generate a separate message for each attachment, and will uuencode the attachment into the message. If 'N', a file with the same name as the message but the extension '.ATT' will be written into the outgoing mail directory, along with the attachments. The .ATT file will contain the names of the attachments to the message, one per line. **** Pmail 2.2 (R4) ONLY supports uuencoded attachments. Burst messages? If 'Y', then Pmail will create one message for every address sent to. If 'N', Pmail assumes that your gateway can parse the message for address information, and will write all the addresses into one message, using standard RFC-822 folding and header rules. **** Pmail 2.2 (R4) ALWAYS bursts messages at this stage. Check new mail every X seconds: [Only applies to gateways where "New mail path" is not a program] specifies how often Pmail should check the New mail path for new mail. This value is a minimum length of time - Pmail may check less frequently than the value specified, but will never check more frequently. Messages written to User-defined gateways are always written in RFC-822 format. Supervisors now have two more NetWare groups which they can define to control user behaviour in Pmail: MAILBOX If this group exists, only its members will be allowed to have home mailboxes on the file server. If the group does not exist, all users are assumed to be allowed to have home mailboxes on the server. NOMAILBOX If this group exists, its users will NOT be be permitted to have a home mailbox on the server. This new feature is dedicated to Mert Nickerson. Other new features or changes in Pmail 2.2: When sorting messages by subject, any "Re:" is ignored. Pmail can now be made to ask before moving new mail which has been read but not filed into the main folder. Copyself messages now show as "To: recipient" in the browser, but the headers are correct in the message. Pmail now recognises and honours a number of quasi-standard requests for confirmation of delivery in SMTP messages. MHS message bursting: MHS only allows 64 addresses per mail message, whereas Pmail distribution lists can have thousands. Pmail will automatically "burst" long lists into multiple transmissions for MHS. A new option exists for copy-to-self: when it is set, Pmail will always ask you if you want to copy to self when you send a message, regardless of the state of the header flag. Vastly improved error handling: Pmail now generates much more explicit and complete error messages. When sending a local receipt confirmation, Pmail now generates a different broadcast message to indicate that the delivery is a confirmation rather than new mail. The Userlist key (<F2>) now lists MHS users if MHS is enabled. Message headers are now tidied when printing. Pegasus Mail requires Novell NetWare ELS-I, ELS-II, 2.15C (Advanced or SFT) or NetWare 386. Some sites with NetWare 2.12 have reported no problems using Pmail, but the author has been unable to test it on that version. Pegasus Mail needs a minimum of 320Kb on the work- station to run. It is essential that the default NetWare file structure on volume SYS: exists, specifically the NetWare-defined user mail directories under SYS:MAIL. Since NetWare creates these directories automatically, this requirement is usually self- fulfilling. If you intend to use Pegasus Mail with Novell MHS, you must use MHS version 1.5 or later. Pmail will not work with earlier versions. To install Pegasus Mail, copy the files pmail.exe, newmail.exe and pegasus.hlp to a publicly-accessible directory on your network file server. If you are currently using an earlier version of Pmail you MUST also install the file pconvert.exe in the same directory. Note that Pegasus.hlp and Pmail.exe must be in the same directory, or Pmail will not be able to locate its help. Newmail.exe can be placed elsewhere if you wish. Pconfig.exe is usable only by supervisor- equivalent users, and should be kept away from public access. *** IMPORTANT *** If you are currently using an earlier version of Pegasus Mail, MAKE SURE that you delete any copies of Pegasus.hlp from that version: Pmail cannot distinguish between versions of the help file, and the help will be erroneous if an older version is located in the system and used. Existing users can use the program immediately. There are no extra steps required when creating users to allow them to use the system - Pmail learns all it needs about the user from the NetWare Bindery. Some operations in Pmail (notably the use of an external editor, and the DOS command in the browser) require the creation of temporary files. Pmail will attempt to create the temporary files in the following order: If the user has defined a scratch area in his editor preferences, then that directory will be used. If Pmail can find a TMP or TEMP environment variable, it will use the directory specified. If it can find neither of the above, it will try to create the file in the current directory. The last situation can create problems if the current directory is one in which the user has insufficient rights. I recommend that you have your users set a TMP or TEMP variable prior to running Pegasus Mail. You should modify NET$LOG.DAT, the NetWare system login script, on the host server to contain commands similar to the following: #newmail if "%ERROR_LEVEL" > "0" then begin write "" pause end This invokes the Pegasus Mail newmail utility, which reports the number of unread messages the user has when he logs in. The write statement prints a blank line, while the pause statement gives the user a chance to see the message printed by newmail. Newmail will check for new mail on all servers to which you are attached and logged in. SUPERVISOR-equivalent users can check for mail for other users on the default server by entering "newmail USERNAME". Some features in Pegasus Mail are only available if the user has been authorised to use them. These are: Autoforwarding, mail disable, notification disable, and denial of receipt confirmation. Because granting these rights requires the creation of a property in the NetWare bindery, they must be explicitly granted by a SUPERVISOR-equivalent user. You can control whether or not a user can modify these settings as well. To grant extended options to a user, either use PCONFIG, selecting "Grant extended feature rights", or else use PMGRANT.EXE, which allows you to use wildcard characters. Pegasus Mail can deliver mail to users on other file servers if access codes are provided. When a user attempts to send mail to a user on a remote server, Pegasus Mail searches a Supervisor-defined internal table for a usercode and password on the remote server. If one is found, the system uses it to log into the remote server and deliver the message. If none is found, the system attempts to log into the remote server as the NetWare GUEST user. If all attempts fail, an error is reported to the user. To define the access information Pegasus Mail needs for remote servers, the Supervisor or a Supervisor-equivalent user should run the pconfig.exe program on the distribution disk. Pconfig presents a menu offering `Interface definition' (this option is covered later) and `Server Access definition'. Select the latter, and a window will open. If you press <Enter> while the `Add a server' entry is high- lighted, another window will open prompting you for information about the remote host. You should enter the file server's name, and a usercode and password Pegasus Mail can use on that server. The data is stored in a heavily- encrypted format which should be secure from even an ardent hacker. You can create any number of entries for remote server access the list will scroll when you have filled the window. When you have finished defining servers, press <Ctrl-Enter> to accept the definitions and return to the main menu. Choose `Save and Exit' to store the definitions. The usercode you create for mail access should be extremely limited. I recommend that it NOT be a member of group EVERYONE, and that it should have only one explicit trustee right granted to it [C] (or [CW] under NetWare 286) rights in SYS:MAIL. Pegasus Mail does not need access to any other directory on the host server, nor does it need access to any NetWare utilities. Pegasus Mail logs into the remote server for the shortest possible time to deliver mail or examine usernames, and guarantees that the user will never be left logged-in to the remote host under the mail usercode. Note: if a mail usercode on a remote server has an expired password, Pegasus Mail will fail when delivering the message, even if grace logins are enabled and plentifully available. Pegasus Mail 2.2 supports the Charon v3 SMTP gateway by Brad Clements of Clarkson University. To install Pegasus Mail to use this gateway, run the Pconfig program supplied and choose `define Clarkson interfaces': a dialog window will appear. You must provide the following information: Queue name : this is the name of the print queue you have created (using the NetWare PConsole utility) from which Charon expects to retrieve messages. The queue need not exist at the time you define the interface. Use always : enter `Y' if you want Pegasus Mail to use the gateway for all messages, including mail to other servers. If you select `N', Pegasus Mail will only pass mail with Internet addresses to the gateway, and will use its own mechanism for all other messages. Server's internet name : Enter here the internet identity you have defined for this file server. Note that this is NOT the same as the name of the gateway itself. This address is used to form the sender's address for replies. For more information on naming, see the Charon manual. The name you enter in this field should be fully domain extended - that is, you should include the domain as well as the host name. Our time zone : Type here the UNIX-format abbreviation for your time zone: this is required by the RFC822 standard for message format. Examples of time zones are: EDT, PST, GMT, GMT+1200. When you have filled in all the blanks, accept the data. That's all there is to it! Pmail has native support for Novell MHS version 1.5 and later. To enable MHS support, run PCONFIG (you must be a SUPERVISOR- equivalent user to do this), and choose "Define Novell MHS interface" from the main menu. A window will open, presenting the following editable fields: Enabled: If 'Y', this field indicates that MHS mail capability is available on this server. If 'N', Pmail will generate an error message if a user attempts to enter an MHS address. Preferred: This flag only has meaning if the Charon SMTP gateway is also installed on the current system. Some MHS and SMTP addresses are indistinguishable from each other (canonical MHS addresses are ALWAYS correctly sensed): if such an address is detected by Pmail, it will be routed to whichever transport has its "preferred" flag set. If NEITHER transport has its preferred flag set, then the user will be asked to use an explicit override (either MHS: for MHS addresses, or IN: for SMTP addresses). Use always? If set to 'Y', then all messages will be routed to MHS irrespective of apparent address format. Pmail will rewrite addresses without workgroup parts, using the name defined for this host (so, a message addressed to "david" will be rewritten as "david @ hostname"). Pmail will not use its own local delivery agent, and messages to the Charon SMTP gateway (if present) will have to be overridden always (using the IN: prefix). NOTE: Hardened MHS users may instinctively wish to set this field to 'Y', but in general, Pmail will perform better if it is set to 'N', since its own delivery agent is extremely efficient. We recommend that this field be set to 'Y' only in an extremely heavy MHS environment - ie, one where a number of MHS mailers are used, to the exclusion of all other protocols. This host's name: This is the name of the local host/workgroup as defined in the installation of MHS on the current server. Pmail uses this name to construct the "From:" field of messages, and when rewriting addresses to MHS format. Native: Currently, this value MUST be set to 'Y'. Pmail can operate in two MHS modes - native, and gateway. In Native mode, Pmail will periodically scan and retrieve new mail from the MV/MHS/MAIL/USERS/USERNAME/APPNAME directory, and will behave in every way like a native MHS mailer. In gateway mode, Pmail will send mail as a native mailer, but will require a gateway to process incoming mail (ie, it will never scan the MV/.../APPNAME directory). The gateway process has some efficiency gains for sites who ONLY use MHS as a means of communicating with remote systems. It will also potentially allow other mail systems to send mail via the Charon SMTP gateway. Its main advantage is that the excessive number of directories created by MHS can be avoided if the gateway is used, since the MV/.../USERNAME directories become unnecessary. The gateway process will be released in due course. Override: In sites where the predominant mail type is SMTP, administrators may wish to set this flag: it tells Pmail to attach the MHS: override to the addresses of all incoming MHS messages when it moves them from MV/...USERNAME/APPNAME to the SYS:MAIL directory. This guarantees that replies will be generated to the correct address in every instance, but impacts slightly on transparency. Sites which are not using the SMTP gateway, where the MHS gateway is set to preferred, or where the Use always flag is set should set this field to 'N'. Pmail includes a number of user configuration options in its preferences menu: MHS user name : if a user has an MHS mail identity which is different from his/her NetWare usercode, then he/she will have to enter that identity in this field. The default is the first eight characters of the user's NetWare userid. MHS App name : if a preferred mailer has not been specified for a user when he/she was added to the MHS system, then mail will be delivered by default to an MHS application directory called MHS. Normally, Pegasus Mail should be installed in your MHS system using the application name PMAIL, which has been reserved with Novell: if, however, you are installing Pmail over the top of an existing MHS mailer, you may not wish to alter all the users. In either of the cases described here, you can change the name of the application directory Pmail will scan for new mail by entering its name in this field. Scan MHS dir for new mail? If set to Y, then Pmail will scan the user's default 'MHS' mailer directory for new mail, as well as scanning whatever directory is defined in "MHS App name". Pegasus Mail understands and uses MHS extended addressing, and will add any personal name the user has defined (under General Settings in the Preferences menu) to his address in outgoing messages: this will result in addresses of the form: joeblogg @ thalia (Joseph Bloggs) In outgoing messages. This syntax is legal, but might possible confuse older mailers which do not understand MHS extended address forms. The advantage of adding the comment field is that Pmail can pick it out of the address and display it in the message browse list; the personal name is 'friendlier' than a raw address. The following guidelines can be used as a guide when trying to decide the best way of configuring Pmail to operate with MHS at your site. 1: Sites using Pmail only, No SMTP, and MHS to deliver between servers: Set "Preferred" to 'N'; "Use always" to 'N'; "Enabled" to 'Y'; "Override" to 'N'. 2: Sites using MHS and SMTP (Charon) on the same system: Set "Preferred" to 'Y' if most mail traffic is MHS, otherwise set it to 'N'; "Enabled" to 'Y'; "Use always" to 'N'. Set "Override" to 'Y' if most mail is SMTP with only occasional MHS traffic. 3: Heavy MHS sites using more than one MHS mailer, and no SMTP. Set "Preferred", "Enabled" and "Use always" to 'Y'. Set "Override" to 'N' Pmail understands two different message formats: RFC-822, the Internet SMTP format, and MHS SMF-70 format. It can distinguish between the message formats transparently: pmail's own mail agent uses the RFC-822 format. Pmail stores all new mail in the user's unique mail directory in SYS:MAIL, irrespective of the transport used: if new MHS messages are detected in MV/.../USERS/APPNAME, they are moved to the user's SYS:MAIL directory before being read, along with any associated attachments. After being read, messages may migrate to a user-specified home mailbox (perhaps on a local drive) or may be left in SYS:MAIL/USERID, depending on user configuration. Outgoing mail is ALWAYS placed in MV/MHS/MAIL/SND for routing via MHS, as per the recommendation in the "MHS 1.5 Technical Overview". Pmail will NOT attempt local MHS delivery on its own - the MHS Connectivity Manager must be running for mail to be delivered. Since the expected main use of Pmail is in sites where Pmail's own agent is used for local delivery, and MHS is used for off-site transport, this should present no problems. * Local delivery: Pmail will NEVER attempt to perform local MHS delivery - the MHS Connectivity Manager must be run. * MHS Macros, as defined in the "Technical Summary of MHS 1.5" are not supported, will NOT be copied back into replies if referenced, but will not generate errors. * Confirmation requests: MHS requests for confirmation of receipt are honoured: confirmation is generated at the moment the message is opened for reading. PMIMPORT allows you to import and export address books between Pmail's internal binary format and ASCII text format. You can use this to generate system address books from other lists you might have available, and to export existing address books for correction and maintenance. PMIMPORT replaces the PMADDR program provided with earlier versions of Pmail, and still referenced incorrectly in the 2.2 manual. To use PMIMPORT, simply run it from the DOS prompt. It expects no command line parameters. You can use PMIMPORT to maintain user address books, but you must know the path to the user's home mailbox, since PMIMPORT does not read the user profile. The MAILDIR program provided in the distribution set will change directory to the SYS:MAIL mailbox of the user specified on the command line. Using this can be helpful when accessing user address books. PMIMPORT has only one menu, from which you can Import an ASCII file into an address book, Export an address book to an ASCII file, or change the flags on an address book. Importing and exporting are straightforward. The flags which PMIMPORT allows you to alter control whether or not an address book is to be treated as a system (non-modifiable) book, and whether or not an address book should be searched when Pmail attempts to resolve an alias. *** In Pmail 2.2 (R4), the alias disable flag is not imple- mented. It will be added to the next release. *** In PMIMPORT v1.1, the ALTER FLAGS option on the main PMIMPORT menu is non-functional. It will be enabled in a future version. PMIMPORT currently only reads or writes one ASCII format, known as Tagged Import/Export Format . In future, other import/export formats will be added. Tagged Import/Export format is a line-based format where each line begins with a keyword which identifies the rest of the line. The first line in the file MUST be the long name of the address book. Lines beginning with spaces or semi-colons (;) are treated as comments and ignored. A totally blank line indicates "end of record", and causes PMIMPORT to write the current entry when exported. You may have multiple consecutive blank lines if you wish - all subsequent blank lines are ignored until either end of file or a non-blank line is encountered. It is permissable in this format for fields to be missing for any entry. Only the Name: field must be non-blank, although an entry without an address as well won't be very much use to you. PMIMPORT currently reads and writes the following tags, corresponding to the appropriate address book field: Name: Dept: Key: Email: Postal: Street: Phone: Fax: Notes: User: "User:" is an optional 4-byte long integer value which you may use for any purpose you wish. Pmail will initialize it to 0, but you may store anything here. When PMIMPORT exports an address book, it writes all the tagged fields except User:, whether or not there is data in the field. User: is only exported if it is non-zero. This is to help you when maintaining the book. The following is a sample of an input file suitable for use with PMIMPORT. Note the very first line of the file, which is the long name of the address book. Note the missing fields in some entries - this is perfectly permissable. ----------------------- Cut here -------------------------- New personal address book Name: Brad Clements Dept: ERC Key: BRAD Email: "Brad Clements" <bkc@draco.erc.clarkson.edu> Notes: Author of Charon ; This line is a comment - it will be ignored. Name: David Harris Dept: Computing Services Centre Key: DAVID Email: "David Harris" <david@otago.ac.nz> Postal: P.O. Box 56, Dunedin New Zealand. Street: University of Otago, Leith Street, Dunedin. Phone: (+64) 3 453-6880 Fax: (+64) 3 453-6612 Notes: Author of Pegasus Mail. Name: Wyatt Barbee Dept: CBA Key: WYATT Email: wgbarbee@splicer.cba.hawaii.edu Postal: CBA, University of Hawaii, Manoa. Notes: Maintains Pmail-updates. PMGRANT can be used to grant or revoke extended feature rights (the ability to autoforward, disable mail, disable receipt confirmation and so forth) from the command line. This may be desirable if you have a very large bindery, with which PCONFIG may not be able to cope. Usage: PMGRANT [-w[-]] [-d] <username> username only grant rights to user allow user to alter settings prevent user from altering settings delete user's extended rights <username> may contain wildcards (* and ?) PMAIL.ICO is the official Windows v3 icon for Pegasus Mail. You can use it if running Pmail from Windows. PMAIL.PIF is a sample Windows v3 PIF file which you can use to configure Windows to run Pmail. Maildir is a simple program to change to a specified user's mailbox in SYS:MAIL. It may be useful if you need to check on the files in a user's mailbox. Usage: MAILDIR <username> <username> may not contain wildcards. Pegasus Mail is free software, and is provided with enough documentation and online help to be easily usable. No manual is provided though. In order to support the costs of hardware and software involved in developing Pmail, I sell printed manuals. There is no obligation to purchase manuals - none whatsoever. Purchasing manuals does, however, help me in my work and also gives you a tangible asset for your money. The manual is provided loose-leaf in a protective folder, ready for copying. The quality of the manual is high. I sell manuals in three ways: 5-user manuals : you get one printed manual with a license to make up to 5 further copies. This costs US$125. Site-licensed manuals : you get one printed manual with a license to make as many copies as you wish for one site. One site is defined as the extent of any organization in any one city or town, so if you have two branches in the same town, one site license will cover both of them. As well as the manual, site licensees get a diskette with RTF and ASCII versions of the manual. Site licenses cost US$275. One year update license : this is a site license with automatic updates: any time there is a new release of the software or manual up to one year from the date of the license, it will be automatically mailed to you at no further cost. Update licenses cover all versions of Pegasus Mail, even those which do not exist at the time of purchase. Update licenses cost US$1000, and can be renewed each year for US$250. Any type of manual can be upgraded to the next level for the current difference in cost between the two levels. To order a Pegasus Mail Manual license, please print and fill out the order form (see the menu for this - a copy of the order form is also supplied in ASCII format as ORDER.FRM). Then send it with your cheque or purchase order to: Pegasus Mail, c/- David Harris, P.O. Box 5451, Dunedin, New Zealand. Purchase orders are accepted from any educational or charitable institution or government department, and from companies with a paid up capital in excess of $30,000. Payment must be made in US dollars, drawn on a US bank . There is usually a delay of around 2-3 weeks before a manual can be sent out, and I reserve the right to hold your order if a new release is pending (so you can get the new release). PLEASE, PLEASE! Remember to enclose the order form: I'm not psychic, and I can't guess at delivery addresses from a cheque alone... A note to European users: it appears to be common practice for European Banks, particularly in Germany, to deduct fees from the cheque they send. In some cases, these fees have been as high as US$15. Because of the costs of manual production, and the relatively small amounts involved in the invoice, DEDUCTIONS OF FEES FROM REMITTANCES CANNOT BE ACCEPTED!! If your bank deducts fees from the remittance you make, I will return the cheque unpresented for repayment. If you prefer to make payments via direct credit to a bank account, please contact me for details. If you have purchased a previous version of the Pegasus Mail manual, you can upgrade it to the current version for US$75 , irrespective of the original type. A box is provided on the order form for upgrades - please check it when you send out the order. No proof of purchase is required - we have all the details on record. If you have already purchased a Pegasus Mail Site License for one version of the program, you can claim a discount of US$100 on a site license for any other version of the system. +----------------------------------+ | O R D E R F O R M | | for Pegasus Mail Manuals | +----------------------------------+ Ship to: Bill to: [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] What is your purchase order number? [ ] How many copies of the invoice does your accounts section need? [ ] Please supply the following items: ---------------------------------------------------------------------- [ ] 5-user Manuals for Pegasus Mail @ US$125 (license to make up to five copies of each copy ordered). . .US$ [ ] [ ] Site-licensed manuals for Pegasus Mail @ US$275 (allows unlimited copying of the manual for internal use in one site, where a site is defined as the extent of an organization in one city) . . . . . . .US$ [ ] [ ] Annual upgrade license @ US$1000: all manual and software releases will be sent to you for one year. . . . . .US$ [ ] [ ] Upgrade from any previous version of the manual to the current version @ US$75 . . . . . . . . . . . . . .US$ [ ] Shipping via first-class airmail is included in the price of any of these options. Please allow 2-3 weeks for your order to be processed. ---------------------------------------------------------------------- Ordering instructions: Please complete this form, and send it via airmail with your cheque or PO to: Pegasus Mail, c/- David Harris, P.O. Box 5451, Dunedin, New Zealand. or e-mail it and the PO number to: david@otago.ac.nz (from CompuServe the address is >internet:david@otago.ac.nz)