DP Tool Club 8/CDASC08.ISO/VRAC/PM301.ZIP/GUIDE.EXE

David's Readme Compiler Executable | 1993-09-01 | 130.2 KB | 1,928 lines

FcYY=
Y4YYF
5YY_^
j3YY_^
H9D0}
 ; A B D G H I K M O P Q R S s t u v
,uY_^]
YYG;>
 A B D
<Ar    ,@
_^_^]
 H I K M P Q
yVY_^
 H I Q.4
YYF;v
;Dz~
9+:+:!:
9+:8:
 DYPV
 H I K M P Q @
DF_^]
YY9|,uK
;D@ui
;DDu2
H9D0~
9D<|    u
.Y;D2v
H9D0u
YY_^]
YY_^]
~-YY3
,Y)D:
C+Y;F
f)Y;D2wK
I].97t
 G H I K M O P Q R S s t u w@h
hQh(gjg,h
t0Nt-
!r.RP
!r$RP
u/SQR
[[XP3
Turbo C++ - Copyright 1990 Borland Intl.
Null pointer assignment
Divide error
Abnormal program termination
$    ~ p
Courier
Do you want to overwrite
File exists
 Print Settings
 - Printing -
 Save as what file?
Failed saving to file!
 Failed!
 PgUp/Dn:
<F10>
 options
 PgUp/Dn
 Line %d of %d
 Search for
 Topics
ind text   <F7>
find
gain  <F8>
rint entry
ave entry
dit entry
Printer port :
PostScript?  :
Press <Space> to change values
Created using
David's Readme Compiler v2.1
(c) 1990-93, David Harris.
e-mail: [e-mail]
LPT1:
LPT2:
LPT3:
%!PS-Adobe-2.0
%%Creator:DRC v2.0
%%EndComments
/leftmargin { 40 } bind def
/bot { 54 } bind def /top {
 } bind def
/cw { 40 } bind def
/xtab
 {currentpoint exch dup cvi
 leftmargin cvi sub cvi
 cw cvi mod sub
 cw add
 exch moveto
 } bind def
/ptsize { 12 } bind def /lead { 12 } bind def
/F { findfont exch scalefont setfont } bind def
/newline {
 currentpoint exch pop lead sub
 dup bot lt {
  pop showpage restore save
  top
  } if
 leftmargin exch moveto
 } bind def
%%Endprolog
%%BeginSetup
ptsize /| F
leftmargin top moveto
%%EndSetup
%.20s (Y/N)?
%-50.50s
newline
) show newline
newline
showpage restore
David's Readme Compiler, (c) 1992, David Harris.
Readme error: no attached data.
 About this Guide
MMMODE
 ; < = > ? @ A B C D T U V W X Y Z [ \ ]
 G O w u R S s t
EAEIIOOUUYIOU
(press any key to continue)
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
 .,@:;
0123456789
         !!!!!
@@@@@@@@@@@@@@@
@@@@@@@
@@@@@@
@@@@
(null)
Data file generated by RCOM.
 Pegasus Mail version 3.0 (R1) guide
Welcome to Pegasus Mail!
Main screen status line
Help on editing text
IMPORTANT info for current users
Information about Pegasus Mail
Installing Pegasus Mail
Customizing your installation
User-defined gateways
PMIMPORT - importing addresses
Other utilities supplied
Hints, tips, suggestions
Ordering PMail manuals
What's New in PMail 3.0
Things to be aware of in 3.0
PMail and NetWare 4.0
Special note for MHS users
Revision history
Finding the PMail version
Version 2.3 (R5)
Version 2.3 (R4)
Version 2.3 (R3)
Version 2.3 (R2)
Version 2.3 (R1)...
Bug fixes and corrections
New features
Default profiles
Version 2.2
Version 2.2 (R3)
Version 2.2 (R4)
About Pegasus Mail
Contacting the author
Acknowledgments
Pegasus Mail Source Code
About this guide...
System requirements
Installing Pegasus Mail
Standalone installation
PMail on Non-NetWare LANs
TEMP and TMP variables
Modifying NET$LOG.DAT
Enabling extended options for users
Enabling delivery between servers
Control groups
Enabling Internet Mail Support
ResCom, the PMail resource compiler
System-wide lists/books/folders
International language support
Adding your own MIME viewers
Adding items to the main menu
SMTP/PostScript character maps
Programmable forms
Site-specific address lookups
Variable signatures
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
Command-line operation
Sample input file
PMGRANT.EXE
PMAIL.ICO/.PIF
MAILDIR.EXE
PREBUILD.EXE
UNCONFIG.EXE
NMAIL.EXE
Pegasus Mail as a listserver
Command-line operation
Problems sending mail?
Pegasus Mail Manuals
Ordering manuals
Telegraphic Transfers
Orders from Europe
Payment by credit card
Upgrading existing manuals
Pegasus Mail Manuals - Order Form
This electronic guide contains all the information you need to
install and use Pegasus Mail.
If you already use Pegasus Mail, you should examine the section
entitled
Important information for current users
 carefully - it
describes what is new in this release as well as any special
installation instructions.
If you wish to order manuals, you can edit and print the order
form from within this guide by pressing
<F10>
 and selecting
 while viewing the form.
Full search capabilities are available in this guide at any time
by pressing
, or selecting
Find text
 from the <F10> menu.
Please press
<Return>
 to continue...
         Pegasus Mail, (c) 1990-1993, David Harris, all rights reserved
     Search, edit and print options available when reading by pressing <F10>
While editing this form, you can move from field to field using
<Tab>
 key.
Use the arrow and page keys to move around while editing. You can
delete text using the
<Del>
 and
<Bks>
 keys, and
<Ctrl-Y>
 will delete
a line.
You cannot alter the readme file from this screen, but you can save
the screen (with any changes you make) to a text file by pressing
<F10>
 and selecting
. You can print this form at any time from
the same menu.
Any changes you make will be lost when you close this screen.
Please press <Return> to continue...
With PMail 2.2 & later, 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.
A full reference to PMail's user-defined gateway feature, as well as
a sample UDG which interfaces PMail to Waffle 1.64 either on a LAN
or standalone is included in this archive in the file UDG.ZIP.
The following features or capabilities are new in PMail 3.0.
 Forms support
  PMail 3.0 allows you to develop your own mail entry forms. The
  forms support in PMail is rather complex - it is not intended that
  the average user will create forms, but rather that one computer-
  literate individual will create forms to which everyone will have
  access. Forms require a small amount of programming skill and some
  patience but can do almost anything. Half a dozen forms are
  provided in "canned" form (complete with source).
 MIME support
  MIME is a new Internet standard for handling multimedia mail:
  PMail 3.0 is rather more than "minimally compliant", as defined by
  appendix A of RFC1341. It supports Base64 and quoted-printable
  encodings with eight ISO character sets, minimal rich-text, has a
  multipart browser and supports site-definable browsers and viewers
  for unsupported MIME types.
 Hierarchical folders
  You can now have "trays" in your folder list: a tray is a folder
  which can contain other folders. Nesting can be arbitrarily deep,
  and commands are provided to move folders around within the
  hierarchy. The hierarchical folder system is 100% compatible with
  the PMail 2.35 folder structure.
 Multiple drafts
  You can now save multiple message sessions as drafts and come
  back to them later. The "stationery" flag introduced in WinPMail
  is also supported. The save-session key (^KS) now (finally) works
  in the message header fields as well as in the message body.
 Several improvements have been made to the UDG interface.
 Site-defined address list support
  You can now create your own program for local user listings and
  tie it into the <F2> userlist key. The program passes addresses
  back to PMail in a file specified on the command line.
 Fixed alias clashes
  PMail 3.0 now detects the condition where more than one address
  book contains an alias and presents the user with a dialog asking
  which alias to use. Address validation is now deferred until the
  point at which the user asks to send the message, so delays in
  going from field to field in the message editor when you have large
  address books no longer occur.
 Improved printing
  PMail 3.0 has much better printing support; messages are printed
  more tidily and problems people have had in the past with last
  page ejection should be gone. PostScript users can now select the
  point-size of the font they want to use.
 Attachments revamped
  PMail 3.0 now does attachments in much the way WinPMail does, allowing
  you to specify attachment encoding (the terrible "send as message"
  flag is now gone forever). PMail 3.0 supports BinHex and has an
  updated uuencoder which no longer encodes to spaces.
 Scans messages for enclosures from other mailers
  PMail 3.0 checks the first few lines of each message for uuencode
  and BinHex signatures and flags the message as an attachment in the
  browser if it finds one.
 Print message from the message editor
  You can now print messages as you edit them using ^KP.
 More browser options
  A new browser option ("Other") contains several new options. The
  previously undocumented <U> key (uudecode) is now a menu option
  on the "other" menu along with simple commands to add a user to
  a distribution list and more.
 Improved rule processing
  A new rule has been added which allows you to run a program with
  the message as a parameter. As well, you can now have multiple rule
  sets and can apply rule sets to any folder at any time.
 Completely resource-based for internationalization
  PMail has been rewritten from the ground up and now contains no
  data - it's all loaded at runtime. The effect of this is that it can
  now be internationalised without recompilation, and multiple language
  versions can exist on the server, the preferred one being chosen at
  run-time. Translations to French, German, Czech, Spanish, Portuguese,
  Finnish and Dutch are already in progress.
 Command-line totally revamped
  PMail's command line has been totally rewritten with many more
  options; for instance you can now specify the CC field and any message
  flag (urgent, no signature and so on) on the command line. There is
  also a command-line option which starts PMail, applies new mail
  filtering rules to the new mail folder and exits immediately. You
  can enter "PMAIL /?" for full help on the command line options.
 "Become" option from command-line
  You can now "become" another user with full access to that user's
  mailbox
provided
 you have NetWare access rights to the directory.
  This feature can be enabled either totally or partially using the
  groups BECOME and NOBECOME - by default it is disabled to prevent
  mail forgery.
 Prompt for copyself folder
  You can now tell PMail to ask you in which folder it should
  place copies to self for your messages on a message by message
  basis; this effectively allows you to file your copies to self
  as you make them. This option is enabled from the "Copies to
  self" options screen in your preferences.
 Import, export and print options in the address book.
 PMGRANT improved
  The PMGRANT command-line program for managing extended features
  for users has been heavily improved. In particular, it can now
  display extended feature settings for users via the -v switch.
 PMPOP POP3 gateway for LAN Workplace for DOS
  PMPOP is a full POP3/SMTP implementation UDG for PMail which uses
  the LWP TCP/IP stack. It has been designed so that PMail users on
  non-NetWare LANs can use it as a simple but effective Internet mail
  transport (running on a dedicated machine).
There are also lots and lots of small fixes and improvements which
have been coming for quite some time.
Current users of Pegasus Mail should note the following points:
 PMail 3.0 uses the resource file PEGASUS.RSC where older
  versions used PEGASUS.HLP. PEGASUS.HLP is no longer needed
  and can be deleted.
 PMail 3.0 supports subsidiary indexing of address books to
  speed sorting by key. Examine PMSORT.EXE for more details.
 To enable MIME support for outgoing mail, you must turn on
  "Use MIME features" in the message headers (<F9>).
 SENDER.PM has been replaced by PM-MENU.RSC in v3.0 and
  Site-specific MIME viewers are installed via PM-MIME.RSC.
  For more information on the PMail 3.0 resource format,
  examine FORMS.TXT in the RESOURCE.ZIP file and the various
  *.R sample files supplied with the release.
 The PMail v3.0 command line is totally different from that
  used in previous versions - applications depending on the
  old format will fail under 3.0.
 If you have created variable signatures for PMail 2.35 you
  will need to revise them to work with PMail 3.0. VSigs in
  3.0 are resource-based and must be created in a different
  format - examine the file RQUOTES.R for more information
  and some sample variable signature quotes.
 PMail 3.0 uses a new dictionary format for its spelling
  checker which requires only one file, PMDICT3.PMD. The
  dictionary files from previous versions of PMail -
  PMDICT.PMD, COMMON.PMD and PMDICT.NDX - are no longer
  required and can be deleted.
PMail 3.0 is compatible with NetWare 4.0 in Bindery Emulation
Mode only: it currently will NOT run well under 4.0 in NDS
mode.
I expect to release a connection server for PMail which will
work well in the NetWare 4.0 environment late in 1993.
If you have previously used an earlier version of PMail with
MHS, then you MUST run the PCONFIG supplied with this version
of PMail and check PMail's MHS settings - they will almost
certainly have changed.
If you are using NetWare MHS 1.5, make sure that the "SMF-71
available?" field is set to 'N'. Also make sure that all the
other values are sensible.
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
PMail 2.35 is mostly consolidation over previous versions, although
there are some new goodies as well.
* Long folder names are now shown in the browser title
* Some cosmetic fixes (spaces after names etc)
* Trailing white spaces in addresses is now stripped.
* Ctext comments in addresses containing commas  (such as
  "(David Harris, CSC)" no longer causes parser errors.
* Extra Distribution List keywords:
  In this release, you have many more options in DLists by
  using keywords starting with '\' in the list.
   all addresses following a \CC entry in the list
          will be placed in the message's CC field.
  all addresses following a \BCC entry in the list
          will be placed in the message's BCC field
   all addresses following a \TO entry in the list
          will be placed in the message's TO field. You can
          use \CC, \BCC and \TO as often as you wish in the
          list, and the addresses will accumulate.
  [ Note: the \TO, \CC and \BCC lines should appear on a
    line of their own in the list - they affect addresses
    on subsequent lines in the list ]
\READING Y/N
  sets the message's "Request confirmation
          of reading" flag to either Y or N.
\DELIVERY Y/N
 sets the message's "Request confirmation
          of delivery" field to either Y or N.
\URGENT Y/N
  sets the message's "Urgent" flag to either
          Y or N.
\NOSIG Y/N
   if N, then signatures can be appended to
          the message; if Y, they cannot.
* Reply-to-all option: you can now select "reply to all" in
  the reply dialog options. If you do, PMail will create a
  distribution list called "Temporary List" containing the
  addresses of every recipient of the original message. Note
  that this includes you.
* Help for the search options in the editor/better prompt.
* UDGs are now polled when "read new mail" is selected. Prior
  to this release, UDG's which depended on a program being run
  to process new mail were not run. That is fixed in 2.35.
* Progress indicator in mail loader window.
* Alternate text selection fixed: PMALTEXT.DAT, used to
  customize SMTP translation tables and PostScript printing,
  was broken in 2.34. It works in 2.35.
* Pmail now picks up NetWare IDENTIFICATION property as
  the user's Personal Name by default when first run.
* MV option now installed using PCONFIG: MHS users can now
  supply the path to the MHS tree using PCONFIG. Doing this
  allows PMail to operate correctly as an MHS mailer when
  the user chooses "Change file server" from the main menu.
Not done in this release:
  At various times I indicated that this release would
  include support for BinHex, and more flexible encoding
  options for attachments. People have also assumed that
  this release would include MIME support, and forms
  support. Because of a lack of time, these options are
  all missing from this release, but will certainly be in
  the next release, early in 1993.
PMail 2.3 (R4) fixes a bug with very long MHS addresses. It also
adds some important internationalization features.
   * PMail's SMTP translation table (a table which determines
     what is sent in place of high-bit characters, which cannot
     be included in SMTP Mail) now supports multi-character
     substitutions, and has been completely redesigned.
   * PMail's PostScript printing now supports the PC extended
     character set.
   * Both the SMTP table and the PostScript character table
     can be overridden locally. This allows sites to install
     their own printing preps for PostScript, and to design
     their own SMTP translation tables. The tools and info
     necessary to do this are contained in CHARSET.ZIP in
     this archive.
   * A new option has been added to DEFAULTS.PM - MHSApp
     allows you to set the MHS Application Name PMail will
     use when retrieving new mail for a user.
   * You can now use the editor ^K^W command to write a
     marked area while reading a message.
   * You can now use the editor ^K^C and ^K^V (copy and
     cut) commands in fields. The field is copied to the
     scrap buffer, and if ^K^V, the field is cleared.
   * Variable signatures: I decided it was time to have a
     little fun, so I added this. You can now have PMail
     pick a random piece of text from a set you provide
     and add it to your signature. Details on how to do
     this are also found in CHARSET.ZIP.
PMail v2.3 (R3) is a maintenance release which fixes a number
of small problems in PMail 2.3 (R2).
Fixed:
   * PMail will not now crash when trying to read more than
     30KB of data into the editor.
   * PMail will not now crash when reading a message with
     more than 300 lines in the To: field. A side-effect of
     this fix is that PMail can now browse messages up to
     around 70% the size of available RAM.
   * Distribution lists may now be nested, and only the
     \SENDER and \REPLYTO fields of the topmost list will
     be included in the message.
   * PMail will now issue a warning when a folder is too
     large to open, and load as many messages as it can
     (around 1900 on a typical machine running DOS 5).
   * PMail should now correctly parse messages sent via the
     MHS<->UUCP gateway UGATE.
   * PMail now issues warnings if you try to paste more data
     from an address list into an address field than will fit.
   * Problems sending attachments on NetWare 2.X servers have
     been fixed.
   * PMail now recognizes and processes new MHS mail as part
     of the browser idle cycle (previous versions only
     checked for new PMail or Charon-style mail while the
     new mail folder was open).
   * Problems with "corrupt message" errors when new mail
     arrives in the Newmail browse screen should diminish.
   * PMail no longer sends an attachment envelope if all
     the attachments are sent as messages. The wording of
     the attachment data entry screen has also been changed
     to be more accurate and informative.
   * PMail no longer strips high-bit chars in signatures
     sent to local addresses.
Worked-around:
   Under previous versions of PMail, newmail filtering rules
   would be repeatedly applied to mail left unread in the
   newmail folder. PMail 2.33 works around this by flagging
   such messages as read. It's not a perfect solution, but
   the problem is more complex than it seems. This workaround
   does NOT affect the Read/Unread status of messages moved
   or copied into other folders - only mail which is left
   in the newmail folder after processing is affected.
Added:
   There are only a few feature additions over 2.32...
   * A new header option allows you to omit your signature
     from a message.
   * New command substitutions available for user-defined
     gateways:
     - ~x   Substitutes the name.ext ONLY of the
            message container file (ie, path stripped)
     - ~p   Substitutes the user's Personal Name field
            as defined in the Preferences Menu.
   * Password entry at startup can now be specified in
     DEFAULTS.PM
   * PMail will now offer to try to create your home
     mailbox if it doesn't exist at startup.
   * New Actions for Newmail Filtering Rules:
     - Add user to list: adds the sender of the message to
       a distribution list. Only lists created using <F6>
       are candidates.
     - Remove user from list: removes the sender of the
       message from the specified list.
   The new rules work strictly on the address, and are not
   fooled by personal names or other comments in the field.
   The sender's address is taken from the Reply-to field of
   the message if one exists, or else the From field.
PMail v2.3 (R2) is a significant release, which fixes a number of
small problems and adds a number of new features.
Fixed:
   * The "Check for New Mail" option will now remain permanently
     enabled if it has a submenu created using the SENDER.PM file.
   * Macros will now work correctly from the main menu.
   * The Copy-CC option for replies now copies the whole CC field.
   * Dates are now correctly printed in all cases in standalone mode.
   * A problem which could cause PMail to crash when addressbook
     entries were edited has been fixed.
   * A problem which could cause PMail to crash after printing
     messages to local printers has been fixed.
   * Problems parsing illegal MHS messages which could occasionally
     result in attachments being "lost" have been fixed.
   * Attachments via MHS from CompuServe will now be recognised
     and processed correctly (even though I really don't like
     the way they do it).
   * Aliases are now correctly resolved in distribution lists.
   * Encryption now works correctly with MHS messages.
   * ... and lots of others which I can't remember.
Changed:
   * PMail now allocates memory more frugally when editing messages.
     This should reduce memory requirements in most cases.
   * The message browser now sub-sorts sensibly; so, if you are
     sorting by date, PMail will sub-sort by sender, and so on.
   * Message headers are now formatted more tidily in outoing mail.
   * The address book and SMF-71 listing windows now have a much
     more functional layout, and the addressbook sorts more than
     an order of magnitude faster on large books.
Added:
   * Password operation: there is now a preferences option
     which will force PMail to prompt for, and verify the user's
     NetWare password before running.
   * True attachments: when composing a message, <F7> now allows
     you to add attachments to the message.
   * Attachment types: PMail now allows you to add a limited
     amount of information about the file type to attachments.
   * Checkmarks on read mail: messages you have read are now
     visibly marked in the browser list with a checkmark (
   * Complete support for the New NetWare SMF-71 message format
     (used by NetWare Global Messaging and MHS v2 when released).
   * Organization field: PCONFIG now allows you to define an
     organization field (a-la-NetNews) for outgoing Internet mail.
   * Urgent field (in the <F9> message headers option). You can
     now flag messages as urgent. The broadcast message for urgent
     mail is different, and PMail sorts urgent mail to the top of
     the browser, displaying the entry in red. Other applications
     receiving an urgent message may or may not handle it in any
     special way even though PMail uses standard headers to show
     that the message is urgent.
   * Delivery confirmation: this differs from receipt confirmation
     in that you are provided with proof that the message has been
     delivered, rather than read. This option is only reliable when
     using NetWare MHS, although many Internet mailers (including
     Charon 3.5) will honour it.
   * From-field synonyms: it is now possible to use usernames other
     than your NetWare username in SMTP messages - so, you can
     define addresses like "[e-mail]". This feature
     will not be usable until Charon v3.5 is released, and will be
     fully documented there.
   * SMFSEND: PMail can now use the MHS SMFSEND utility to deliver
     MHS mail, obviating the need to have MHS running on your system.
   * Environment variables in command substitution: you can now
     substitute the value of an environment variable into any string
     which uses command substitution (ie, fields in DEFAULTS.PM, and
     most of the strings in User Defined Gateway Definitions) using
     the following syntax: ~%varname% - that is, a ~, followed by
     the name of the variable enclosed in % signs. If the variable
     does not exist, or has no value, no substitution will occur.
   * Prebuild.exe: rebuilds damaged PMail message folder indexes.
   * Unconfig.exe: totally removes PMail's configuration records
     from the NetWare bindery.
   * 2 new Newmail Filtering Rule actions have been added -

Text File
 and
Send Binary File
. As well, if the search
     text for a rule starts with a caret (^), then PMail will only
     activate the rule on an exact match (ignoring case) - so,
     "^SUBSCRIPTION" will activate on "SubScription", but not on
     "Concerning my list subscription".
   * Newmail Filtering Rules will now apply to new mail which
     arrives when the new mail folder is open. Using this and the
     new rule actions, you can use PMail to implement a simple but
     effective listserver. See the instructions in the
Hints, tips
     and Suggestions" option on the main menu for more details.
Enhanced:
   * PMGRANT has been totally reworked: you can now manipulate all
     aspects of PMail's extended features from the command line
     with PMGRANT. Enter PMGRANT with no parameters for help.
   * PMIMPORT can now be run from the command line: enter
     PMIMPORT /? for information on how to do this.
PMail 2.3 (R1) fixes the following problems:
   * When replying to an encrypted message, the message is
     decrypted correctly when included.
   * A problem which could cause MHS attachment extraction
     to fail has been corrected.
   * A variety of MHS parsing problems associated with
     mailers whose authors don't read standards docs have
     been accommodated (idiots!).
   * The reformat command has been repaired: it will now
     reformat paragraphs without doubling spaces in places,
     and will reformat commented paragraphs correctly.
   * Distribution lists can now be correctly renamed.
   * Problems some sites have had with newmail filter rules
     either crashing or being improperly applied have been
     fixed.
   * Several cosmetic issues have been fixed/resolved.
   * A short-term fix has been provided for sites who find
     that folders are not compressing, but just keep growing
     and growing: Pressing <F10> while in the folder selection
     window will unconditionally compress a folder.
The folder compression problem has not yet been resolved, since
I can't replicate the problem - they compress fine for me! A
number of diagnostics have been built into this release which
will appear if PMail encounters problems compressing a folder.
If you see any of these messages, please quit from PMail and
contact me as soon as you can without touching the folder again,
so I can check it out.
Some new features are included as well:
   * Standalone operation. PMail can now run on non-NetWare
     LANs (with some limitations) or on standalone machines.
     Source for an interface to the Waffle BBS system (which
     provides UUCP mail) is included in the file UDG.ZIP. An
     Asynchronous gateway will be available for PMail in the
     near future.
   * User-defined gateway support has been heavily beefed up.
     Please see the section on the main menu covering this
     topic, and the file UDG.ZIP.
   * NEWMAIL.EXE now checks for new MHS mail.
   * A new group, PMSEND, is now checked before sending messages
     from the logged-in user list (<F4>). If the group exists
     and the user is not a member, or if the user is a member
     of NOPMSEND, then he/she will not be allowed to send.
   * NOGROUPMAIL: a counterpart to the GROUPMAIL group, used to
     control who can mail to groups. If a user is a member of
     this group, he/she will NOT be permitted to mail to groups.
   * PROMPT options in message headers: you can now enter the
     value
 in the
Copy Self
 and
Request confirmation
     message fields. A
 value will force PMail to
Prompt
     you for a Yes or No before sending the message.
   * INFO option on the Browse menu gives information about
     messages, including whether they have been read, replied
     to or forwarded. NOTE: PMail CANNOT remember whether you
     have replied or forwarded a message if you leave your
     New Mail new, although it will remember if you have read
     it.
PMail 3.0 allows you a limited form of "default profile" -
a user profile which will be applied the first time the user
runs PMail. The default profile is a text file called
DEFAULTS.PM, stored in the same directory as PMAIL.EXE. It
contains lines consisting of keyword/parameter sets. In 3.0
the following keywords are recognised:
   Homebox   Where the user's home mailbox should be located.
             This should be a path in either NetWare or DOS
             format with no trailing '\'. The directory
             must exist - PMail will not create it. All
             command substitutions possible in user-defined
             gateways can be used here: in practice, this
             allows you to imbed the special string ~8 in
             the path - it will be replaced by the first 8
             characters in the user's name at runtime. For
             more information on command substitution, see
             the file UDG.TXT in UDG.ZIP.
   Copyself  N, Y, or P, to set the copy-self option for the
             user. The P option forces PMail to Prompt for
             copy-to-self at send time.
   Scratch   A work area. If you do not define a TMP or TEMP
             variable on your machine, you should give this
             a meaningful value. As with 'Homebox', command
             substitutions are possible in this string.
Lines starting with a semi-colon, a space, or a tab are
considered comments and ignored. Case is not significant.
All, some or none of the keywords may be used in the file.
Unrecognised keywords are ignored without error or warning.
A sample DEFAULTS.PM is provided with this distribution. Other
fields may be added to it in future.
   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.


  Welcome to Pegasus Mail, v3.0

   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 purchase order or cheque if you choose to 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 native
Windows version, WinPMail, is also available). 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, then you can mail me at one of two addresses:

[e-mail]
             (preferred)
  or
[e-mail]
From CompuServe, you can mail to me at either of these addresses by
prefixing them with
>internet:
 - e.g.
>internet:[e-mail]
I'm not currently addressable via MHS, but hope to be in the future.
If you wish, you can fax me at either
([phone]
I can be phoned at
([phone]
, 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 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 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
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/drc21.zip.
It can also be found on CompuServe in the NOVUSR area.
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 384Kb 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.
PMail 2.32 and later are SMF-71-aware, and completely compatible
with SMF-71 systems such as Novell's NetWare Global Messaging, and
MHS v2.0 (yet to be released at the time of writing).
To install Pegasus Mail, copy the files
pmail.exe
newmail.exe
pegasus.rsc
 and
pmdict3.pmd
 to a publicly-accessible directory on
your network file server. If you are currently using a version of
PMail earlier than v2.2, you
 also copy the file
pconvert.exe
to the same directory. DO NOT copy other files from the PMail
distribution to the public directory, unless you are sure they are
needed. Normally, you need only copy the files named above.
Note that Pegasus.rsc and PMail.exe must be in the same directory, or
PMail will not run. 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.
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.
Pegasus Mail can run on standalone machines, although it will
have limited usefulness in such a case unless a user-defined
gateway is provided as a mail transport. Standalone installation
is easy: copy PMail.exe and Pegasus.rsc into a directory on the
path, then run PCONFIG.EXE. Choose the option for standalone
configuration from the main menu and tell PMail where your home
mailbox and new mailbox are located (PCONFIG will NOT create
these directories). Note that you can use command substitutions
(see UDG.TXT in UDG.ZIP for more information on this) in these
fields to allow multiple users to run on the machine.
When you start PMail standalone, it will look for the DOS
environment variable PMUSER: if it exists, it will use its
value as the current user's name. If it does not, then PMail
will open a window and ask the user to enter his or her name.
PMail does NOT validate the username in any way whatsoever.
We suggest you examine the user-defined gateway manual UDG.TXT
in the archive UDG.ZIP supplied with this distribution: this
will give you more information you can use to run PMail in
standalone mode, and provides a sample interface to Waffle.
Pegasus Mail can be run on non-NetWare LANs, although the
support for this is rather crude at this stage - essentially
a generalisation of standalone operation.
To run PMail on a non-NetWare LAN, you need to define a mailbox
directory structure based on usernames in a globally-available
location on your file server. Then, run PCONFIG and use a
command substitution in the Homebox and Newmailbox fields to
key the structure.
   Example: you have created a directory called M:\MAIL. In
     this directory you have created a subdirectory for each
     user based on their usernames - so user DAVID's mailbox
     is M:\MAIL\DAVID and so on. Using PCONFIG, tell PMail
     that the Home mailbox is M:\MAIL\~8 and that the New
     Mailbox is also M:\MAIL\~8. PMail will use this infor-
     mation to perform local delivery.
Users only need the ability to create files in other users'
new mail folders - I encourage you to limit their rights in
this manner using the facilities your LAN offers. Of course,
a user needs all rights in his own mailbox...
You will have to devise your own user-defined gateways to
provide mail transports off-server.
Non-NetWare operation will be heavily enhanced in future
versions of PMail with the introduction of a true user
database which PMail can use as well as or instead of 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.
Many aspects of PMail's operation can be controlled using NetWare
User Groups (created using the NetWare SYSCON utility). PMail 3.0
recognizes the following NetWare groups:
     GROUPMAIL   Those who MAY send to NetWare groups
   NOGROUPMAIL   Those who may NOT send to NetWare groups
       MAILBOX   Those who MAY have a home mailbox on the server
     NOMAILBOX   Those who may NOT have a home mailbox on the server
     MAILUSERS   Those who MAY use Pegasus Mail to send mail
        NOMAIL   Those who may NOT use Pegasus Mail
        PMSEND   Those who MAY send one-line messages from <F4>
      NOPMSEND   Those who may NOT send one-line messages from <F4>
        BECOME   Those users who MAY run PMail as other users
      NOBECOME   Those users who may NOT run PMail as other users
In the absence of both allowing and disallowing groups, the default is
that all users have access; so, if there is no MAILUSERS and no NOMAIL
group, then all users may use mail. The exception to this rule is the
BECOME/NOBECOME combination: in order to become another user, one of
these groups must exist and you must be authorised (either by being a
member of BECOME or NOT being a member of NOBECOME).
Pegasus Mail directly supports Internet mail via either the Charon
SMTP gateway by Brad Clements or by my own Mercury Mail Transport
System for NetWare 3.11.
To enable Pegasus Mail's support for these transports, run the Pconfig
program supplied and choose `SMTP Internet mail intercaces': a dialog
window will appear. You must provide the following information:
Spool interface?
  If you are using Mercury 1.11 or later as your
   SMTP transport agent, you can select either a queue or a directory
   interface to Mercury. The directory interface has some advantages
   over the queue interface and is the only way of running Mercury
   under NetWare 4.0 at this time. For more information on using the
   spool directory interface to Mercury, see the Mercury 1.11 guide.
Queue name
:  this is the name of the print queue you have created
   (using the NetWare PConsole utility) from which Charon or Mercury
   expects to retrieve messages. The queue need not exist at the time
   you define the interface. If you have installed Mercury 1.11 using
   the spool directory interface, you should enter the path to the
   Mercury spool directory in this field, preferably in the MS-Net UNC
   format of
\\SERVER\VOLUME\PATH
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. 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 3.0 is entirely resource-based; all data in the program
is loaded at runtime from indexed read-only data files called
resource files
, which are created using PMail's resource
compiler, ResCom.
Customising PMail requires at least some familiarity with the
format ResCom expects and can be reasonably complicated; forms
support in particular can be quite involved, although it's
powerful enough to reward the effort handsomely.
The primary reference for ResCom is to be found in the Forms
support file for PMail 3.0, RESOURCE.ZIP, which is included as
part of the PMail 3.0 distribution: unpack RESOURCE.ZIP in its
own directory and examine it, in particular the file FORMS.TXT
which is the forms reference.
Well-commented source code for several sample resource files
is provided with PMail 3.0; by printing FORMS.TXT and examining
the samples you should be able to customise PMail extensively
with relatively little effort.
Instructions for creating system-wide entries:
Creating system-wide distribution lists:
   Distribution lists are text files with the extension
   make a distribution list system-wide, copy it into the same
   directory as PMAIL.EXE, or else put it in a publicly-accessible
   location on the server and set a PML DOS environment variable to
   point to that location.
Creating system-wide address books:
   Address books consist of two files - name
 and name
   create a system-wide address book, copy both files for the book
   into the same directory on the server as PMAIL.EXE. Alternatively,
   copy the files into a public directory then set a DOS environment
   variable called PMR which points to that directory. If the address
   book is large and changes little, consider creating a secondary
   index for it using PMSORT.EXE - this will markedly speed up PMail
   when opening it.
Creating system-wide mail folders:
   In the same directory on the server as PMAIL.EXE, create a sub-
   directory with the extension
 - the name is unimportant. In
   this directory, create a file called
PMFOLDER.ID
, which contains
   the long name of the folder. On some systems, you may have to
   edit the file using a binary editor (such as Norton's DE) so that
   the last character in the file is an ASCII 0.
   Once you have created the folder and the name file, grant rights
   to the directory as required: in order to read messages, users will
   need [RF] rights; in order to move messages into the folder, they
   will need at least [RWCF] rights.
Pegasus Mail v3.0 is fully internationalizable: all text, strings
and data structures are stored in PEGASUS.RSC and loaded at runtime.
At the time of release for 3.0, translations are under way for the
following languages:  Dutch, German, Czech, French, Spanish, Finnish
and Portuguese.
When international versions of PMail are made available, they will
appear as replacements for PEGASUS.RSC; these files should be copied
into the same directory as PMAIL.EXE on your file server and can be
selected by setting an environment variable called
PMRSC
 to the
name of the resource file.
Example:
   the French version of PEGASUS.RSC might be called PEGASUS.FR;
   you would
SET PMRSC=PEGASUS.FR
 before running PMail.
Translation of the PMail resources is done under a quite strict
nondisclosure and licensing agreement - contact [e-mail]
for more information if you are interested in producing a version
of PMail for an unsupported language.
MIME (Multipurpose Internet Mail Extensions) is a recent standard
which addresses several long standing problems with Internet mail,
most notably the transmission of binary data.
PMail 3.0 supports everything required for "minimal compliance" to
the MIME specification as described in Appendix A of RFC1341 and
quite a bit more; in particular, you can define your own attachment
viewers for MIME content-types which PMail does not support directly,
such as IMAGE/GIF or APPLICATION/POSTSCRIPT. You can also override
PMail's internal viewers for every type except MULTIPART/MIXED.
Customising PMail's MIME support is done via a PM-MIME.RSC resource
file created using the PMail 3.0 resource compiler, ResCom. For an
example of how to create a PM-MIME.RSC file for yourself or your
entire site, examine the sample source file, PM-MIME.R contained in
the file RESOURCE.ZIP provided as part of the PMail 3.0 release.
PMail 3.0 allows you to add sub-menus to the
New mail
 and
 options on the main menu and to define your own
address
listing
 services, via a resource called PM-MENU.RSC.
As with other PMail 3.0 customisations, PM-MENU.RSC is created
using the ResCom resource compiler. A sample PM-MENU.R source
file is provided in the RESOURCE.ZIP file supplied as part of
the PMail 3.0 distribution.
In previous releases of PMail it was possible to alter the
SMTP translation table PMail uses to map 8-bit characters
onto 7-bit data for outgoing messages, and to change the
PostScript code PMail uses to format banners and messages.
This facility is preserved in PMail 3.0, although the SMTP
translation table is only applied to non-MIME messages. To
adjust character mapping for SMTP or PostScript, examine the
sample resource file PM-CHAR.R in RESOURCE.ZIP. This new
resource format replaces the PMALTEXT.DAT file used in older
releases of PMail.
PMail 3.0 allows you to design your own mail entry forms. The
facility is complex but powerful - it is not envisaged that
average users will design their own forms, but rather that
someone with some programming experience will develop forms
for the whole site.
Several sample forms are provided with PMail 3.0 in the file
RESOURCE.ZIP, along with a complete reference, FORMS.TXT which
goes into the data structures and layout of a form file. You
may use or customise the sample forms as you wish - they are
reasonably well-commented and in when read in conjunction with
FORMS.TXT are fairly clear.
Forms are made available in PMail via the PM-MENU.RSC resource,
discussed above. If you develop forms which you find useful,
you are encouraged to make them available to all PMail 3.0
users by whatever means you find most convenient, including
the PMail user group at [e-mail].
PMail 3.0 lets you create your own address lookup service and
tie it into the <F2> local userlist key. Your program is run
by PMail and passed (among any other parameters it might need)
the name of a file. If the user selects any addresses using
your program which need to be pasted into the current address
field in PMail, you must write them into the file, one per
line. On return, PMail will scan the file adding any addresses
it contains to the field.
Adding your own lookup service to PMail 3.0 is done via the
PM-MENU.RSC resource file, discussed earlier in this topic.
Examine the sample PM-MENU.R file for an example of how you
might implement this at your site.
PMail 3.0 allows you to add a randomly-selected fragment of
text to your message signatures; this may be used to add an
enlightening, witty or other touch to your messages and can
be quite entertaining if done carefully and in good taste.
Previous versions of PMail implemented variable signatures
using a file called QUOTES.PMS in the user's home mailbox.
Under PMail 3.0, the file is a resource file compiled with
the ResCom compiler, called RQUOTES.PMS. A sample RQUOTES
file is provided in source form as RQUOTES.R in the
RESOURCE.ZIP file provided with PMail 3.0. To use it, add
your own quotes in the proper format (see the sample for
more discussion of this), then compile using the command
ResCom rquotes.r
. Once compiled, you will have to rename
the resulting RQUOTES.RSC file to RQUOTES.PMS and copy it
into your home mailbox.
A variable signature is activated when PMail encounters the
two characters
 in your signature file.
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 an Internet 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 via an Internet mail transport (if present)
    will always have to be overridden (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.
Default workgroup:
    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.
Local delivery:
    This option only has meaning at sites where both MHS and an
    Internet gateway are used simultaneously. If this flag is set
    to 'Y', then MHS will be used for any local mail - that is,
    PMail's own delivery agent will be effectively disabled.
    So, where an address such as "DAVID" would usually be taken
    as a local PMail address, if this flag is set, then PMail will
    treat it as an MHS address instead.
    This option does NOT cause PMail to attempt local MHS delivery
    without MHS - PMail will never do this: MHS MUST be running on
    your system for any MHS delivery to occur.
SMF-71 available?
    Set this flag to 'Y' if you are using an SMF-71 transport such
    as NetWare Global Messaging, or MHS v2.0. For MHS 1.5, set it
    to N.
UTC Time value
    Enter here the time offset of your area from GMT, expressed as
    a positive or negative 4-digit value; New Zealand, for instance
    is 12 hours ahead of GMT, so you would enter +1200 here. MHS 1.5
    does not require this field to be completed.
Use SMFSEND
    If set to 'Y', then PMail will attempt to use the MHS SMFSEND
    utility to deliver mail. On some systems this will permit mail
    to be delivered locally without having MHS running, but SMFSEND
    is not the most reliable utility in the world, and performance
    using this feature may be erratic.
DOS MV path
    Enter here the path to the MHS tree - exactly the same as the
    MV environment value set at the DOS level. While PMail will
    function correctly if this value is not set, you will not be
    able to change file servers reliably from the PMail main menu
    if it is not.
PMail includes a number of user configuration options in its
preferences menu:
SMF/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. If you are using an SMF-
   71 transport, such as NetWare Global Messaging, then this field
   can contain a full address, such as "David [e-mail]".
   PMail uses this value to create the "From" field of outgoing
   messages.
MHS/SMF mailbox name
: each user has a directory in the MHS
   directory tree where new mail is stored. In almost all cases
   this will have the same name as the first eight characters of
   the user's NetWare username, but very occasionally it might
   be different. If it IS different, then PMail will not be able
   to find new mail for the user until the correct name is entered
   here.
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 Internet mail 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 three different message formats: RFC-822, the
Internet mail format; MHS SMF-70, the format of MHS 1.5, and SMF-71,
the format of NetWare Global MHS and MHS v2. 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. The only
possible exception to this is to use SMFSEND for local delivery,
but this option has variable reliability.
* 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.  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.
PMIMPORT can be operated in batch mode from the command
line using the following syntax:
   To import a text file into an address book:
      pmimport /i <textfile> <addressbook>
   To export an address book to a tagged text file:
      pmimport /e <textfile> <addressbook>
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" <[e-mail]>
Notes:   Author of Charon
;  This line is a comment - it will be ignored.
Name:    David Harris
Dept:    Pegasus Mail
Key:     DAVID
Email:   "David Harris" <[e-mail]>
Postal:  P.O. Box 5451, Dunedin New Zealand.
Street:  University of Otago, Leith Street, Dunedin.
Phone:   [phone]
Fax:     [phone]
Notes:   Author of Pegasus Mail.
Name:    Wyatt Barbee
Dept:    CBA
Key:     WYATT
Email:   [e-mail]
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 [option] <username> [parameter]
     -v: view user's or users' extended rights
     -d: delete user's extended rights
     -l: set user's local forwarding address to [parameter]
    -l-: clear user's local forwarding address
     -i: set user's Internet forwarding address to [parameter]
    -i-: clear user's Internet forwarding address
     -f: set user's address synonym to [parameter]
    -f-: clear user's address synonym
  -w[-]: allow/do not allow user to edit extended rights
  -a[-]: enable/disable delivery even if autoforwarding
  -m[-]: enable/disable mail delivery altogether
  -c[-]: honour/refuse requests for confirmation of reading
  -n[-]: turn on/turn off message arrival broadcast messages
  <username> may contain wildcards (* and ?)
  Only one of -v, -l, -i or -f may be used in one invocation.
  Address synonyms are only valid when using Charon 3.5 or later.
  If no option is present, the user is granted extended rights.
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.
PRebuild rebuilds the index file for a damaged PMail folder.
Prebuild assumes that the .PMM file (which contains the
actual text of the messages in the folder) is intact, and
regenerates the index from it.
Although PRebuild is quite safe to use, some information
(flag fields recording the Read/Replied/Forwarded status
of the message) is lost, so it should be used only when
necessary, and not routinely.
UNCONFIG removes the Bindery Property PMail creates to store
its configuration information. Very occasionally you may find
that this property has somehow become corrupt (a good symptom
to look for is that a Yes/No value in PCONFIG behaves as if
set to 'Y', even when you set it to 'N').
In such cases, run UNCONFIG to remove the old property, then
run PCONFIG again to reinstall a new, correct property.
UNCONFIG has no effect on user-defined gateways or on extended
features granted to users. It only affects the configuration
PMail uses for Charon, MHS, and inter-server delivery.
NMAIL is an enhanced replacement for PMail's NEWMAIL
program, written by Lars-Kaare Skjoerestad and included
with his permission. NMAIL provides comprehensive and
extremely configurable listings of your new mail from
the DOS command line.
For more information, please read NMAIL.DOC.
A listserver is a program which monitors incoming mail
and automatically forwards it to members of a specific
distribution list.
PMail 2.3 includes important modifications which allow
it to act as a simple but functional list server. There
are four new NewMail Filtering Actions -
Send Text File
Send Binary File
Add To List
 and
Remove From List
which assist in this, and, more importantly, new mail
which arrives while the new mail list is open will be
filtered (it hasn't been in the past). This means that
you can create a set of rules to handle incoming traffic,
then leave the new mail window open on a machine
somewhere, and PMail will take it from there, applying
the rules to each message as it comes in.
Another new feature in rule handling in 2.3 will help
as well: if the first character of the text to match in
a rule is a caret (^) then PMail will require an EXACT
MATCH on the string, instead of the substring match it
usually does (ie, if the field contains the string at
all). So, if you enter ^SUBSCRIBE as the text to match
for a rule, then PMail will only activate the rule if
the field contains ONLY the word "Subscribe". PMail
ALWAYS ignores case when matching, whether or not you
ask for an exact match.
ONE RESTRICTION! Once there are more than 75 messages
in the newmail folder, PMail no longer performs checks
for new mail in the background. As a result of this,
the rules you use to implement a listserver should
always ultimately move the message out of the new
mail folder or delete it.
Here's a sample set of filters you might use to set up
a simple list.
  Subject contains SUBSCRIBE:
       * Forward to list moderator
    or * Add sender to mailing list
       * Move message to subscription folder
  Subject contains UNSUBSCRIBE:
       * Forward to list moderator
    or * Remove sender from mailing list
       * Move message to subcription folder
  Subject contains FAQ:
       * Send the text file C:\MAIL\FAQ.TXT
       * Delete or move the message.
  Subject contains ARCHIVE:
       * Send the file C:\MAIL\ARCHIVE.LIS
       * Delete or move the message
   Subject contains anything (*) - default rule
       * Forward the message to the list
       * Move the message to the archive folder
    or * Append the message to the archive file,
         then delete it.
Note the order of the rules - it's quite important
that you establish the sequence correctly. Remember
that rule processing stops as soon as a message is
deleted or moved.
PMail can be used from the Command Line using the following syntax:
PMAIL
 -t <to_address>     To: address for message
        -f <[@]filename>    Name of file to send
        -s <"Subject">      Subject (optional, must be quoted)
        -c <cc_address>     Cc: address for message (optional)
        -b                  Indicates that <filename> is binary
        -l <message_flags>  See below for more information
        -p <pref_server>    Server to use (must be logged in)
        -u <username>       NetWare username for this session
        -a                  Force standalone operation
        -r                  Process rules only, then exit
Options may be specified using either '/' or '-' and may be freely
mixed, although -r only works with -[apu]. Spaces must appear
between options and parameters. The -u option depends on your having
rights to the specified user's mailbox and and may be subject to
other restrictions at your site.
The -l flag is used to indicate message flags such as "urgent" or
"copy to self": it consists of a string of
 characters:
whose meaning depends on their position in the string. A
 in any
position stands for "Default".
   Character 1:   Copyself flag
   Character 2:   Confirmation of reading flag
   Character 3:   Confirmation of delivery flag
   Character 4:   Urgent flag
   Character 5:   No-signature flag
Example:  The command line switch "-l YDYNN" should be read as:
   Keep a copy to self     -    Yes
   Confirm reading         -    Default
   Confirm delivery        -    Yes
   Message is urgent       -    No
   Omit signature          -    No
Example:  The command line
   PMail -t [e-mail] -s "Testing" -f message.txt
Sends the file MESSAGE.TXT to [e-mail] as a message with
the subject field set to "Testing".
Example:  The command line
   PMail -u BETTY -t JANE -f message.wp5 -b -c BOB -s "Report"
Sends the file MESSAGE.WP5 as a binary attachment to Jane with a
copy to Bob with the subject set to "Report", and does so from
Betty's mail account.
Some sites have reported problems sending mail. There's
no general solution, and all the problems appear to be
to do with subtleties in the way different versions of
NetWare interpret Trustee rights. What makes these
problems particularly frustrating is their rarity, and
the fact that they are almost always unreproducible at
other sites.
One I've had reported a couple of times involves sending
mail from a 3.11 server to a 2.15 server. The mail user-
code has been correctly setup on the 2.15 server, but
PMail reports "Unable to create container file" errors.
In this case, I've found that granting the mail usercode
S rights in the 2.15 SYS:MAIL directory (remember: S
means "Search" under 2.15, not "Supervisor") seems to
fix it, although I don't know why.
Other problems often involve curiosities in the NetWare
Bindery, particularly after upgrading a 2.15 server to
3.xx. In this case, running BINDFIX often cures the
problem.
As a last resort, run UNCONFIG (from this archive) and
then re-run PCONFIG to setup your server.
Pegasus Mail is free software, and is provided with enough online
help and documentation to be easily usable, but no full manual is
provided with it.
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$150.
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$325.
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$1250, 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. Manuals are always sent
via EMS (Express Mail System) couriers at no extra cost.
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.
(or Fax [phone])
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. The cost of your manual license
includes shipping by courier (EMS).
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...
I will accept payment by telegraphic transfer, but you
should be aware that there are some very particular
conditions you MUST meet for me to be able to do so.
Telegraphic Transfer Checklist:
------------------------------
*  Your bank must not deduct any fees from the amount
   invoiced.
*  Transfer to: The National Bank of New Zealand,
   Dunedin North Branch, account 060-909-0106632-13.
   The account name is "David Harris Pegasus Mail".
Your bank MUST ONLY TRANSFER TO MY BANK!!!
 If your
   bank transfers to me via any other bank in New
   Zealand, it will incur processing fees at this end
   which I will not accept.
If your bank cannot trans-
   fer directly to the National Bank of New Zealand,
   please pay by cheque. PLEASE ENSURE THAT YOUR BANK
   UNDERSTANDS THIS CONDITION!
 In particular, transfers
   via the Westpac Bank in New Zealand will be rejected
   outright.
*  Please make sure that your bank states my invoice
   number in the transfer narration, so I can credit
   the remittance against your invoice.
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.
We can accept payment for Manual orders on any valid VISA or
Mastercard. If you wish to pay this way, please note your
card number, expiry date, and the name on the card on the
order form.
Special Conditions:
*  Credit card payments attract a 2.5% surcharge which will
   be automatically added to the voucher.
*  The amount you are billed will probably not be exactly
   the amount on the order, because I have to submit the
   voucher to the VISA Centre converted to New Zealand
   dollars. I will use the USD conversion rate which
   applies on the day your order is processed.
If you have purchased a previous version of the Pegasus Mail manual,
you can upgrade it to the current version for
US$125
, 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$75
 on a site
license for any other version of the system.
       Press <F10> and choose "Edit" to fill in this order form
 Please read "Terms and Conditions" at the end of this form carefully.
         +--------------------------------------------------+
         |         O R D E R   F O R M,   v 3 . 0           |
         |              for PMail/DOS Manuals               |
         +--------------------------------------------------+
 Ship to:                            Bill to:
[                            ]      [                               ]
[                            ]      [                               ]
[                            ]      [                               ]
[                            ]      [                               ]
[                            ]      [                               ]
Date this order was mailed          [   ] Day  [   ] Mon  [   ] Year
What is your purchase order number  [                               ]
 or: Credit card type (tick one)    [   ] Visa [   ] Mastercard
     Card number (print carefully)  [                    ] exp: [   ]
     Name shown on card             [                               ]
Number of invoice copies required   [   ]
Manual format required (tick one)   [   ] A4   [   ] US-Letter
Internet e-mail address of contact  [                               ]
Fax number of contact               [                               ]
(Order status and update information cannot be sent if you do not
provide either a contact e-mail address (preferred) or a fax number).
Please supply the following items:
----------------------------------------------------------------------
[  ] 5-copy manual license for PMail/DOS @ US$150 . . .  US$ [       ]
[  ] Site-licensed manuals for PMail/DOS @ US$325 . . .  US$ [       ]
[  ] Site bundle - PMail/DOS and WinPMail @ US$500  . .  US$ [       ]
[  ] Annual upgrade license @ US$1250 . . . . . . . . .  US$ [       ]
[  ] Update from a previous license to 3.0 @US$125  . .  US$ [       ]
[  ] We already hold a PMail manual license - please give us a
     US$75 deduction from a site license purchase (does not
     apply to purchases of 5-copy licenses, upgrades or bundles).
----------------------------------------------------------------------
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 fax it and your PO number to: ([phone].
Shipping via EMS courier is included in the price of any option.
Please allow 2-3 weeks for your order to be processed.
-------------------- Terms and Conditions ------------------------
"Site license"
A site license for WinPMail manuals provides you with one master
copy of the manual and a license permitting you to make an unlimited
number of copies of that master for use at one site. A "site" is
defined as the extent of an organization in one metropolitan area,
so if you have four offices in one town, one site license will cover
them all. Only ONE organization may hold a site license - you may not
distribute copies of a site-licensed master outside your organization.
Note that State or National Governments do not consitute organizations
for the purposes of this definition. Site licensed manuals include
ASCII and RTF versions of the manual on diskette.
"5-copy license"
You receive a single master copy of the manual, and a license
permitting you to make up to five copies of that original for use at
one site (as defined in "Site license" above).
"Annual update license"
A recurring site license for all versions of Pegasus Mail, including
those released during its lifetime. One annual update license covers
a single site (as defined above) for one year for all versions of
Pegasus Mail. Updates are sent out automatically.
"Media:"
All manual licenses include a diskette with the most recent version
of the Software.
Prepayment:
If you prepay your order, your payment will not be presented until
the day your manual is shipped.
Credit terms:
Our terms for payment on invoice are STRICTLY net 30 days. No
monthly statement is issued - we require payment on invoice.
Credit card payments:
* A 2.5% surcharge applies to credit card payments
* Credit card payments will be converted to New Zealand dollars
  using the prevailing exchance rate on the date your manual is
  shipped to you. The amount you see on your credit card statement
  will probably not be exactly the amount shown on the order form
  above.