Hall of Fame/HallofFameCDROM.cdr/qbbsetc/rqsex140.lzh/RQSEX140.DOC

Text File | 1990-12-10 | 37KB | 756 lines

           ┌───────────┐         ┌───────────┐        ┌───┐     ┌───┐
           │▒▒▒▒▒▒▒▒▒▒ ├─────────┴┐▒▒▒▒▒▒▒▒▒ ├────────┴┐▒ └┐   ┌┘▒▒ │
           │▒▒┌────┐▒▒ │▒▒▒▒▒▒▒▒▒ │▒▒┌──────┬┘▒▒▒▒▒▒▒▒ │▒▒ └┐ ┌┘▒▒ ┌┘
           │▒▒└────┘▒┌─┘▒┌─────┐▒ │▒▒└──────┴┐▒ ┌──────┴┐▒▒ └─┘▒▒ ┌┘
           │▒▒▒▒▒▒▒▒▒└─┐▒│     │▒ │▒▒▒▒▒▒▒▒▒ │▒ └────┐ ┌┘▒▒ ┌─┐▒▒ └┐
           │▒▒▒┌───┐▒▒ │▒│     │▒ ├───────┐▒ │▒▒▒▒▒▒ │┌┘▒▒ ┌┘ └┐▒▒ └┐
           │▒▒▒│   │▒▒ │▒│     │▒ ├───────┘▒ │▒ ┌────┘│▒▒ ┌┘   └┐▒▒ │
           │▒▒▒│   │▒▒ │▒└─────┘▒ └┐▒▒▒▒▒▒▒▒ │▒ └─────┴┐▒ │     │▒▒ │
           └───┘   └──┬┘▒▒▒▒▒▒▒▒▒▒ └┐───────┬┘▒▒▒▒▒▒▒▒ │──┘     └───┘
                      └─────────────┘       └──────────┘







                  RemoteAccess/Quickpoint Mail/SuperBBS eXpress
                                  Version 1.40
                Program CopyRight (C) 1989, 1990 by Mike Ratledge
      Documentation written and all rights reserved by Ed Meloan of 360/1

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 1   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘






            ┌─────────────────────────────────────────────────────┐
            │  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒  Table of Contents ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒  │
            └─────────────────────────────────────────────────────┘




                What is RQSEX ............................... 2

                Getting Started ............................. 3

                Setting Up RQSEX for QuickBBS/SuperBBS....... 4

                Setting Up RQSEX for RemoteAccess ........... 5

                Processing INBOUND Mail ..................... 7

                Setting Up The QMXSETUP.CFG File ............ 8

                A Few Hints ................................. 10

                A Short Check List .......................... 11

                Using RQSEX on Your BBS ..................... 11

                Odds & Ends ................................. 13

                Credits ..................................... 15

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 2   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘





                         ┌─────────────────────────┐
                         │ ▒▒▒  What is RQSEX  ▒▒▒ │
                         └─────────────────────────┘




RQSEX is An exciting way for your callers to get all the messages they are
interested in and =READ THEM AFTER THEY LOG OFF=.  The  RQSEX system allows
your users to do the following:

         1.  Custom select the Message Areas =THEY= want to read

         2.  Collect the new messages from these areas =AND= ALL
             messages addressed to them even in areas they don't select.

         3.  Pack them in an archive and send them to their computer

         4.  Lets your user read them while off-line, freeing your board
             for the next caller!!

         5.  The companion XRS Response system gives your caller an
             EXCELLENT full-screen editor that allows them to read,
             reply and edit all their messages WHILE OFF-LINE!

         6.  Pack their replies and send them back to this BBS where
             RQSEX will automatically place them in the correct message
             areas just as if the user had written them there.











┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 3   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘




            ┌─────────────────────────────────────────────────────┐
            │  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒  Getting Started  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒  │
            └─────────────────────────────────────────────────────┘



Read the following information and you'll be on your way to providing your
RemoteAccess/QuickBBS/SuperBBS users with this exciting new feature!

