



              ___           _       __ __             __
             |             | \     |  |  |           |  \
 _ _   _ _   |___       _  |_/     |  |  |  _        |__/   _  _       _  _  _ _
| | | | | |  |    | |  |_  | \ \/  |  |  | |_| | |   |  \  |_ | | | | |_ |_   |
| | | | | |  |    | |_ |_  |_/  |  |  |  | | | | |_  |   \ |_ |_\ |_| |_  _|  |


                        __ __   __   __   __   ___   __  __
                       |  |  | |  | |  | |  | /     |   |  \
                       |  |  | |__| |  | |__| |   _ |__ |__/
                       |  |  | |  | |  | |  | |   | |   |  \
                       |  |  | |  | |  | |  |  \_/  |__ |   \


                                   Version 1.0



                            1996 by Sebastian Bleikamp


================================================================================



    I. Introduction:  FbMReq - What is it ??
    ----------------


FbMReq stands for File-by-Mail-Request. It is file request system that works via
netmail or e-mail. You request a file, and it will be sent to you uuencoded.
Or you can request a FAQ and it will be sent as a message.
It is not a file request system like FReq in the fidonet. There you have to call
the other system directly. Here you only have to write and receive mail.

I got the idea for this program when several people asked for a FAQ server
that worked with MM. I ever thought about writing an uuencode robot, and so
I combined both ideas: The idea of MM_FbMReqM was born. :-)

FbMReq works like Areafix. You write a message to the robot and it sends
you the results.


Copyright notice:
-----------------

This program is MAILWARE.

YOU ARE ALLOWED TO USE IT IF YOU SEND THE AUTHOR AN E-MAIL. THE PROGRAM AND THE ARCHIVE
AND ITS CONTENTS MUST NOT BE CHANGED OR MODIFIED IN ANY WAY. THE ARCHIVE MAY BE
COPIED AND DISTRIBUTED FREELY. IT MUST NOT BE SOLD, BUT MAY BE INCLUDED IN A
PD COLLECTION LIKE Fred Fishs OR THE AMINET CDs.



    II. Installation:
    -----------------

Installation is quite easy. Just copy the files to the directories where they belong,
e.g. MM_FbMReqManager.rexx to MM:Rexx/, MM_FbMReqManager.doc to MM:Docs/.
Then create somewhere a directory for the data files and one for the files to send,
e.g. MM:Freq/Data/ and MM:Freq/Files/.

MM_FbMReqManager will scan for mailareas for not sent mails.
That means, every area that shall be scanned must have the flag
TwoPassImport !!


    III. Configuration:
    -------------------

MM_MFRM is completely configured by one file: MM:Config/MM_FbMReqManager.cfg
It is an ASCII file, so edit it using a standart text editor.

Now a short description of the keywords (I think you can guess what they mean.):

#SERVERNAME     -     Name of the server, e.g. FileByMailRequestManager.
                      You can give several names here. The first one will
                      be used when answering messages.

#SYSOPNAME          - Your name.

#UUENCODE           - The uuencode command.
                      e.g.: uuin INFILE {INFILE} OUTFILE {OUTFILE} MAXBYTES {MAXSIZE}
                      NORENAME
                      The keywords {INFILE}, {OUTFILE} and {MAXSIZE} will be
                      automatically replaced.

#INDEXFILE          - The indexfile, where all files are listed with name, path,
                      sec. level and description. e.g: MM:Freq/Data/index
                      There is an example in MM:Freq/Data, where it is explained
                      how to build one.

#PASSWDFILE         - The passwordfile. All users who have an other level than
                      the standard level have an entry with name, level and
                      password here. e.g.: MM:Freq/Data/passwd
                      There is an example in MM:Freq/Data, where it is explained
                      how to build one.

#STDFLAGS           - The flags an outgoing message will have. e.g.: PVT KILL

#STDLEVEL 0         - The Level for user which are not in the password file.
                      Level -1 means that the user is locked out !

#MAXTXTSIZE         - The max. size of a textfile. Is it larger than this,
                      it will be splittet.

#MAXFILESIZE        - The ma. size of a binary file.


#TEXT_HELPFILE      - The textfiles. They will be sent as answers and contain
#TEXT_FILENOTFOUND    e.g. the files. Several replace patterns can be used.
#TEXT_WRONGPASS
#TEXT_FILELIST
#TEXT_SENDFILE
#TEXT_SENDTEXT
#TEXT_SENDSCAN

#SUBJ_HELPFILE      - The subjects of the answer messages. They can
#SUBJ_FILENOTFOUND    contain replace patterns, too.
#SUBJ_WRONGPASS
#SUBJ_FILELIST
#SUBJ_SENDFILE
#SUBJ_SENDTEXT
#SUBJ_SENDSCAN



    IV. Usage:
    ----------

When MM_FbMReqManager is started, it will scan the mailareas for
new messages which are addressed to him. Then it will answer these.

Writing messages to MM_FbMReqManager is quite easy. Its just like
writing to Areafix.

Write a test message to e.g. FileRequestManager at your system.
If you are in the password file, then add your password in the subject line.
You can use the following commands in the body:

%HELP       - And you will receive a helpfile.
%LIST       - And youll get a filelist with all files avaible
              at your security level.

