This program was an automatic BBS list program, accessible via Fidonet
.msg-style messages.  You could request a list, update the list,
automatically send lists via batch files, and things like that.



Some help for installing the BBSLIST program:
---------------------------------------------

The program may be run from any directory and the config and data
files may be located anywhere (even separately from each other,
which seems silly).  The only argument you pass to the program is
the filespec of the config file, i.e.:
    \bbs-util\bbslist \bbs-util\bbslist.cfg

The config file is a text file which contains (line by line):
    - The spec of the help file, which is file-attached to users
    - The spec of the info file, which is file-attached to users
    - The spec of the data file (indexed), which the program maintains
    - The spec of the distribution list file (indexed), which the program maintains
    - The spec for the output (text) bbs list
    - The directory spec for your netmail directory (.MSG-style!)
    - The spec of the header file to be prepended to the bbs listing
    - The spec of the trailer file to be appended to the bbs listing
    - The authorization password, which users include as the subject
    - A debug string:  If 1st char is 'Y' then debug mode is on.
                       If 2nd char is 'Y' then received messages are deleted.
                       The other 6 characters are unused; don't use them!

The errorlevels returned by the program are:
    #define ERRORLEVEL_SUCCESS       0
    #define ERRORLEVEL_LIST_CHANGED  1
    #define ERRORLEVEL_BAD_PARAMETER 2
    #define ERRORLEVEL_CONFIGURATION 3
    #define ERRORLEVEL_ENGINE        4
    #define ERRORLEVEL_FATAL         5

    Whenever the program exits with the _ENGINE errorlevel, the source
    of the error may be found in the accompanying file I_F_ENG.H.

If you don't want to support the distribution list function, or want to
use the errorlevel returned by the program in conjunction with TICK or
a similar program to send out updates, then simply place a line in the
batch file which looks for and deletes the distribution data file if it
exists.  The end result is that any distribution list entries added will
exist only during the current program execution, then be deleted.

I imagine a batch file like so:
    \bbs-util\bbslist.exe \bbs-util\bbslist.cfg >>\bbs-util\bbslist.log
    if errorlevel 2  goto bbslist_error
    if errorlevel 1  \tick\hatch etc. etc. etc....

Known bugs:
    The header message should have a blank line at the end.


---------------------------------------------------------------------------
Please direct comments, wish lists, and bug reports to:

Alton Moore
Fidonet 1:397/5264 (NEC)
WWIVnet 1@1042

---------------------------------------------------------------------------

Update history:

Version 1.00 -- 06/01/92 -- Original
        1.01 -- 06/29/92 -- Added info. file
        1.02 -- 07/29/92 -- Added distribution list filespec and debug/delete
                             flags to the configuration file (2 lines total).
                             Program was rewritten to handle multiple functions
                             per message (separated by a blank line) and
                             generally just respond more cleanly.