If you're already running ECHOMAIL - then you are well on your way already!
Since RQSEX depends on an AREAS.BBS file to know where to place incoming
messages, you'll need to have that file set up.  One point here is that you
=MUST= setup names for EVERY message area...  Even ones which normally do not
handle ECHOMAIL.  This allows your present echomail processing to properly toss
LOCAL as well as ECHO messages into the correct message areas.

[A note here that while RQSEX can handle AREAS.BBS area names in lower case,
some mail tossers can not!  All area names should be in UPPER CASE.]

The XRS program requires group zero to be a local message area, and therefore
XRS always shows "00 LOCAL" as the first available group.  This 00 area is
inherited from the TCOMM program, for which XRS was originally written, and
really has no function in the R/Q/SBBS environment.  You should setup the main
general local area of your BBS with the area name "LOCAL", so that the mail
tosser will place the inbound traffic into the correct area.  This can be ANY
message area number as long as it is named LOCAL in AREAS.BBS. Since there is
no 00 area, as there is in TCOMM, you will want to use one of your regular
area numbers.  This feature is required because all your users may not have
access to NetMail - they cannot send private message back to your BBS (XRS
will =ONLY= allow private status on NetMail, Local or in response to a private
message)!

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 4   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘
         ┌────────────────────────────────────────────────────┐
         │  ▒▒▒  Setting Up RQSEX for QuickBBS/SuperBBS  ▒▒▒  │
         └────────────────────────────────────────────────────┘

RQSEX is compiled in TWO versions.  Select RQSEX.EXE for use on XT (8088/8086)
systems and RQSEX286.EXE for V20/80286/80386 systems and place the correct
version in your QuickBBS/SuperBBS system directory.

RQSEX must be set up as a Type 15 external program.  It will NOT work as a
type 7 option.  Here are the steps to set RQSEX up as a type 15 menu option:

Decide on an error level and add the following lines to your QuickBBS or
Mailer BAT file.  Let's assume we decide to use 98 as our level.  We would set
up a type 15 menu option with 98 as the optional data.  Do not type the
comments that are in brackets.  For SuperBBS "SET SUPER=Y" in the environment.

:After_Quick
   If errorlevel 98 goto RQSEX    (ADD this line)
   If errorlevel 5 goto Both      (You probably already have this line)
   If errorlevel 4 goto NewEcho   ( "     "        "     "     "    " )
   If errorlevel 3 goto NewNet    ( "     "        "     "     "    " )
   Goto Loop  (or whatever you call your starting section of BAT file)


Since RQSEX has its own internal FOSSIL handling and carrier detection, you
will not need nor should you use redirection devices such as CTTY or GATEWAY
or carrier monitors such as WATCHCD.  Please =DO NOT= use them.  All you will
need in your BAT file will be something like this:

:RQSEX
   RQSEX286 (or RQSEX.EXE)
   QuickBBS -R -E0
   Goto After_Quick

       ┌─────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒         TWO IMPORTANT NOTES !!        ▒▒▒▒▒▒▒▒▒  │
       └─────────────────────────────────────────────────────────────┘

You =MUST= have the popular archiving programs PKARC, PKZIP, and LHARC as well
as a recent version of ZMODEM AVAILABLE IN YOUR PATH STATEMENT!!  We cannot
emphasize this too strongly.  Having them in the QuickBBS sub-directory is not
necessarily enough if you don't have that sub-dir in the path statement!

RQSEX uses DSZ.COM to provide external protocol support.  It does not select
the COM: port for DSZ!  If you use COM2: (or anything other than the default
COM1: address) you must place the following command immediately before RQSEX
in your batch file: SET DSZPORT=2.  "SET SUPER=Y" selects SuperBBS support.

SET DSZPORT=2 would tell DSZ to use COM2:, for example.  You should also place
a similar command after RQSEX without the '2' (but no spaces after the '='
either!), and you will free up the environment string space it uses.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 5   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘


       ┌─────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒   Setting Up RQSEX for RemoteAccess   ▒▒▒▒▒▒▒▒▒  │
       └─────────────────────────────────────────────────────────────┘



