19.0 SPITFIRE Net-Mail Capabilities

Source: SPITFIRE.DOCEdition: searchable Web reading editionPresentation: historical wording retained
19.0 - SPITFIRE NET-MAIL CAPABILITIES
        -------------------------------------

            SPITFIRE supports net-mail in three basic formats.  In the first
        format, SPITFIRE is used in conjunction with a front-end type program
        where net-mail messages are imported and made available to callers.
        Secondly, SPITFIRE supports Postlink style net-mail which, when used in
        conjunction with a Universal Text Interface (UTI) program will directly
        import net-mail into SPITFIRE's message base.  In addition, Buffalo
        Creek Software's program, SHILOH, is a QWK based net-mail message
        system designed exclusively for use on SPITFIRE Bulletin Board Systems.

        19.1 - EXCHANGING MAIL WITH A FRONT END PROGRAM
        ------------------------------------------------

            Using SPITFIRE with a front-end program requires the use of such
        programs as BinkleyTerm or FrontDoor for sending and receiving
        net-mail messages.  Sysops who run their copy of SPITFIRE with a
        front-end type program will have to boot SPITFIRE using the baud rate
        of the caller as a command line parameter.  For example:

        SPITFIRE 2400

                     NOTE: The SF.BAT file included with the SPITFIRE package
                     should be used even with a front-end program.  Using the
                     SF.BAT file, the front-end program should boot SPITFIRE
                     in this manner - SF 2400. Then within the SF.BAT file the
                     SPITFIRE command would have to be followed by a %1.
                     (For example - SPITFIRE %1)

            When SPITFIRE is booted in the above manner, SPITFIRE assumes
        there is a caller and begins the process of logging the caller on.
        When the caller logs off, then SPITFIRE does not recycle to the
        "SPITFIRE ready for use..." prompt but rather terminates so control
        can be returned to the front-end program.

            It should be noted that if SPITFIRE is used with a front-end
        program, the scheduled events feature within SPITFIRE becomes basically
        inoperative since events are run while SPITFIRE is at the "SPITFIRE
        ready for use..." prompt.  However, when used in this environment,
        SPITFIRE does check when the caller logs off to see if an event is
        scheduled to run.

        19.2 - EXCHANGING MAIL USING A UTI DRIVER
        -----------------------------------------

            Certain features within SPITFIRE allow it to be compatible with
        specific net-mail drivers.

            Each Message Conference available on the BBS must be configured as
        to whether it will support net-mail.  (Refer to CONFIGURING MESSAGE
        CONFERENCE RECORDS of this manual for more detailed information.)
        When a caller enters a message in a Message Conference configured to
        allow net-mail, the caller will be prompted as to whether they wish to
        send the message via net-mail.  If the caller responds with a Y for
        Yes, the caller can send a message to someone who is not a caller on
        the BBS.  Furthermore, the message is marked as a net-mail message,
        which allows net-mail utilities, such as the BCSUTI, to go through
        and extract the net-mail messages for processing and exchanging
        with other BBS systems.  The BCSUTI serves as a conversion driver
        between SPITFIRE and the Postlink net-mail software and allows
        messages transferred between other BBS systems to be imported directly
        into SPITFIRE's existing message base.  (Sysops should refer to the
        Postlink and BCSUTI documentation for complete instructions regarding
        setting up a SPITFIRE BBS for exchanging mail with these programs.)

        19.3 - EXCHANGING MAIL USING QWK PACKETS
        ----------------------------------------

             Buffalo Creek's Software program, SHILOH, allows SPITFIRE BBS
        systems to exchange QWK mail packets with other SPITFIRE boards.
        SHILOH determines what messages should be extracted by whether the
        Message Conference are configured as net-mail conferences, whether
        the Message Conferences are included in the caller's message queue and
        by the last read message pointers for the caller in each net-mail
        conference in his/her queue.  Each Message Conference must have the
        Net ID Name configured (Refer to CONFIGURING MESSAGE CONFERENCE RECORDS
        of this manual for more detailed information) according to the Net ID
        Name assigned by the mail system the BBS is participating in.  When
        importing messages, SHILOH matches the Net ID Name with those in the
        QWK packet to be imported and those messages are imported directly into
        SPITFIRE's message base.  (For additional information regarding
        SHILOH, please refer to SHILOH.DOC.)