         ڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿ
         
                       
                 ߱  ߱  ߱  ߱ 
                                   
                                    
                                    
                                 
                      
                              
                    ****** North Coast Echomail Network ******
               ** Hosted By The Mailbox BBS - A Sysop's Only BBS **
                            ** BBS (216) 671-3347 **
                       **** Located in Cleveland, Ohio ****
                         **** Fido Address 1:157/584 ****

                 *** Netmail Crash Changes/Errors to 11:623/0 ***

         ڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿڿ
         
               North Coast Echomail Network (NCEN) Regulations 
               ===============================================



       PROFANITY:
       **********

       Profanity is prohibited in in all conferences that are
       NOT classified as Adults Only in the conference lists.
       A word here on the definition of profanity.  If you would
       not like your children or wife to see/hear the word, it's
       most likely profanity. In other words, if you would take
       offense if someone used that word in front of your family,
       don't use it in a conference classified as General.  The
       MODERATOR will be responsible for monitoring the assigned
       conference(s) for violations of this restriction. The
       local sysop shall be required to restrict underage users from
       all conferences classified as Adult Only. It is the local
       sysop's responsibility to provide conference descriptions of
       all conferences that are carried on his/her local system.



       OFF-TOPIC:
       **********

       All messages in each conference should pertain to the topic
       that the conference was set-up for.  If the discussion strays
       from the topic at hand, move the discussion to the appropriate
       conference.  If the thread is a general chat, move it to the
       general chat conference. Don't discuss plumbing in the cooking
       conference. The MODERATOR will be the judge as to whether
       or not the current thread is off-topic.


       Alias'
       ******

       Alias' or handles will only be allowed in conferences deemed
       as an Alias conference.  It is the responsibility of the local
       sysop to ensure that the conference is set-up up properly for
       a alias conference.  There will be NO deviations on this rule.
       All echoes MUST be set up the proper way throughout the network.
       An Alias conference will only use ALIAS names.  No real names
       are allowed in the conference NETWORK WIDE.


       Conference Descriptions:
       ************************

       Each conference will have a description file concerning the
       rules governing all actions in said conference.  This will
       include the topic of discussion, classification of the conference,
       any any other criteria needed to define the conference.  All
       conferences through-out the network shall be set-up identically.
       It is the responsibility of the local sysop that each conference
       adheres to the conference description.  Each local system will
       post and/or make available to their users a conference description
       file AND a copy of the network rules.  These items are made avail-
       able on the Mailbox BBS.  It is the local systems responsibility
       to avail themselves of these documents.  It is not required that
       the Mailbox BBS send these documents to the local system UNLESS
       said system is capable of receiving attached files. The conference
       description file supplied by the Mailbox bbs shall have a coding
       system showing what the conference set-up shall be.


       ORIGIN LINES:
       *************

       All conferences that are a part of the NCEN shall have an
       origin line affixed to it. This origin line MUST be on one line,
       and must be the LAST line of the message.  The origin must have
       the the logo *NCEN* as the FIRST word in the line.  The origin
       line shall contain at least the following information:

          1.  *NCEN*  (First word in line).
          2.  The originating bbs's name.
          3.  The originating bbs's city & state.
          4.  The originating bbs's phone number, including area code.
          5.  The originating bbs' network address, which will be assigned
              by NCEN HQ.  QWK transfer bbs' will have a non-continuous
              mail status, and file transfers must be done thru the bbs
              itself. (No netmail transfers.)  All NCEN member bbs' are
              encouraged to adopt fido-style mailers because of the ease
              of file & mail transfers afforded by this method. However,
              this is not a requirement to become a member bbs.
          6.  If a hub or regional hub, the following word:

                            REG-HUB or HUB

          7.  Any other information the local system/sysop would like
              to appear in the origin line, PROVIDED the above info
              is NOT EXCLUDED/OMITTED, or will force the origin line
              to become more than one line.


       Private Messages:
       *****************

       Private messages will only be permitted in those conferences that are
       designated as such, NETWORK WIDE.  Users must be informed of the
       fact that completely private messages are not really possible in the
       echomail environment using a disclaimer that will be posted in such
       a place that all users WILL see it each and every log-on.  This is
       for the protection of you, the sysop.


       File Attachments:
       *****************

       File attachments are only allowed in conferences that are expressly
       designated as such.  As a general rule, file attachments are NOT
       permitted in echomail conferences.  File attachments should be
       sent via netmail file transfer using a front-end mailer. The QWK
       format does not lend itself to sending files to only one bbs
       destination, but to all nodes attached to that conference. This
       will put an undue strain on bbs' that do not wish to receive the
       file.  Therefore, file attachments are PROHIBITED using QWK type
       mail transfers.  File sends are permitted via netmail file sends
       only.  File sends are not permitted during a SCHEDULED mail run,
       but must be sent as a separate transmit, outside of normal mail run
       schedules and/or hours.

       Governing Body:
       ***************

       A Governing Body will be formed, consisting of three (3) network
       sysops, one (1) conference moderator and one (1) permanent member,
       which will be me, Rich Bongiovanni, for a total of five (5) persons.
       This body will handle rules changes/additions/deletions and appeals
       processing.  It will also handle conference additions/deletions and
       coding.  The Governing Body is the only way that a moderator can
       be over-ridden or removed.  Each member of the Governing Body shall
       have one vote on all agenda items.  A majority vote is required for
       any and all agenda items to be implemented.  Approval of the body
       is required for the removal of a member bbs from the network.  The
       term of office for each member of the Governing Body is three months,
       excluding the permanent member (me), which is lifetime. This term
       will be handled in a special way the first time the Governing Body is
       implemented. During this time, the term for sysops will be staggered
       to allow for a staggered rotation schedule for the remaining periods
       on the Governing Body.  All member bbs sysops will be required to
       serve on the Governing Body, when their name is reached on the rotation
       schedule, which will be a separate document.

          * SPECIAL IMPLEMENTATION:

                       Sysop #1 - one month
                       Sysop #2 - two months
                       Sysop #3 - three months
                       Moderator - three months

       Thereafter, three months for each body member.


       Moderators:
       ***********

       The CONFERENCE MODERATOR shall be in charge of the daily activities of
       his/her conference.  The Moderators duties include monitoring the
       conference to ensure that all messages are on-topic, with content
       within published conference guidelines.  The moderator shall have the
       power of suspension and/or blackball.  All network sysops are bound by
       the decisions of the moderator.  However, all sysops and bbs users may
       appeal the moderator's decisions to the Governing Body.  If a moderator
       suspends or blackballs a user, the local sysop must honor this decision,
       or appeal the decision.  The affected user shall remain on suspension
       or blackball during any appeals process.  If the decision of the Governing
       Body is to repeal said moderators action, then, and only then, shall
       the affected user be re-instated.  A network sysop may institute removal
       procedures against a moderator at any time to the Governing Body.  If
       the Governing Body decides that the action is warranted, the action shall
       then be carried out immediately.  There is no further appeals process.


       Conference Coding Symbols:
       **************************

       NP  - Private messages are NOT permitted.
       PA  - Private messages allowed but not required in conference.
       PO  - Private messages ONLY in conference.
       NA  - Alias' are NOT permitted.
       AA  - Alias allowed but not required in conference.
       AO  - Alias is REQUIRED in this conference.
       REQ - Required conference.  All members MUST carry conference.
       ALD - ADULT conference, no minors allowed. NO exceptions.
       GEN - General audience - NO profanity or off color discussions.
       FN  - No file attachments allowed.
       FY  - File attachments allowed.


       ANSI Graphics:
       **************

       ANSI graphics are permitted in the message bases.  However, bbs
       specific @ codes are NOT permitted.  Most bbs software will accept
       ANSI codes, but @ codes are normally only readable by the specific
       bbs software that it is designed for use with.  This will cause
       unpredictable results with other bbs software.  Therefore, do not
       use these codes in your messages or ads.


       Network Rules:
       **************

       All network rules and/or regulations shall be instituted first through
       the Governing Body, and if approved by them, put to a network wide sysop
       vote, before being incorporated into the By-laws of the network. For
       any changes/additions to be implemented, a majority sysop vote is
       required.
