                                     ����Ŀ
                             ����������  ����������
                                  �����  �����
                                     ������
                      Intelec International E-Mail Network
                             Operational Guidelines
                          Release v.90  dated 10/01/92
                 Copyright (1992) Intelec Business Network, Inc.
These network operational guidelines may not be reproduced in part or whole
without the  expressed permission  of the  Intelec Network  Administration.

1.0  Administration
1.1  The Intelec International E-Mail Network  (hereafter refered to as the
     Network, Intelec Network or Intelec) is a four-tier telecommunications
     network comprised of  one Net Host BBS, Regional Hubs, Hubs and Nodes.

1.2  Intelec is operated as a "public service"  of Intelec Business Network
     Inc and Intelec Online serves as the Net Host BBS.  The Network is run
     by the Network Administrator, Cliff Watkins, also the SysOp of Intelec
     Online  and the President of Intelec Business Network, Inc.  But while
     Intelec operates as a public service, it is NOT a `public access' net-
     work. We are a `private network'  thus the rules of operation that are
     set forth in this document supercede any and all rights set forth out-
     side of this document.

1.3  The Network Administration  reserves the right  to admit or refuse any
     BBS/SYSOP as participating members of the Intelec Network. The Network
     Administration further reserves the right to remove and/or suspend net
     access of any individual node, hub or regional hub for any action con-
     sidered detrimental to the goals, spirit and/or quality of the Intelec
     Network  as well as failure to abide by these guidelines.