RQSEX is compiled in TWO versions.  Select RQSEX.EXE for use on XT (8088/8086)
systems and RQSEX286.EXE for V20/80286/80386 systems and place the correct
version in your RA system directory. If running more than one line, place a
copy in EACH line's directory (\RA\LINEx) as discussed below...

Complete file sharing and record-locking for updates is enabled *if* DOS
"Share" is detected.  Assuming Share *is* detected, RQSEX looks for "TCNODE" in
the DOS environment to determine the node number the user is on (i.e. "SET
TCNODE=2" for node 2, etc), and then uses BAT2MAIL.XRS, MAIL2IDX.XRS,
SUMMARY2.XRS, USER2.XRS & AREAS2.XRS, all of which get archived into the file
BAT2MAIL.* unless it's a local SysOp logon and SysOpOut is in affect.

If you run multi-line RemoteAccess, you *must* start the program from the
proper \RA\LINEx (or whatever you call them) sub-directory.  It is NOT
necessary to duplicate the files used by RQSEX in each line's directory.
Here's why...

RQSEX checks for the "RA" set in the DOS environment, and if found, looks in
that subdirectory for the CONFIG.RA file.  Assuming "RA" is set, RQSEX uses
that file plus the MESSAGES.RA. It then uses the path found in CONFIG.RA to
find the message databases.

The following files are looked for in the current sub-dir, then in the System
Path and finally in the Messages Path.

QMXSETUP.CFG, USERS.BBS, EXPRESS.BBS and FLSEARCH.QMX

You can have specialized nodes or let a single set of control files be used.
The "QMX_CONF.SYS" file (user defaults) is first looked for in the current
sub-directory, then in the System (*not* messages!) sub-directory for RA.
This way you can have separate paremeters/configuations and users on each
node if you wish, or one configuration stored in the System directory.

RQSEX will look for DORINFO1.DEF and EXITINFO.BBS in the sub-directory where
RQSEX is located and =ASSUMES NODE 1= so single-line systems with Share
enabled are not treated like networks and the use of the TCNODE environment
variable is only required for true multi-line systems.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 6   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘


Using file sharing and record-locking, multiple users can all access the
databases =AND= RQSEX at the same time.  Full support for the "RemoteAccess
BBS" software is included.  RQSEX looks to see if RA has been set in the
environment and if found, uses the RA Configuration files for information
about message area security and access. It also notifies XRS 3.12 and later to
tag the tear and origin lines with the proper RAX identity.  Please NOTE that
although RQSEX uses the MESSAGE.RA file, it will still need an AREAS.BBS file
since the MESSAGE.RA file does =NOT= contain the exact ECHOMAIL AREA NAMES!
You do not need a copy of AREAS.BBS in each line's sub-directory since RQSEX
will look in the system and message directories if it doesn't find the file in
the current one.

RQSEX is remarkably simple to setup on the RemoteAccess system.  A menu type 7
(shell) works VERY well!  Add the *M and you can swap RA out of memory if you
are multitasking and memory space is limited.

Since RQSEX has its own internal FOSSIL handling and carrier detection, you
will not need nor should you use redirection devices such as CTTY or GATEWAY
or carrier monitors such as WATCHCD.  Please =DO NOT= use them.  All you will
need in your menu type 7 OPTIONAL DATA is the following line:

   C:\RA\RQSEX286 *M (or RQSEX.EXE *M)

That's it!  No elaborate BAT files are needed!  Including the C:\RA\ path
will allow you to use a single copy of the RQSEX program, regardless of the
number of lines you may be running.  If you do NOT include the path, you will
need a copy of RQSEX in the directory for EACH line.


       ┌─────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒         TWO IMPORTANT NOTES !!        ▒▒▒▒▒▒▒▒▒  │
       └─────────────────────────────────────────────────────────────┘

You =MUST= have the popular archiving programs PKARC, PKZIP, and LHARC as well
as a recent version of ZMODEM AVAILABLE IN YOUR PATH STATEMENT!!  We cannot
emphasize this too strongly.  Having them in the sub-directory with RQSEX is
not necessarily enough if you don't have that sub-dir in the path statement!

RQSEX uses DSZ.COM to provide external protocol support.  It does not select
the COM: port for DSZ!  If you use COM2: (or anything other than the default
COM1: address) you must place the following command immediately before RQSEX
in your batch file: SET DSZPORT=2

SET DSZPORT=2 would tell DSZ to use COM2:, for example.  You should also place
a similar command after RQSEX without the '2' (but no spaces after the '='
either!), and you will free up the environment string space it uses.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 7   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘
       ┌─────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒         Processing INBOUND Mail       ▒▒▒▒▒▒▒▒▒  │
       └─────────────────────────────────────────────────────────────┘

RQSEX IS HARD-CODED TO PUT UPLOADED FILES INTO A NEW SUB-DIRECTORY NAMED \QMX
ON THE CURRENT DRIVE.  You will need to MAKE A DIRECTORY, off the root, called
QMX.  You must move the incoming message files, from your users, into your
normal inbound net files area for processing by your echomail software.  To do
this automatically, you'll need to add the following lines to your BAT file to
handle the incoming mail.  Place this line so that it is read either before or
after every call!
   If exist \QMX\xxxx????.* goto QmxMail
                 ^^^^
(Note: this number will always be the same for your system, but it will *not*
 actually be "xxxx" - for example, "73E3" is the number XRS will use if you
 are in net 360.  It is computed exactly like a normal FidoNet echomail bundle
 name would be computed by subtracting net numbers - in hex, of course)

Now place the following lines IMMEDIATELY before (above) your section that
tosses incoming echomail.

:QmxMail
   COPY \QMX\xxxx????.* \FD\FILES (Replace \FD\Files with YOUR incoming
   DEL \QMX\xxxx????.*             mail directory)


:Toss_Echo  (Start of your regular ECHO tossing section)
   CD\RA (or QuickBBS or FD)
   Qecho -A -P -T -U   (or EchoGen, TosScan or Zmail...)
   Goto Loop

This will copy the new incoming messages into the correct area and then drop
through to your regular tossing program.  D'Bridge users see page 10.

RQSEX exits with different errorlevels to tell you whether an upload was
received and/or mail was downloaded.  ErrorLevel = 0 means no errors and
neither u/l or d/l was used.  ErrorLevel 1 means mail was downloaded, a 2
means mail was uploaded and a 3 means both upload and download of mail.

An option is available which allows the user to get their mail, automatically
update their "last read" pointer and automatically LOG OFF!  Three additional
error levels handle this "auto-logoff" function for those who wish to control
mail handling through error codes.  4 indicates automatic logoff (no
download), 5 indicates auto-logoff with a mailbag downloaded and 6 means auto-
logoff with both upload and download of mail. (All higher exit codes indicate
other program failure of some type!) These error levels can be used to direct
specific BATCH file activities if desired.  Please note!  It is NOT necessary
to use these codes unless you wish to do so.  RemoteAccess or QuickBBS will
recover from the AUTO-LOGOFF without their use and mail will be tossed
normally.

If you choose to use the Mark May utility MkXRS, you will NOT need to move
incoming mail from \QMX\ since MkXRS will toss DIRECT from \QMX\.  Please
see the documentation with MkXRS for details on how to set it up.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 8   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘

       ┌────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒   Setting Up The QMXSETUP.CFG File   ▒▒▒▒▒▒▒▒▒  │
       └────────────────────────────────────────────────────────────┘

RQSEX allows the SysOp to control certain functions by editing a
"configuration" file.  This file is named: QMXSETUP.CFG.  Here are the
options in QMXSETUP.CFG along with brief descriptions of the options
function.

BBSID xxxxxxx - The "BBSID" parameter is =REQUIRED=! If not found, RQSEX
will still run, but it will beep and display a warning message and use the
name "UNKNOWN1" for the BBS name if "Named Mailbags" are turned on by the
user.  You should set the BBSID parameter to something that will uniquely
identify your BBS.  For example, Augusta Forum is AGFORUM.  RQSEX will read
ONLY the first seven characters and will add the correct extension. If you
are running RemoteAccess and using multiple lines, the eighth character
will indicate the line the caller was using.  Note that this feature is
only available to users of XRS 3.21 and later, and it must be turned on in
the new "Option Toggle" section by any user that wants the "Named Mailbag"
feature.  Named Mailbags =ARE= the default for =NEW USERS=.  If you have
users who are still running  versions of XRS older than 3.21 they =SHOULD=
upgrade!

NetMail xxx - !!REQUIRED!! for RemoteAccess systems. Where 'xxx' is the
area number of the netmail board.  Failure to set this parameter for RA
systems causes RA/QMX to beep and use area # 201 as the netmail area (which
doesn't exist), therefore any netmail will be treated as echomail!  Not
needed for QuickBBS/SuperBBS.

InDir xxxxx - Allows you to give a different path for incoming mailbags
(default is "\QMX").  This is mostly to allow you to accept mail for multiple
nodes into separate areas if you also have the "Point xxx" parameter (which
causes everyone to have similar filenames).

PointNet xxxxx - Allows you to select the point number used by XRS.  By
default, XRS uses pointnet number 30027, which was assigned to the program by
the ZC/IC.

ShowBar - Forces the status bar to be shown even if Desqview is detected.

NoBeep - Turns off beeps on SysOp side.

OutPath x:\path - Allows you to have RQSEX automatically place the resulting
BAT1MAIL.xxx archive file into a different subdirectory. The "X:\PATH" portion
*MUST* point to a directory name! (you can't change the final filename,
anyway).  You should DELETE this file automatically at logoff time to prevent
users from reading someone else's mail.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 9   ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘

       ┌────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒ Continuing the Setup of QMXSETUP.CFG ▒▒▒▒▒▒▒▒▒  │
       └────────────────────────────────────────────────────────────┘

SysopOut x:\path -  Allows THE SYSOP (User 0) to have RQSEX automatically
place an UNARCHIVED MAILBAG into a different subdirectory.  The "X:\PATH"
portion *MUST* point to a directory name!

NoBuff -  Disable file buffering on MSGHDR.BBS and MSGTXT.BBS - on some
systems it may be faster to *not* buffer these files!

LockBaud - Force Hardware Flow Control on DSZ - required for HST's, etc!

ShowFiles - Show New Uploads ON SCREEN during FileScan.  Files will ALWAYS be
included in the XRS <F6>Summary if FLEARCH.QMX is present.  More on
FLSEARCH.QMX later.

NoBreak - To disable <CTRL-BREAK/C/K> exits from external batch files, you
may use the this parameter.  NOTE:  The user cannot interrupt the program
except by hanging up if this is turned on!  Under normal conditions, this
option should be left turned OFF!  (When left off, the user is sent back to
the BBS when he hits <CTRL-BREAK>...)

Point 666 - In order to run in "No Points" mode, or to assign a specific
point number to all RQSEX/XRS users, place a number from 0 up to 32767.
For NO points, use 0.  If you want RQSEX to assign the point numbers in
consectutive order do NOT use this option at all.

Limit 500 - To use a different maximum limit of messages for one mailbag,
assign any number less than 995.

Defer -  Disable the internal DSZ downloads (so user can d/l from normal
files area) [NOT NEEDED if OUTPATH is used]

Include -  Accepts a filename (*with* pathname!) and inserts that file into
the mailbags.

Show PIDs - Makes the ^aPID: lines show up (for the sysop *ONLY*) in the
XRS mailbags. [This works with XRS 4.00 and later only!]

MkXRS - Causes RQSEX to IMMEDIATELY call MkXRS after an incoming mail bag
is uploaded by the user.  MkXRS will TOSS mail DIRECTLY into the RA/Q/S
type message base with checking for security level and flags as well as
netmail accounting.  MkXRS is written by Mark May (1:110/290).

New Only - Makes the file search show =ONLY= new files - never the five
"most recent" which are the LAST five found in each FILES.BBS listing.

NoLogOff - Disables the logoff by carrier drop for systems running RQSEX
under Wildcat.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 10  ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘

       ┌────────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒          A Few Hints         ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒  │
       └────────────────────────────────────────────────────────────────┘

RQSEX looks for FLSEARCH.QMX - if not found *NO* "New File Search" is done at
all!  This way you can just search one or two if that is what you want, or you
can turn it off altogether.  If you want it to search all areas, just "COPY
FLSEARCH.CTL FLSEARCH.QMX". (the format of the file is *exactly* like
FLSEARCH.CTL!)  If you do not want to search ALL areas, simply copy
FLSEARCH.CTL to FLSEARCH.QMX and then edit out the lists you do not want
included in the search.

