UPDATE ³ JetMail v1.05 (c)Copyright 1991 by DJ Chuang
       ³ .QWK-Compatible Mail Door for SPITFIRE 3.x

My goal of a working 1.00 wasn't realized.  Some critical problems were
discovered on certain systems, and they've been corrected.  Hopefully
any future updates will just be cosmetic changes.  (Definitely a
distinct disadvantage trying to develop a Spitfire software apart from
running a Spitfire board myself.)

You will need the JET100.ZIP distribution files for the complete JetMail
package.  To upgrade to JetMail version 1.05, just overwrite JETMAIL.EXE
with the new JETMAIL.EXE dated 8/21/91 17:39.  This update is originally
distributed by the author as JET105U.ZIP, but the distribution boards
are encouraged to incorporate it into JET105.ZIP accordingly.

Version 1.05 Changes

  -  Added record-locking mechanism for processing REP packets for
     multi-node operation.  If you specify the .CNF configuration file
     on the JetMail command line, JetMail will be put in multi-node mode
     automatically, using this record-locking mechanism.
     SHARE must be loaded!  Thanks Bob Zimmerman.

Version 1.04 Changes

  -  Late note:  CKIT 2.0 is 'hard-coded' to use DOOR.SYS to initialize
     its communications routines.  For auto-pilot mode and local use of
     JetMail, you need to rename AUTOJET.SYS (or LOCAL.SYS) to DOOR.SYS.
     (if you fail to do this, JetMail will return with Error opening
     JetMail door, code 3)

  -  Compiled with CKIT release version 2.0 (by Rickie Belitz), an
     excellent door toolkit.

  -  JetMail was not processing the PORT:F:x or PORT:0aaa:i parameter.
     This caused double/triple echo in parts of the door.  Fixed.

  -  Makes sure that memory is properly deallocated during REP
     processing (it was potentially possible to eat up all available RAM
     if the user were to upload many bad .REP packets).

  -  Specify a WORKDIR parameter in your JetMail .CNF configuration file
     if you are using XFERTYPE=JET and the default sample transfer batch
     files in JETXFER.ZIP, to make sure all 5 parameters are passed
     properly.  [I recommend C:\WORK, or in a multinode environment, use
     C:\WORK<x>, where <x> is node number ]  If JetMail creates its own
     temporary directory (when WORKDIR is unspecified), the path names
     being passed to JETUP<x>.BAT accumulate, and becomes too long for
     DOS to properly handle it.

  -  Codes defined for "* Error Opening JetMail DOOR":
        1   Unable to open BBS system file (pcboard.sys,door.sys etc)
        2   Problem reading BBS system file
        3   Unrecognized BBS file type
        4   Unable to open pcboard USERS file
        5   Invalid User record or problem seeking to user record
        6   Problem reading USER record
        7   PORT command syntax error
        8   Fossil driver specified but no Fossil driver installed
        9   Memory allocation problem

Version 1.03 Changes

  -  Reply packet processing was messed up badly in version 1.02,
     resulting in locked up computers.  SORRY!  I'm handling one bug at
     a time these days, to keep the variables down.  I need to get
     together a checklist to test new code before making official
     release, especially since I can't test some of the features
     personally locally.  Your patience is appreciated.

Version 1.02 Changes

  -  My attempt to insure share-compatibility in my code caused a BIG
     problem with remote transfers.  They became "disabled", and of
     course I can't test that locally.  Now it's fixed.  Thanks Steve
     Newman.

  -  I misspoke in the JETMAIL.FIX documentation.  7000 bytes is not
     quite enough for processing a 99-line message, 8000 bytes is more
     like it.  I've changed default message "buffer" to be dynamically
     allocated during message scan, so you can gain 8K more memory for
     'ZIP' and 'DSZ' shells.  Will be doing research on swapping the
     code out for future upgrade.

Version 1.01 Changes

  -  Double checked code to make sure JetMail is share-compatible for
     all files that need to be shared.  Found two instances that slipped
     through - in the new files scan and the transfer protocol routines.

  -  The word wrapping algorithm no longer 'butchers' the MegaMail
     quoting boxes.

  -  Memory was being clobbered on some systems during messages scan
     (resulting various error messages such as "Not Enough Memory", or
     "Unable to write to MESSAGES.DAT").  This has finally been tracked
     down and corrected.  Thanks Steve Newman.

  -  During local JetMail use, print .QWK packet name used doing an
     'incremental' copy command.

  -  Documentation error/clarification:  JetMail will not allow a
     private post in a conference that only allows public messages,
     regardless of configuration parameter DONTPOST.  The DONTPOST
     parameter only determines JetMail's action upon attempted posts to
     invalid conferences.

DJ Chuang, JetMail author