1.4  The Network Administration consists of the `Network Staff' as outlined
     in section 10 of this document.

1.5  Acceptance to Intelec is determined by the Network Administrator or by
     the Intelec Regional or Hub SysOps that an applicant may apply to. Any
     incomplete application forms will not be processed. Applicants may not
     apply directly to any Intelec Node SysOp, only Regional or Hub SysOps.

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

2.0  Net Host BBS  Operations
2.1  The Net Host BBS equipment is NOT the property  of any system relaying
     the Intelec Network. No claims may be made against the software and/or
     hardware that "comprises" the Net Host BBS.  All software and hardware
     required to run the Net Host BBS is privately owned and used with per-
     mission by the owners of Intelec Business Network, Inc.
   
2.2  The Net Host BBS Sysop  coordinates the primary mail exchange time for
     each Regional Hub or Hub connected to the Net Host BBS.  Each Regional
     Hub and Hub has a "time slot" ensuring that all routine mail exchanges
     are accomplished in a timely manner.  The Net Host BBS Sysop publishes
     the primary mail exchange times to ensure that no  Regional Hub or Hub
     deliberately intrudes  during another Hub's primary mail exchange time
     slot. Only Regional Hubs or Hubs may "relay" through the Net Host BBS.
   
2.3  Intelec is a "no fee" network.  The expenses of network operation will
     be offset by  funds generated through "voluntary contributions" to the
     Net Host BBS or Network Administration. Changes to this policy will be
     by majority vote of all the network SysOps [only].

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

3.0  BBS/Network Software Supported
3.1  Network members must use legally purchased or obtained NET software as
     defined by the respective software author's docs  and as listed below:
     Rnet, Qnet, RoseMail, PCRelay, Tnet, QWiKerNet, MkNet, Cnet, Cam-Mail,
     TriNet, Jnet, BGNet.   If it is not listed here it is not approved for
     use in the Intelec Network for relay of said network.

3.2  Network members must use legally purchased or obtained BBS software as
     defined by the respective software author's docs  and as listed below:
     PCBoard, GAP, Wildcat!, Spitfire, Searchlight, TriBBS, RBBS, UltraBBS,
     Remote Access, Auntie and GT Power. If it's not listed here, it is not
     approved for use within the Intelec Network for relay of said network.

3.3  Additional software might be approved for use within Intelec  but only
     after extensive testing is done on the software and after the approval
     of its use by the Network Administrator and the software author and/or
     vendors. Authors interested in getting "Network Use" approval can con-
     tact the Intelec Network Administrator, Cliff Watkins, in the NetAdmin
     conference on any Intelec Network Member BBS.

3.4  The Network Administrator reserves the right to "decline or terminate"
     access to the Network to those individuals failing to operate with the
     properly registered or purchased software used for netmail operations,
     and/or BBS operations.

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

4.0  Network SysOp Responsibilities
4.1  Hub SysOps are responsible for  abiding by administrative decisions in
     said region. Node SysOps are responsible for abiding by administrative
     decisions which pertain to their board or users access to the network.

4.2  Hub SysOps must relay mail a minimum of once daily  unless it is tech-
     nically impossible"  to do so.  No Hub SysOp should intentionally shut
     down for  over (24) consecutive hours  without first making provisions
     for the continued relaying of it nodes.  In the event that a Hub SysOp
     does not relay for 3 consecutive days without notification to the Net-
     work Administrator, its' Nodes and Hub,  the Hub may be temporarily OR
     permanently removed as that region's hub at the sole discretion of the
     Network Administration.

4.3  Hub SysOps  should make "every possible effort" to accommodate any/all
     conference requests for their nodes as equipment/configurations allow.
     This applies to Intelec conferences only.  This does not apply  to any
     of the network links, such as BizNet, that Intelec may be porting.

4.4  When any Hub SysOp has been notified by  the Network Administrator  to
     remove the net access of a node the Hub SysOp should remove the node's
     access as soon as possible. In the event that the Hub SysOp "does not"
     comply with a  "node-access-removal"  request,  the Hub SysOp's access
     may be removed and the Regional "assignment" may be passed to another.

4.5  The Hub SysOp  has the "authority" to remove the access of one or more
     of its nodes for one (1) day if the situation warrants such an action.
     Immediately following any node's "access removal", the Hub SysOp needs
     to notify the removed node by voice and  the Network Administrator via
     voice or public message in NetAdmin  explaining the situation in full.

4.6  Neither Hub nor Regional SysOps may Tcan a user from the network, thus
     preventing mail from the user from flowing up or down his or her link.
     All Network SysOps retain the right to Tcan a user from his or her BBS
     as this is considered a "BBS Tcan". All "Network Tcans" are to be made
     with the approval of the Network Administrator.

4.7  Regionals must relay through the Net Host BBS on a "daily basis". Hubs
     must relay through their respective Regional on a daily basis and Hubs
     cannot relay through the Net Host BBS unless message activity from the
     Hub warrants more "affordable" relays and upon approval by the Network
     Administrator. Regional zoning isn't written in stone and is flexible.

4.8  No Intelec Network SysOp may censor in any way any message relayed via
     the Intelec Network unless permission is given by the administrator to
     do so and includes manual modification or with the use of utilities to
     do so automatically. Network guidelines handle this matter already but
     if  `local ordinances'  place your BBS in jeopardy, regardless of your
     tenacity in  `keeping your BBS clean', then you may wish to reconsider
     involvment with electronic mail until your local government `rescinds'
     such laws which may be unconstitutional.

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

5.0  Conference Coordinator, Hosts and/or Moderators
5.1  The Conference Coordinator is a Network Staff position and is outlined
     in section 10.0 of these network guidelines.

5.2  Conference Host, Moderators are selected by the Conference Coordinator
     or by the Network Administrator and may be removed and replaced should
     a CH or CM fail to fill the duties of said position. CH and CM respon-
     sibilities are described below:
5.2.1  Attempt to keep message traffic "on topic" and politely redirect off
       topic users to the "appropriate" conference.
5.2.2  Notify the Network Administrator of problems regarding config errors
       such as but not limited to: Duplicate Mail, Cross-Echoes, etc.
5.2.3  Notify Network Administrator should you have any difficulty in main-
       taining the mail flow of your assigned conference(s).
5.2.4  Do not flame  or help fan the flames of users. Report any situations
       to the Network Administrator in the NetAdmin Conference.
5.2.5  Maintain the friendly atmosphere that has become our trademark.
5.2.6  Assist in the answering of questions relating to the subject of your
       conference, to the best of your ability.