You can also automatically restrict the user-side program (XRS) from sending
any mailbags in formats you can't process by placing a file named ARC_ONLY.XRS
(or ZIP_ONLY.XRS, but not both!) into the system subdirectory.  When XRS
sees this file it will only use the desired method to pack the mail.  Note
that "SPAZ" is available in the archive and handles *any* compression type!

You may also "Force" your users to use YOUR origin line if you like.  To do
this just create a file called XORIGIN.XRS which contains the desired line (in
plain ASCII).  If XORIGIN is present, RQSEX will place a CRC value in the users
file which can be read by XRS version 3.12 or later.  This CRC check will not
allow the user to replace YOUR line with one of his own.  A CRC check is also
performed on the users name.  If either are incorrect XRS will terminate
immediately.

RQSEX recognises the person named in DORINFO?.DEF as the SysOp and always
allows *CRASH* netmail for THAT person.  Later versions of RQSEX/XRS will
also allow the SysOp to designate users who may send crash mail but current
versions will allow ONLY the sysOp to send CRASH mail.

If you are a D'BRIDGE user:
RQSEX normally puts all files in a directory named \QMX. Assuming that
your inbound mail goes to a directory named \QUICK\MAIL, add the following
to your BBS.BAT file.  You may put it after an exit from the BBS or at the
beginning of the batch file if you restart it after each user.

