THIS DOCUMENT IS FAIRLY SHORT, SO PLEASE READ ALL OF IT BEFORE INSTALLING.


    Source code WILL be made publicly available.  It will be uploaded to
    Paul's system in AZ, Perry Alexander's in Lexington, and mine in
    Houston.  Any future independent modifications of this software, and
    redistribution of software based on this code will be coordinated
    through me, but I will not act to impede any independent progress.
    Just let me make the final call on coordinating the various
    potential inputs.   All code submitted becomes subject to the "no
    fee for use or distribution" copyright.


SYNTAX:

       FIDO

Concepts:

        1.  The gate software tracks messages in three ways.

                a.  Messages imported from fidonet are marked
                    as fido originating.  This is marked by the
                    2nd bit in the flags byte, the one after the
                    sticky bit.

                b.  The "Fido Gate" user record uses the lastread
                    pointer to indicate the last message processed.
                    No messages before this will be scanned out.

                c.  Messages output to fidonet by the gate, but not
                    yet scanned will have the node number encoded in
                    the ftsc header, and if it matches the systems
                    node number, the gate will not import it.

        2.  The gate software deletes *.msg files when the following
            conditions occur:

                a.  The message is from Qmail, ie, highwater mark.

                b.  The message has an ^APATH: nnn/xxx where nnn/xxx
                    is the node number of the gate.  ie, scanned out
                    messages originating on the gate system.

                c.  The message is an externally originated message that
                    has been imported.

        3.  Maximum message size is about 60k.  (0xF000).  It was
            picked arbitrarily.

        4.  Source code will be released with the package at the time
            of its first initial non-beta release.

        5.  Anyone may try this software out during the beta test.  I do
            ask that a netmail message be sent to me at 1:106/960.0 or
            001/060.  Please report all bugs to either of these two
            addresses.

These concepts are not up for discussion, so if you don't like'em, don't
bother using the software, it didn't cost you anything anyway.




System Assumptions:

        1.  I am making the assumption of Binkley and Qmail v1.00
            as the primary interface software on the *.pkt and *.msg
            side.  I have attemted to adjust it for Qmail 1.3x and
            SquishMail *.msg highwater marks as well.

        2.  Message bases will be initialized properly on the GT
            side.  (I'm not adding DRAM code to my programs for
            several reasons, one of which is that I program
            religiously in large model.)

        3.  You are using GT Power version 16 or higher.

        4.  You currently have a valid and functioning fidonet
            system.

        5.  That there is a user named "Fido Gate" with an access
            level high enough to prevent accidental deletion from
            inactivity.  (ie, be careful when you delete users with
            the sysop.exe program)




Setup instructions:

        1.  Configuration file must be in GTPATH: "fidogate.cnf"

                line 1: fidonet z:net/node.point
                line 2: fidonet origin line text

            See the example included.

        2.  Login to your bbs using the username of "Fido Gate"
            Access level does not matter.  Or use the SYSOP.EXE
            program provided by P&M software.

        3.  Join "Fido Gate" to the message area you wish to gate.
            Either by selecting that area from the BBS or by joining
            with the SYSOP.EXE program.  (be careful when deleteing
            users that you do not accidentally delete Mr. Fido Gate.)

        4.  Add the area to your configuration file according to
            the syntax:

                AREA=<mode> <gt directory>  <fido directory>

                AREA=nnnn must be in upper case and have no imbedded spaces.

                Directory entries *MUST* have a trailing backslash.

                Available operating modes:

                    0001    Strip high-bit, and ftsc illegals and
                            .ORIGIN/Route: gtnet identifiers.

                    0002    Allow high order ascii to pass through
                            but kill control A characters.

                    0009    Process fidonet netmail message.  Use
                            the full zone:net/node.point format on
                            line 1, ie, line 1: 1:106/960.0.

                            Zone and point data are now properly
                            exported into the fidonet message base,
                            so anyone using this outside of zone
                            one, PLEASE route me netmail message
                            if you can.

                    Any other will do no modifications to the text
                    of the messages processed.

                    Leading zeros are NOT optional.

        5.  Configuration file must have an "END" command after the
            listing of areas, again, case IS critical, "end" will not
            work.



    Quick note: (new to 1.16)

        1.  Changed MSGID and INTL fields to top of message text

        2.  Added LANPATH functionality

        3.  Added error level exits
                0 = nothing happened
                1 = import only
                2 = export only
                3 = both import and export

        4.  Added compatibility for arcmail attach transfer method.

        5.  Have attempted to add rudimentary file sharing for the
            USER.DAT file...




MARKALL:

        SYNTAX:

                MARKALL  <msgpath>


        This little program will mark an entire message base as
        fido originated so that you can convert to the new driver
        with an existing message base, without having to worry
        about duplicates.








                              DISCLAIMER


I disclaim everything.

Simple nuff.