5.2.7  Deal with a problem user or users in the following manner:
          5.2.7.a  Issue polite warning to users failing to follow rules.
          5.2.7.b  If user persists in a manner that you feel  warrants a
                   temporary suspension, contact the user's SysOp and the
                   Network Administrator in the NetAdmin conference only.
5.2.8  Conference suspension, network suspension and/or network banning  is
       described in section 6.0.

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

6.0  Conference and Network Temporary Suspensions  and Network Bans
6.1  All suspensions or network bans  are determined by a "two-thirds vote"
     between the moderator, the user's SysOp and the Chief Moderator or the
     [Network Administrator or Assistant Administrator].

6.2  Moderators requesting administrative action must do so in the NetAdmin
     conference or in the Moderators conference. While NetAdmin is a public
     forum it is not an invitation to debate a moderator's request for such
     action.

6.3  Upon network-wide suspension or ban, a SysOp may "appeal" the decision
     on behalf of the user in the Moderators conference. This may only take
     place after the suspension or ban has been enforced by the SysOp.

6.4  Suspensions or bans are determined under the following guidelines:
6.4.1.a  A warning message must come from the conference moderator prior to
         administrative action  unless actions are determined to be severe,
         and/or blatant enough to warrant an immediate suspension or ban as
         determined by the Network Administrator.
6.4.1.b  2nd offense: 30 day suspension from conference  with a 90 day pro-
         bationary period.
6.4.1.c  3rd offense: If during probationary period, network-wide ban for a
         period to be determined by the Network Administrator.
         If after probationary period lapses,  a 30 day suspension from the
         conference with a 90 day probationary period.
6.4.1.d  4th offense: Permanent network-wide ban.
6.4.1.e  If the 1st, 2nd or 3rd offense is considered blatantly disruptive,
         abusive, or otherwise detrimental to the network, an immediate ban
         may be implemented by the network administrator.
6.4.2  Repeat offenses do not need to be the same nor do they need to occur
       in the same conferences as the original offense.
6.4.3  The Administration reserves the right to determine if the actions of
       a user warrant a conference suspension or network-wide suspension.
6.4.4  All temporary suspensions  are for a period of  no less than 30 days
       unless otherwise shortened by the Network Administration.
       Any/all probationary terms are for a period of  no less than 90 days
       unless otherwise shortened by the Network Administration.

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

7.0  Receiver Only and Copyrighted Messages
7.1  Pursuant to the  Electronic Communications Privacy Act of 1986, 18 USC
     2510 et. seq., all BBS SYSOPs and users  participating within Intelec,
     must be aware that there are no facilities provided by the Network for
     sending or receiving confidential electronic communications.  Although
     Intelec maintains the capability and capacity to send and receive mail
     that is flagged as "Receiver-Only" or "Routed Mail.",  mail so flagged
     is not to be considered by any user as actual "private" messages.  The
     purpose of the  "R/O", "Routed Mail" or "Point-to-Point" flags are in-
     tended solely to provide a means to limit the possible number of nodes
     and/or users  that may have access  to the mail  for display purposes.

7.2  All participating Network SysOps must agree, as a condition of network
     membership and participation,  that they will notify anyone reading or
     exchanging messages within all Intelec conferences on their BBS of all
     network guidelines  and that Intelec has no facilities  for exchanging
     confidential electronic communications. Suitable bulletins and/or news
     displays should be placed in a prominent place within the users' view-
     ing capabilities, indicating that no confidential communications capa-
     bilities are available within the Intelec Network. All messages posted
     in relayed conferences are deemed to be public. Access policies to the
     private conferences must be maintained  to restrict access to only the
     private conference members  as described in these guidelines.  Intelec
     Network,  Intelec Business Network, Inc  and all member SysOps  assume
     no accountability or liability  whatsoever  for any violations of this
     policy by any and all users of the Intelec Network.
 
7.3 Messages entered into an Intelec Network conference become the property
    of  the Intelec Network and its membership,  unless the author posts an
    explicit copyright notice in the message and only the author of a copy-
    righted piece of material may post copyright notices on messages.

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