if exist \qmx\*.* goto qmxmail

:qmxmail
copy \qmx\*.* \quick\mail
echo y | del \qmx\*.*
cd \dbridge
db unpack

At this point, you need to return to the beginning of the batch
file, or wherever else you run DB as your mailer.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 11  ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘

       ┌────────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒     A Short Check List       ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒  │
       └────────────────────────────────────────────────────────────────┘

Here's a short check list of what we have done.

1.  Make sure ALL message areas are listed in AREAS.BBS

2.  Create a directory called QMX OFF THE ROOT, not off the QuickBBS or RA
    subdirectory!

3.  Add a Menu option to allow your users to access RQSEX

4.  If QuickBBS, add the necessary lines to your BAT file to handle a Type
    15 menu option exit.  If RemoteAccess, add a type 7 menu option as shown
    in the RA section.

5.  Add the necessary lines to MOVE incoming RQSEX mail to your ECHO tossing
    directory or setup MkXRS to handle mail tossing.

6.  Edit QMXSETUP.CFG and place it and RQSEX.EXE in the QuickBBS directory or
    if running RA, place QMXSETUP in the RA system directory and place a copy
    of RQSEX.EXE in each line's sub-directory.

7.  Make a copy of FLSEARCH.CTL and name it FLSEARCH.QMX =IF= you want new
    files listed.  Place it in the system directory.


       ┌────────────────────────────────────────────────────────────────┐
       │  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   Using RQSEX on YOUR BBS    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒  │
       └────────────────────────────────────────────────────────────────┘

