         NETWORK ADVICE:       COPYRIGHT 1996  TERRY L ERICKSON

   The following is a checklist of advice that we have compiled to aid
the operations of the network.  While these are not 'rules' as such, we
ask that you consider these as part of your responsibility to your users
(and this network) to help promote reliable message relays.


                       To our HUBS and MEMBER SYSOPs:

1: We promote a regularly scheduled and/or routine check of the mail
   being imported/exported from your system.  It's easier than you may
   think if your software allows for the following suggestions (most do):

     Many QWK based 'mail doors' have an option of including a file named
   SESSION.TXT in your .QWK packet.  Turn this on either when you do a
   'check' or just leave it on full-time.  SESSION.TXT is a report of what
   messages are actually in the .QWK packet.  If you have this on full
   time, you can "extract" it into a bulletin (or wherever) to check
   against your mail-tossers logs.  If you also put your mail-tosser
   log report into a bulletin, your callers can do the checking of
   reliable mail for themselves also!

     The 'check' simply involves looking at the total number of messages
   according to the SESSION.TXT file and matching it with what your mail
   tosser's log says that it imported.  Any differences should be found
   in a more careful 'conference-by-conference' study of the report(s) to
   see which conferences are losing messages.

     We strongly recommend that this be done monthly or quarterly, along
   with right after any configuration changes or if a user reports any
   type of mail-flow problems.  I do this -at least- twice weekly myself
   (with PCBoard and Cam-mail) and it takes LESS THAN FIVE MINUTES to see
   that reliable mail is flowing between me and my HUB with about 200
   conferences included in the network.  Small price to pay to be certain
   -all- the mail is coming in!!

     Exported mail is a little tougher to check than imported because you
   don't have a SESSION.TXT reported back to you for the messages you send.
   However, if your communications program supports logging an on-line call
   to a disk file (many do), this is easy to match to your mail-tossers
   export logs.

     I can help setup anybody with a routine if you use PCBoard, Cam-mail,
   and/or Procomm Plus (DOS).  I can also assist with procedures for some
   other software, though I'm not that familiar with everything available.
   If you have questions, please leave a detailed message about what you
   are using and your questions to Terry Erickson in OtherNet Administrate
   conference.

2: We promote a regularly scheduled and/or routine check of conference
   content, definitions, and mail-tosser links.  Simply put, this means
   to insure that when a message is posted in the ADMINISTRATE conference
   on one system that it appears in the same conference everywhere else.
   You can usually tell this by comparing the SAME information in the
   above routines (point 1: above) using conference names and message
   counts.  Also, we will regularly post 'conference information' messages
   in each conference which is a very easy check of basic configuration.

3: PROMOTE THE NETWORK to your callers and get them involved!!  Several
   people just call BBSes for files and aren't aware of the wonderful
   world of messaging.  Sure you can have a few hundred conferences on
   the system, but unless your callers are aware of WHAT they are about,
   most people won't pay much attention to them!  The success of a network
   depends largely on the active support of the member Sysops and the use
   of the conferences by message authors!!!  This is not to say that just
   because you promote the network that all of your callers will get into
   messaging, but a few may learn what messaging is about and find a real
   interest in it - just like most of us did!


                     To our USERs (message writers):

1:   The sad but true reality of BBSes is that Sysops (System Operators)
   have a LOT to do when it comes to running a BBS!  Sysops can't monitor
   every aspect of the system constantly nor can they catch every problem
   that might occur.

     So we ask that as BBS callers, you assist your Sysop by informing
   him/her of any problems that you encounter with the setup of this
   network on their system.  Report problems with the following style:

     A: Be brief, yet provide any/all useful, relevant information.  Like:
          "Message #972 in conference #47 is dated four weeks ago and I
           haven't seen any more messages in there since, Please check."
        This directs the Sysop TO the problem and tells them WHAT they
        should be looking for.  Don't just leave a message that asks, "Are
        we getting new mail?" as this doesn't do much for a Sysop.
     B: Be nice!  Realize that the Sysop has -many- other areas s/he is
        working with and may not have noticed a problem in that area.  Give
        the Sysop a reasonable chance to deal with it and get back to you.
     C: Be alert!  Pay attention to your surroundings on the BBS.  Read
        system 'newsreels', bulletins, and messages from the Sysop (or a
        Co-Sysop) to see if s/he has already acknowledged a problem (like
        saying there is trouble with network mail, etc).

2:   Any time you are dealing with a publicly available service (similar
   to this network) you are going to encounter a diverse mix of people.
   Often, other ideas/views/opinions which are expressed do not coincide
   with yours.  This should not be considered to be a bad thing though!
   You are expected to act like a mature civil adult while posting your
   messages through this network - especially when you encounter a view
   which differs from yours.  Don't -ever- put down (criticize) another
   person for an opposing opinion!!