8.0  Specific Network Guidelines
     While it is not the intent of  Intelec or the Network Administrator to
     interfere with any SysOps authority on his or her own BBS, all relayed
     conferences are subject to the jurisdiction of these guidelines. These
     Network guidelines  are explained in detail below  and Intelec Network
     SysOps are responsible for the  enforcement  these Network guidelines.

8.1  No Illegal Activities
     Any illegal activities, including but not limited to  the promotion of
     illegal acts and promotion of software copyright infringement will not
     be allowed within the Intelec Network.  Any such activities constitute
     a grievous reason for the removal of the node or hub from the Net, and
     may necessitate compensatory action against the violator for any legal
     liabilities such activities may cause the Intelec Network.

8.2  No BBS Ads
     Participating Intelec Network SysOps  will not relay nor will allow to
     be relayed  messages that contain information that advertise BBS's un-
     less in the Intelec Network BBS AD or ANSI Conferences.  The placement
     of BBS telephone numbers within messages  to advise users of a contact
     telephone number is not considered a "BBS Ad" as long as the intent of
     the message is clearly evident without the telephone number. It is un-
     derstood that a user might disregard this rule.  It is the expectation
     of the Network Administrator that SysOp's will take appropriate action
     to prevent this occurrence. Flagrant disregard of this rule  justifies
     the removal of that node  from the Network.  It's also understood that
     if an ad is relayed and the SysOp corrects the situation,  it does not
     justify removal of that node from the Network.

8.3  No Aliases
     Obvious "aliases" must not be used anywhere in Intelec conferences. We
     are not telling you that you can not have aliased users  but if you do
     they must NOT be able to access or enter messages  into ANY of Intelec
     Network's conferences.  An alias is defined as a name used by a caller
     whose intent is to prevent identification of the caller  by the SysOps
     and any other Intelec Network member. SysOps of each participating BBS
     are responsible for ensuring  that only validated users are allowed to
     exchange messages within conferences  that are relayed by Intelec.  It
     is the Network Administrator's  understanding that  each node SysOp is
     responsible for the names used on their own BBS. If the SysOp grants a
     user an alias for what the SysOp deems is a valid reason, such as sec-
     urity,  and that alias is not apparently an alias  (such as Dr. Modem,
     which is) then there's no need to inform Intelec of that alias. Should
     the Network Administrator think a user is using an alias  the SysOp of
     the originating board must either validate or remove that user.

8.4  No Flames or Personal Attacks
     Anyone found to be abusive in nature, such as but not limited to, name
     calling, insults, slanderous statements, arrogant or instigative posts
     or any other rude, lewd  or otherwise obnoxious  behavior or comments,
     is to be removed from the conference. Further occurances of this abuse
     will result in the user(s)  being removed from the Network completely.
     Intelec,  Intelec Business Network, Inc  and all member SysOps  assume
     no accountability or liability  whatsoever  for any violations of this
     policy by any and all users of the Intelec Network. Network SysOps can
     and will be  held accountable  for failure to remove any user or users
     who make statements that are  abusive, slanderous or demeaning  to any
     individual, group,  organization either social, political, theological
     or racial. No "offensive or abusive" language is to be used in any and
     all of the Intelec conferences.  The use of  any word, group of words,
     expression, comment, suggestion, or proposal which is profane, filthy,
     lewd, lascivicious, obscene, indecent, or that is demeaning ethnically
     or racially is strictly prohibited within the Intelec Network. Network
     member SysOps must remove any users from the echoes for flaming and/or
     fighting. We cannot ask that users be removed as "users of your board"
     but if they are a problem to Intelec  they must not have access to it.
     Removal of abusive users will be handled in accordance to section 6.4.

8.5  Network Configuration
8.5.1  Monitoring NetAdmin
     Network member SysOps MUST monitor the NetAdmin conference on a timely
     basis to be aware of announcements (conference additions or deletions)
     or mail regarding configuration errors  (duplicates and cross-echoes).
     SysOps must "correct" any detrimental activity coming into the Intelec
     Network via their board, on a timely basis, including  but not limited
     to  duplicates, cross-echoes,  abusive users and improper or excessive
     taglines. All Hubs must ensure that their nodes take corrective action
     against these or other problem areas.