Important!  Your caller MUST have a CONFIG.SYS file setup on their system
with a FILES equal AT LEAST 20!  Failure to do this will cause the XRS
program to be unable to unpack mail.  If a user complains about this problem,
that should be the first thing you ask about.  They should also download a
small mailbag BEFORE running XRS the first time.  XRS will look for mail and
complain if it can't locate any!  (this also can cause the program not to
"see" other files that *are* there...)

Your callers will find running RQSEX to be basically intuitive.  The first time
your user goes into RQSEX they will be asked to select their default message
areas to read, the message packing method and transfer protocol to be used.
Message area selection must be done before the caller can "Pack for Download".
Unconfigured (new) users are not given the option to download messages UNTIL
they have completed their configuration.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 12  ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘

When selecting message areas the first time, your users should select from
"All" groups instead of only those which have new messages!  This will allow
them to select from all available groups and save these defaults for use every
time until they change them (and not miss any areas that do not have "new"
messages available at the current time).

The users SECURITY level and AUTHORIZATION flags determine the areas from
which users can read or write.  If a message area has a higher security level
in READ the user will be unable to select that area to be included in their
mailbag.  If the area's security allows the user to read but not to write
in an area, RQSEX will allow the reader to read but will not allow a reply
to a message or a new message to be written in the area.

