          NOTES ON USING AN ALIAS IN THE SYSOP RECORD OF GAP
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Version 3.x of MainMail make some special considerations regarding
the sysop record of GAP, when an alias name is used.  There are some
circumstances that need special handling of the sysop's name within
the door.  These special circumstances are described here, and their
solutions explained as well.

   First, this document does NOT apply to you if you use your REAL
name in the sysop record (first physical record in the GAP user file)
in GAP.  If you use your real name in GAP, you need not read the
remainder of this document.  It does not allpy to you....

   If you use a fake name in GAP for security reasons, the following
rules apply to you:

   1)  MainMail will _NEVER_ use your alias name.  All messages will
       appear to or from your REAL (public) name.

   2)  If you are using an alias in GAP, you should _NEVER_ use your
       real name in GAP!  In other words, DO NOT create a second user
       record with your real name!  Doing so will confuse MainMail.

   3)  Place your _REAL_ (public) name in two places...

       a) In the 'Sysops Name In BBS' field in the first field in
          GAPSETUP.

       b) In the 'Sysops Name In Door' field in MMSETUP, in the
          CONFIG/GENERAL screen.


    If you follow these directions, MainMail will use your REAL name
in the door, even though it does not actually exist in the bbs.


    OPERATION IN DETAIL
    ~~~~~~~~~~~~~~~~~~~
    When the door is first opened, MainMail reads door.sys, or the
'-N:' command line parameter, and checks for the word 'SYSOP'.  If a
match is not found, it then checks the name in door.sys or the command
line and looks to see if it matches the name entered in MMSETUP in the
CONFIG/GENERAL screen.  If either match is found, then MainMail
assumes that the person in the door is the sysop, and reads the FIRST
RECORD in the GAP user file (and subsequently, the member records for
THAT user) no matter what the name of that user record is even if it
is an alias.

    Logging on at the console (local login) using the C/S or C/Q login
method essectially does the same thing.  You will log in as the sysop,
no matter what name is in the sysop record.....

    If you have another record in GAP with your REAL name in it (a
second user record), and you use that name to log in as, then you are
logging in as a DIFFERENT user, with different member records, and
different message pointers.  MainMail will always use the SYSOP
record, thus you will have different pointers in MainMail then you do
in GAP.  Do not create a user record in GAP using your real name, if
you use an alias in the GAP sysop record.  _OR_ if you _DO_ create a
user record with your real name, DO NOT LOG IN AS THAT USER UNDER ANY
CIRCUMSTANCES!  Log in from remote using your alias, NOT your real
name.  This will always guarantee that your GAP and MainMail message
pointers will match.