8.5.2  Network Taglines
     Every Intelec Network tagline must begin with the text string Intelec.
     PCRelay SysOps must use the NET.ID file supplied from the Net Host BBS
     or their regional/hub. QWK format members must have the string INTELEC
     in the 'TAG' and 'HTAG' portion  of their Network configuration files.

8.6  Conference Configuration
8.6.1  Required Conference
8.6.1.a  NetAdmin is Intelec's Administrative conference and is required to
         be carried by all members. It is a fully public access conference.
8.6.2  Private Conferences
8.6.2.a  Moderators  is open only to hosts or moderators of Intelec Network
         conferences and the SysOp "carrying" this conference.
8.6.2.b  Regionals conference is a non-required conference, although highly
         recommended for all  Intelec QWK Regional and Hub SysOps to carry.
         It is used for the processing of network applications  between the
         Regional or Hub SysOp to the Host and the Nodelist Coordinator and
         must be setup as PRIVATE conferences. Network applications may NOT
         be relayed through ANY OTHER CONFERENCE in the Intelec Network!
8.6.2.c  SysOps conference is open only to validated BBS SysOps regardless
         of network affiliation.
8.6.3  Restricted Conferences
8.6.3.a  PCRelay  is the ONLY conference that PCRelay members are permitted
         to "route" mail to other PCRelay member BBSs.