The number of messages XRS can handle in one "MailBag" is 995, so that is
also the maximum number of messages RQSEX will extract before beginning the
archiving process - normally, a caller will probably get much less mail than
that!  RQSEX will normally default to a message number that gives the LAST 20%
of the messages FOR A FIRST TIME USER.  This prevents a first time caller from
accidentally downloading a packet of ALL the messages!  As Sysop, you can set
the maximum limit lower than 995 by using the LIMIT option in your
QMXSETUP.CFG file.

Note that RQSEX (and the XRS reader/editor) do not do "exact" matching as far
as upper/lower case letters go!  You will always get all messages addressed
to you no matter how the names are capitalized by the sending system!

Unless instructed not to, RQSEX will =ALWAYS= automatically extract =ALL= mail
addressed to the caller whether or not they have the message's group selected.
That way, the caller can be assured that they won't miss any mail even if they
don't regularly read certain conferences.  This function can be defeated by
selecting an option in the RQSEX configuration section.  The user may elect to
tell RQSEX =NOT= to scan for messages OUTSIDE the selected areas.  This
change is useful if the user calls several boards and doesn't want to receive
duplicates of the same messages from each board.

RQSEX will NOT extract messages FROM the caller since it assumes they have
seen them before!  Your user CAN include their own messages by selecting that
option in the CONFIGURATION OPTIONS menu.

RQSEX allows a caller to select message areas that have PRIVATE messages.
When scanning these areas, it will =ONLY= pack mail addressed TO THE CALLER
OR MARKED "Public".  Private mail to other individuals is NOT included in the
mailbag.

RQSEX will normally ask if you wish to update the HighMsgRead and/or
LASTREAD.BBS fields, assuming you read new message (you can select "Pack" from
the main menu and "backtrack" to old messages!).  You should, in general,
always answer "Yes"!  If your user selects the <L>ogoff option, when packing
mail, then the HighMessageRead and LastRead fields are updated automatically.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 13  ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘

You will want to make the XRS eXpress Response Reader available to your
callers.  The Reader comes with it's own documentation included in the
package.  Again, there are two versions.  One for XT type machines and
one for AT systems.  Current versions are XRS400X.ZIP (generic 8088/8086)
and XRS400A.ZIP - the V20/30/80286/386 edition. Overlay versions are also
available.  Overlay versions require less memory but will not run as
quickly on slower machines.  X400CORE.ZIP provides the documentation AND
other files needed for ALL versions and =IS REQUIRED= to use XRS.
XRS40KIT.ZIP provides sample scripts for various communications programs
plus foreign language support overlays and is optional.


                         ┌───────────────────────┐
                         │ ▒▒▒  Odds & Ends  ▒▒▒ │
                         └───────────────────────┘