%GET<xy>    - The file <xy> will be sent to you; uuencoded or as a text file.
%SCAN <xy>  - The filebase will be scanned for files named <xy> or having <xy>
              in the description. A list of these files will be sent.
%SEARCH <xy>- Like %SCAN, but the files will be sent.



    V. The indexfile:
    -----------------

The indexfile consists of one line per file.
A line looks so:

[MAGIC]|[TYPE]|[Path/Filename]|[LEVEL]|[DESCRIPION]

[MAGIC]:          The name of the file. This name has to be used with the
                  get command.
[TYPE]:           FILE or TEXT at the moment. File means binary sending,
                  TEXT message like sending.
[Path/Filename]:  The AmigaDos path and filename (e.g. "MM:Bin/MM" ).
[LEVEL]:          Security level needed to be able to download the file.
[DESCRIPTION]:    Just a short description, max. 60 charakters. (If
                  you add more, a line wrap will appear in the list.)

e.g.: "DiskInfo|FILE|Ram:Disk.info|0|Ram:Disk.info -> Testfile."




    VI. The password file:
    ----------------------


As the indexfile, the password file consists of one line per user.

[NAME]|[PASSWORD]|[LEVEL]

[NAME]:         The users name as it can be found in the MSG_FROM field.
[PASSWORD]:     The users password.
[LEVEL]:        The users level. Level -1 means he is locked out.

e.g.: "TheSysop|Secret|10000"



    VII. The replace patterns in the textfiles and subjects.
    --------------------------------------------------------

These patterns will be replaced when the message is sent.

The only important is {TEXT}. It has to stand at the beginning of a single
line. Here the message text / uuencoded file will be inserted.


The following patterns will be replaced in all the textfiles & subjects:

{SYSOP}         - the configured sysopname.
{SERVER}        - the first configured servername.

{PRGNAME}       - the program name.
{PRGVER}        - the version.
{PRGID}         - the program name + version.

{FROM}          - the processed message sender.
{FROMNICK}      - the senders first name.
{FROMADDR}      - the senders address.
{FROMWHO}       - the senders name and address - fido or e-mail.
{EMAIL}         - the processed message senders e-mail address.
{LEVEL}         - the senders security level.

{TO}            - the processed message receiver - FileRequestManager ?
{TOADDR}        - the receivers address.

{MSGSUBJ}       - the subject of the message.
{MSGDATE}       - the date.
{MSGFLAGS}      - the flags.
{MSGAREA}       - the area.
{MSGNUM}        - the number.


The following patterns will only be replaced in some textfiles & subjects, only if
the data exists:

{FNAME}         - the filename.
{FTYPE}         - the filetype.
{FPATH}         - the AmigaDos path, be careful !
{FLEVEL}        - the level to ge the file / the search level.
{FDESC}         - the file description.
{FPART}         - the current part of the file, if splittet.
{FMAXPART}      - in how many messages the file is splittet.



    VIII. UUCP & E-Mail support:
    ----------------------------

MM_FbMReqManager recognizes the REPLYADDR kludge. If it is an e-mail
address, it will use this to answer a message.
So can MM_FbMReqManager used with UUCP gateways, too.



    IX. How to contact the author:
    ------------------------------

Any suggestions or comments ?? Wanna beat the author ???

Then write to me:

    Sebastian Bleikamp
    Lothringer Weg 37a
    45481 Mlheim
    GERMANY

E-Mail:  bleikamp@mail.rhein-ruhr.de
WWW:     http://www.rhein-ruhr.de/~bleikamp/
Fidonet: 2:2448/10.131

You can write me in MM_Support.GER, too. I am sorry, I cant get the Area MM_Utils.GER.
On my Web page the newest versions of MM_PGPManager and FbMReqManager are avaible.




    X. Credits:
    -----------

Eugene Stepanoff,       for his ideas, suggestions and beta testing.
Pino Aliberti,          for his wonderful MailManager.
Siggi Weisner,          for his support of MM and its utils in Germany.
My Cat,                 which made me quiet and happy again when I was not far
                        from throwing my computer away.



    XI. History & Future:
    --------------------

SINCE v 0.7:

    ->  !!!! New index format: !!!!
        Name|Type|Path|Level|Desc
        (Before: Type|Name| ... )

    ->  Functions ok:
        HELP
        LIST
        SCAN
        SEARCH
        GET

    ->  EMail Support !!!!!
    ->  Passwd Support !!!

SINCE v 0.8:

    -> Replace Patterns !!!
       !! Other filenames for text files !!

SINCE v 0.9:

    -> Much more replace patterns !!
       Now all message infos are avaible !

    -> UUencode: MAXSIZE added !!
    -> Textfile: MAXSIZE added !!

SINCE v 0.10:

    -> Filelist will be splittet, too !

SINCE v 0.11:

    -> some more replace patterns ...

    -> now there are two different values for text and binary max.
       message size.

    -> Wrong-Password function improved: Message will be sent back.

    -> Maany bugfixes.

SINCE v 0.12:

    -> Now with a configfile !!!
    -> Configureable subjects.



FUTURE:

    -> Up to you !!! If you have suggestions, Ill include them !!!




(EOF)