8.6.3.b  ANSI is permitted in ONLY the BBS ADS or ANSI conferences per 8.7.
8.6.3.c  BBS Ad may appear once per BBS per week in the BBS Ads Conference.
8.6.4  Recommended Conferences
8.6.4.a  NetChat is an active and recommended conference for a global link.
8.6.4.b  Net-Staff is recommended to maintain the "user to net-staff" link.
8.6.4.c  Moderators (private) is recommended if your board has a moderator.
8.6.4.d  Regionals (private) is recommended if you are a Intelec Hub SysOp.
8.6.4.e  PCRelay is recommended for all PCRelay members for `routing' mail.
8.6.5  Remaining Conferences
8.6.5.a  All remaining Intelec conferences are considered public access and
         accessible to everyone. The exception here is if the user has been
         "removed" from an Intelec conference for any valid reason  (as de-
         cided by the Network Administrator, the users SysOp and Conference
         Host or Moderator or these Intelec Network guidelines section 6.0.
8.6.5.b  Any of our "public conferences" may be made private on the SysOps'
         BBS at that SysOps' discretion.
8.6.7  Conferences Not Carried
       SysOps will make their users aware of any conferences 'not carried'.
       This can be done by means of news screens or bulletins. Also, if you
       are carrying multiple networks,  your conference menu must display a
       type of coding  that differentiates our conferences  from any of the
       other network conferences that you might also have available. Moral-
       ity is a "valid reason" for any SysOp (including Regionals and Hubs)
       to decline carrying a specific conference. It is  not  the intent of
       the Intelec Network to impose moral values or issues on anyone, user
       or SysOp alike. Lastly, networks that Intelec ports to it's members,
       such as BizNet or ChuckleNet, are not a requirement for Regionals or
       Hubs to carry. They are ported for convenience, not requirements.
   
8.7  ANSI In Messages
     'ANSI' is permitted ONLY in the Intelec ANSI conference or the BBS_Ads
     conference and nowhere else.

8.8  PCBoard or similar BBS-Software-specific Macros
     PCBoard or similar macros  are not to be used anywhere in the Network.
     Although PCBoard makes up a majority of this network,  the 'macros' it
     supports is NOT supported by  the other BBS software packages.

8.9  Network Related Discussions or Debates
     Network business will be discussed in the NetAdmin, Regional, Net-Staff
     or Moderators conferences. If it does develop elsewhere, move it to the
     appropriate conference. If it develops in the NetAdmin conference and a
     topic or thread is asked to be moved to Moderators or Regionals, please
     do so so that everyone in the network is not subjected to the increased
     amount of mail activity.

8.10 Signatures and Taglines
     While we have come to the conclusion that limits on signatures would be
     very difficult to enforce, we have agreed that some limit is necessary.
     Three lines should be more than sufficient but if constantly used and/
     or abused, the user *will* be asked to cease. No signatures or taglines
     may reflect a moderator, host or administrative position outside of the
     Intelec Network positions.  ie:  if you host the Programming Conference
     on another network, do not use it in your tagline in any Intelec confs.
     Also, if you host the For Sale Conference on Intelec, do not use it in
     your tagline or signature *outside* the Intelec For Sale Conference. If
     your signature is of "political nature" please restrict it's use to the
     Politics and/or related conferences. If your signature is of "religious
     nature" please restrict it to a religious-based conference, etc.

8.11 Quoting Guidelines and Utilities
     Some new utilities of late have been introduced  which create some very
     big problems in the network. The fancy quote utilities have been banned
     from use in our network due to the overhead that these utilities create
     and subsequent expense to those SysOps relaying the mail.  Fancy quotes
     consist of any quoted text "border" that consists of MORE than a single
     ascii line around the quoted portion of a reply. While this can also be
     abused there are limitations to quotes of all kinds.  Quote "size" will
     consist of the quoted text AND any border to the quoted portion. Quotes
     are not to exceed the replied portion of any message.  And please quote
     only when it is necessary to maintain a "proper train of thought".

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

9.0  Making Ammendments To These Network Guidelines
9.1  Although the Network Administrator is responsible for implementing any
     changes to these guidelines, any Intelec Node or Hub Sysop, Conference
     Host or Conference Moderator  may request ammendments  to these guide-
     lines from the Network Administrator. Such requests / petitions or any
     and all discussions thereof MUST take place in the NetAdmin, Regionals
     or Moderator conferences of the Intelec Network and no place else.

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

10.0 Network Staff
     The Network Staff positions are by "appointment only", any staff member
     failing to perform their duties will be replaced by the Network Admini-
     strator. Network Staff positions will be added as necessary.

10.1 Network Administrator: Cliff Watkins
     The chief administrative position in the network is responsible for the
     overall direction of the network.  The network administrator determines
     the membership of the network staff. If any member of the network staff
     has any difficulties or questions  they are encouraged to seek the help
     or advice of the network administrator.

10.2 Administrative Assistant: William Padilla
     Assistant to the administrator, responsible for "project coordination",
     quality control,  and in case of absense by the chief administrator, he
     will serve as the Acting Network Administrator.

10.3 Chief Moderator: Rod Wardlow
     Moderators will go to the "CM" first for assistance with any conference
     related problems. The "CM" is also the Moderator of all the Moderators.
     This key position will also be responsible for  the initial attempts at
     any dispute settlements although the final administrative decisions may
     be determined by the Network Administrator or Assistant Administrator.

10.4 Conference Coordinator: David Bucci
     Responsible for taking suggestions for conference additions, deletions,
     etc. Tallying votes on proposed confs, and the keeper of the conf list.
     Conference "deletion approvals" are subject to administration approval.
     The conference list is to be forwarded to the IN Basket Chief Editor on
     a timely basis. The Conference Coordinator may assign assistants to aid
     in the monitoring of conferences.

10.5 In Basket Chief Editor: Dave Calmer
     Coordinates the "Intelec Network Distribution File"  (IN-yymm.ZIP)  for
     timely monthly distribution, compiles "monthly newsletter" (IN Basket).
     The Chief Editor also assigns assistants  to aid in the distribution of
     the Network Distribution File or Monthly Newsltter.

10.6 Nodelist Coordinator: Gordon Lincoln
     To "keep track" of the information for the Network Nodelist and keep it
     current.  Regionals and hubs who approve new members must pass nodelist
     information to the Nodelist Coordinator  in either the Regionals or the
     Structure conferences. As information contained is private in nature it
     should not be displayed or transmitted in a public forum,  even as R/O.

10.7 Network Statistician: Bob Gibbons
     Compile net/conference information, etc for inclusion in the IN Basket.

10.8 Network Marketing: David Shapiro
     Coordinate Callers Digest or other Ads that the network is involved in.

10.9 Network News Reporter: Bill Wilson
     Gather news from around the network for inclusion in the IN Basket.

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

<END>
     End of Network Guidelines.