RQSEX operates as a pseudo-point system.  The callers "point" number is
determined by RQSEX the first time the user selects any options in the
configuration menu of RQSEX.  The user will be assigned the next consecutive
number above the last assigned RQSEX user.  The information that RQSEX needs
for each user is kept in a small file named QMX_CONF.SYS.  Since RQSEX
maintains its own data file, you can sort and pack your userlog at any time
without any effect on RQSEX.

A User editor program is currently being developed.  This program will
allow you to list your point users and their assigned numbers, and make
changes in their configurations.  Available soon!!  RQSEX also places
information about how many messages are downloaded, mailbags received,
groups selected and other information in your LOG file.

As a point of information, XRS uses 30027/xxx as the "From" address in the
outbound message bundles.  This has NO effect on your systems actual node
number and can be ignored!  ('xxx' always = 0 if running "No Point" mode)
Be sure to add "PointNet 30027" to your echomail processor's configuration
file if you run in 'secure' mode!  This pseudo "PointNet" number was (and
other pointnet numbers are) assigned by the Zone Coordinator.

RQSEX watches the users input and features an automatic user entry timeout set
at three minutes.  This is integrated in the FOSSIL input routines.  After two
minutes with no activity, the program will beep three times signaling that it
is waiting for input.  If another full minute elapses without any response,
the program is terminated.

RQSEX looks for the file named "EXPRESS.BBS" and copies it into the top of
SUMMARY1.XRS each time the program is run.  This allows you to have a custom
BBS "banner" of special message that will pop up in the users' editor <F6>
summary/index window every time!  You should not use color graphics in this
file, since the summary/index routine pokes characters into memory for speed
and therefore does not allow for ANSI interpretation...   This allows you to
have a special announcement capability for RQSEX/XRS users.  You could place
notices of new versions being available in there, as well.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 14  ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘


A short 'PROMO' file is included, for your use, to announce the addition of
RemoteAccess/QuickBBS Message eXpress to your system.  You'll find it included
as BULLETIN.ASC, should you want to use it in your 'NEWS.ASC' or
'BULLETIN.ASC' files.

We think you going to like this new way for your callers to communicate with
your system!  It allows your best and most active users to get on, get their
mail and get off in much less time.

If you have questions, suggestions or problems, we'll be happy to try and
help.

A FidoNet "EchoMail" conference with AREA: tag "QMX_XRS" is available from
the echomail "backbone" system.  You'll find lots of friendly help and lively
discussion of topics of interest to RQSEX SysOps in this conference.  You
should be able to get connected easily via your local Network Echo
Coordinator!

Note: native Dutch message & help overlays for XRS (Peter and friends) and
Dutch language documentation by Rudi Kusters is available, making XRS truly
bi-lingual. French, German and Swedish are also available.  If you need one
of these for XRS, Contact Mike Ratledge for further details.

┌─────────────────────────────────────────────────────────────────────────────┐
│ ▒▒▒   RQSEX    ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒   PAGE 15  ▒▒▒ │
└─────────────────────────────────────────────────────────────────────────────┘

                            ┌───────────────────┐
                            │ ▒▒▒  Credits  ▒▒▒ │
                            └───────────────────┘



Documentation for RemoteAccess/QuickBBS Mail/SuperBBS eXpress module
written by: Ed Meloan, Sysop The Augusta Forum RemoteAccess system
(1:360/0,1:360/1) and Michael Y. Ratledge, dated December 15, 1990



The first page graphics and page heading ideas were "stolen" from
Mike Janke's outstanding program RACE!  I am deeply appreciative
of his allowing me to use them to dress up the RQSEX documentation.



(C) CopyRight 1989, 1990 by Michael Y. Ratledge, CDP, CSP
SysOp of East Bay X-Change Multi-Node TCommNet BBS in Charleston, SC, USA
FidoNet addresses: 1/112, 372/0, 372/666, 372/777, 372/888, 372/6666
Compuserve Information System ID: 76666/1512