Micronet Information Network Policy Document
Last updated 19 July 2018
Written by Sean Dennis, Micronet Zone Coordinator
618:618/1@Micronet -or- zc@minftn.net
=============================================================================
Micronet is meant to be a laid-back, friendly and comfortable mail network
where everyone can feel comfortable.  However, there's always a bad apple
in every bunch so there are policies in place to help keep things running
smoothly.

By carrying Micronet on your system, you agree to abide by the following, so
make sure you read and understand this before you submit your application!

The following is for the network in general.  For Micronet's IBBS League 618
policies, please see L618RULE.TXT that is included in your infopack.

SECTION I: General Policies

  1. Andrew Leary, Assistant Zone Coordinator, has full authority over the
     network if I am unable to be contacted.

  2. If your mail system/host bounces my email address (zc@minftn.net)
     as being spam, that is cause to not have your application approved or
     your removal from Micronet.

  3. You are solely responsible for all traffic coming from your BBS.  It is
     your responsibility as the sysop to stop problem users from creating any
     problems in Micronet.  If you are unable to stop the users on your
     system from abusing their priviliges, your Micronet access may be revoked.

  4. Do not incite, flame, or otherwise rile anyone up in any of the public
     echoes in Micronet.  Good-natured ribpoking is fine (and encouraged :),
     but an all-out flamefest is not.  Not only is that in bad taste, it also
     reflects badly on you and your BBS.  Bad behavior is NOT tolerated in
     Micronet and is dealt with swiftly and without mercy.

  5. If you have a disagreement with someone, move it to netmail or email.
     Do NOT duke it out in public.  Act your age, not your shoe size.  See
     the above policy about bad behavior.

  6. Absolutely no illegal content (I'll leave it up to you to figure out
     that one) is allowed in Micronet, either in public or private messages.
     If it is found that you are using Micronet for illegal purposes, your
     access will be immediately cut, no questions asked.

  7. You can use aliases in all echoes except for MIN_ADMIN and L618_SYS.
     
  8. Network nodelists and infopacks are released on a weekly basis,
     normally at 0400 Friday Eastern Time (UTC -4/-5 DST).  Both are
     hatched out via the MIN_LIST and MIN_INFO filebones.  For non-FTN
     systems, you may get the infopack (which always includes the latest
     nodelist) via the following:

     Web: https://outpostbbs.net/mininfo.zip
     FTP: bbsftp.outpostbbs.net/pub/network/micronet/min_info
          (Nodelist is in the min_list directory)
     FREQ: FREQ MININFO at 618:618/1 or 1:18/200@Fidonet

     If you are a QWK or NNTP node, your uplink should have made
     arrangements to get both files to you via a mutual protocol.
     
     Micronet does not use nodediffs.

  9. If you find an error in your nodelist entry, please notify your hub as
     soon as possible.  The correction will be published in the new nodelist
     created on Friday.

 10. You may use ROT-13 encryption in Micronet, but any other encryption type,
     including PGP-encoded messages, are strictly forbidden in Micronet.

 11. Any legal questions are bound to follow the laws of the State of
     Tennessee and the federal laws of the United States of America.

 12. Last, but not least, be a contributing member of Micronet.  Please don't
     hook up your BBS and never post a single message.  That will actually get
     you removed from Micronet since I'll assume that your system is no longer
     working.  Drop a line at least once a week and if you don't see traffic,
     create some!  If everyone just sits waiting for traffic, there never will
     be any...

          
SECTION II: Mail/Connection Policies

  1. You can connect to Micronet via FTN, QWK or NNTP-not a combination of
     feeds.  Pick one and stick with it unless there is something drastic
     that requires a feed type switch.  This can only be done after the
     approval of the ZC and your current mail hub.  There is a possibility
     that depending on the type of feed you select, you will have to 
     reconfigure your mail setup for a new hub.

  2. Be aware that not all hubs support all mail transfer protocols.  The
     most common protocol for FTN connections is BinkP (BinkD).

  3. If you cannot connect your system properly within two weeks of your
     Micronet node application being approved and your uplink has not been
     notified by you about problems you may be having with your system, 
     your BBS will be removed from the network.

  4. If you have mail problems, please contact your hub FIRST before
     contacting me about Micronet mail problems.  I generally do not 
     keep track on what's going on "downstream" from me and I will 
     involve your hub anyway if there are problems with your system
     connecting to your hub.  If your hub's system is not answering 
     or if you suspect problems with your hub, DO let me know as 
     soon as possible so I can try to contact your hub directly.
     
  5. If your system will be down for longer than a day, please contact
     your uplink and let them know as soon as possible so we can put your
     mail on hold until your system is up and running again.  If your 
     system is unable to toss mail for a week and there is no notice
     from you, your system will be marked "down" in the nodelist.  After
     another week (two weeks total time) with no notice from you, your
     BBS will be removed from Micronet for no activity.  It is imperative
     that you contact your uplink or if there's problems contacting your
     uplink, contact me, and let us know what's going on with your system.

  6. Every Micronet hub has the authority to cut feeds without notice to you
     if they feel that, for any reason, remaining connected to your system
     will endanger their system's or Micronet's integrity.

  7. We will try to help you get Micronet set up as much as we can, but you
     really should know about your BBS's style of networking and how your
     BBS handles it before you join Micronet.  Each BBS is different and
     not everyone has experience with your particular setup.  While we 
     will try to help you with your connection, common sense and courtesy 
     dictate that you should already know how to run your BBS before you 
     start working with mail networks.  We all have our own BBSes to take 
     care of; we can't possibly hold your hand constantly to get you set up.

  8. Unless you are a designated hub for QWK/NNTP feeds, you absolutely
     CANNOT feed anyone else!  If you do so, that will lead to your immediate
     removal from Micronet.  Only the hubs the ZC designates are allowed to
     feed QWK/NNTP nodes for logistical reasons.

  9. Nodes are allowed to set up points for themselves and others.  In the
     case of creating a point for a personal mail system, a sysop is allowed
     to do so but I ask that you tell me that you are doing so as I will need
     to set things up here properly.  If you are creating a point for someone
     else, they MUST fill out a node application and be approved by the ZC
     before they are to be connected!  If you are caught feeding points that
     have not been approved by the ZC, that is cause for your immediate
     removal from Micronet.

If you have any questions about any of the above policies, please contact me
via netmail (preferred), email, or leave a private message for me on my BBS.

-- Sean Dennis
   Micronet Zone Coordinator

<EOF>
