F I D O N E W S -- Volume 14, Number 27 7 July 1997 +----------------------------+-----------------------------------------+ | The newsletter of the | ISSN 1198-4589 Published by: | | FidoNet community | "FidoNews" | | _ | 1-904-409-7040 [1:1/23] | | / \ | | | /|oo \ | | | (_| /_) | | | _`@/_ \ _ | | | | | \ \\ | Editor: | | | (*) | \ )) | Christopher Baker 1:18/14 | | |__U__| / \// | | | _//|| _\ / | | | (_/(_|(____/ | | | (jm) | Newspapers should have no friends. | | | -- JOSEPH PULITZER | +----------------------------+-----------------------------------------+ | Submission address: FidoNews Editor 1:1/23 | +----------------------------------------------------------------------+ | MORE addresses: | | | | submissions=> cbaker84@digital.net | +----------------------------------------------------------------------+ | For information, copyrights, article submissions, | | obtaining copies of FidoNews or the internet gateway FAQ | | please refer to the end of this file. | +----------------------------------------------------------------------+ ONE YEAR AGO THIS ISSUE! AND DRIVING ON MARS! Table of Contents 1. EDITORIAL ................................................ 1 One Year Ago, this Issue! ................................ 1 2. GUEST EDITORIAL .......................................... 2 Gulp? .................................................... 2 3. LETTERS TO THE EDITOR .................................... 3 FTSC Chairman retires in office? ......................... 3 How Do I get a Node number in Hong Kong? ................. 3 A remark concerning FSC-0093 ............................. 4 Found it! ................................................ 5 FTPoint in Zone 1 Wanted ................................. 6 Where does FidoNews go in Zone 3? ........................ 7 4. ARTICLES ................................................. 9 FidoSpine Distribution System Pledge ..................... 9 Observational Titbits .................................... 10 5. TRUE STORIES OF FIDONET .................................. 11 A True Story of FidoNet .................................. 11 6. FIDONET HISTORY .......................................... 14 History of Echomail - Part 1 ............................. 14 7. GETTING TECHNICAL ........................................ 27 No more "Getting technical" ? ............................ 27 8. COORDINATORS CORNER ...................................... 35 Nodelist-statistics as seen from Zone-2 for day 185 ...... 35 9. ECHOING .................................................. 36 ELIST Suspended for July ................................. 36 And more! FIDONEWS 14-27 Page 1 7 Jul 1997 ================================================================= EDITORIAL ================================================================= This is the Issue number where I took over the Editorial operation of FidoNews last year. It's STILL fun. [grin] This is quite a full Issue with lots of Echomail-related stuff and some odds and ends that came in at the last minute. One of the items is a note about the resignation of the FTSC Chairman, David Nugent [who is also ZC3]. This was first reported in several Sysop Echos and is confirmed here. Nugent is indeed resigning and is also leaving FidoNet. Along these lines, I sent direct Netmail to each Zone Coordinator asking for information, comment, and publication permission for any replies. They will appear here or in subsequent Issues as they arrive and are released for publication. Nugent advises that he has a few unpublished Proposals to get out and list updates to make before his successor takes over the Chairmanship and that will be done in the next weeks. Another is a plea for assistance from a fellow in Hong Kong who can't seem to get a Node number over there. Somebody help him, please. Speaking of the Comix section, if any .CMX come in that are political in nature, they will be reassigned to the Guest Editorial [.GUE] section so as not to confuse anyone. It also puts them up front. I forgot to add the two new sections mentioned in 1424 to the ARTSPEC doc. That omission has been corrected and the updated ARTSPEC.DOC has been hatched into the pipeline for the FIDONEWS file echo and ARTSPEC.ZIP into the SDS area SOFTDIST for further distribution. The entire ARTSPEC.DOC will be reprinted next week [due to space constraints this week] for information. Look for it once a year or whenever updated. The two, new sections are the .TRU and .FIC sections for FidoNet-related true stories or fiction. Both ARTSPEC.DOC and ARTSPEC.ZIP can be file-requested from this system or found on the FidoNews webpage and many other FidoNet file sources. And now that we've successfully put a robot rover on the surface of the planet Mars, maybe someone can tell me why FidoNet still doesn't have an International Coordinator? [How about that MARS MISSION?!!] C.B. ----------------------------------------------------------------- FIDONEWS 14-27 Page 2 7 Jul 1997 ================================================================= GUEST EDITORIAL ================================================================= --------------------------------------------------------------------- /`. o .^\ \ \, o o { \ / `~~~--__ { \___----~~' `~~-_ ______ _____ \ FidoSpine / a '~._(_||___)________/___ / /~~~~-, ,__. , /// __,,,,) Zone 1 Backbone__/\ \/ \/ `~~~; ,---~~-_`~= \ \------o-' \ / / / / '._.' _/_/ ';|\ (Art stolen from Jack Sargeant) ----------------------------------------------------------------- FIDONEWS 14-27 Page 3 7 Jul 1997 ================================================================= LETTERS TO THE EDITOR ================================================================= --- Following message extracted from NET_DEV @ 1:18/14 --- By Christopher Baker on Fri Jul 04 19:54:57 1997 From: Lisa Gronke To: Frank Ellermann Date: 02 Jul 97 14:18:32 Subj: Where O Where is the FTSC_Chair? 27-Jun-97, Frank Ellermann <2:240/5815.1> muttered to Christopher Baker in the NET_DEV echo: > BTW, you probably noticed it, 3:3/20 is not more listed, what > is the true FTSC now planning, elect another chair man ? Just > curious as always... greets, Frank Where O Where is the FTSC_Chair? I sent Internet email to David Nugent, davidn@csource.oz.au, and asked him. He said that he resigned as FTSC chair since he is leaving FidoNet at the end of July. His BBS is already offline due to lack of callers. He said he informed the other FTSC members of this fact about 3 weeks ago via the ftsc mailing list, but has gotten no response at all. He also says the ftsc web page will be disappearing at the end of July unless he finds a current member of the FTSC who is willing to maintain it. Origin: EastSide Data Services (1:105/61) -30- ----------------------------------------------------------------- Received: by yonet.org.hk (0.99.970109) From: any@yonet.org.hk (Chris Tang) Date: 06 Jul 97 12:10:17 +0800 Subject: fidonet Organization: YO!Net To: cbaker84@digital.net .o[-MAiL-FRoM-AnY-BoX-Of-Chris Tang-tO-cbaker84-]o. cd> yes. that is what the above means. send me your story and contact cd> info in an email msg and i will publish it in FidoNews tomorrow. ok..below are the details. (my English is not good actually :> ) btw, i hope u can give me a copy of fidonews which published FIDONEWS 14-27 Page 4 7 Jul 1997 this event via any@writeme.com, thanx.. --- Hi, i'm a sysop in Hong Kong, I met a problem of applying a fidonet node in Zone6 Host700. A few month before, I have tried to contact 6:700/0 via netmail, however, his system doesn't receive any netmail at all, I assumed that his mailer couldn't work properly. Later, luckily, i found his E-Mail address from fidonet nodelist and i sent him a E-Mail about apply a fidonet node in Z6H700 with my system information, he then replied within a day and told me that he would help me to do so. However, a few weeks later, i didn't get any reply from him any more. i then got a fidonet nodelist to see if my node had already inside or not, but it had no change at all in Z6H700 part of fidonet nodelist. So I tried to send him the second E-Mail to him about the applying of fidonet node, he has replied that he would do so. Again, no more reply was received from him. Luckily, i read Fidonews and find out some fidonet sysop contact methods from it for help. I wanna have a fidonet node because of the international purpose and the fidonet node is always required if being a bbs product oversea distro sites in order to prove that my system works properly. this is why i wanna join fidonet family. :) Now, i hope i can apply a fidonet node directly from ZC of Zone6 but i can't find his e-mail address (E-Mail is the unique contact method for me for contacting oversea). Anyone can help me about this? below are my contact methods. Name : Chris Tang E-Mail: any@who.net (text email only) any@writeme.com (file attach support) ICQ : 1251490 BBS : AnyWhere Board +852-2672-5505 [Hong Kong] -- Greetz, Chris Tang, any@who.net -= AnyW =- -30- ----------------------------------------------------------------- --- Following message extracted from NETMAIL @ 1:18/14 --- By Christopher Baker on Wed Jul 02 22:59:44 1997 From: Frank Ellermann @ 2:240/5815 FIDONEWS 14-27 Page 5 7 Jul 1997 To: Editor @ 1:1/23 Date: 03 Jul 97 04:18:00 Subj: fsc-0093.let A remark concerning FSC-0093 by Frank Ellermann, 2:240/5815.1@fidonet.org Hello Chris... I don't know how this *.LET submission type is meant to work, but at least I try to stay within the 70 columns limit. First an idea, how you could get more replies like this into FidoNews. Just replace the useless (?) publishing of pages in NEWSCHAT by posting of the complete articles there. Then whoever wants to answer can simply use the quote function of his news reader... et voila, a new article !? Two additions to your publishing of FSC-0093. Reduced seen-by lines are implemented in IMAIL version 1.85. If some users of this fine product weren't aware of it until today: Reduced seen-by lines are by far safer than tiny seen-by lines, because the vital informations to detect dup-rings automatically are preserved by reduced seen-by lines. So if you still use tiny seen-by lines today (and you're not by accident a zonegate :-), then please try reduced seen-by lines. Second point, it would be quite simple to extend FSC-0093 in a way that allows interzonal dup-ring detection. Still fully compatible with FSC-0074 (i.e. FTS-0004) of course, and mostly of interest for zonegates. Today it's almost impossible to detect multi-zone rings automatically, but based on the old SPTH-proposal it's possible to extend FSC-0093 in this direction... However, before I try it, there should be at least one zonegate (all those internet tunneling nodes, hi, that's you :-) really interested in using this method, if it's implemented in e.g. IMAIL or FASTECHO. "QOFM" to Chris, you probably know, that in practice FidoNews is the last working "official" glue keeping FidoNet together, don't you ? Tnx and bye, Frank -30- ----------------------------------------------------------------- Got my CRC problems solved... Anybody with a nodelist later than day 150 punch up Susana Baratta 4:851/7 The entry for this node contains high ascii characters at the end, some utils probably do not allow for this, so the CRC comes out incorrect! The bad file was NODEDIFF.157 which has a grunged entry. The CRC calculates correctly if the data type is changed from signed 8-bit FIDONEWS 14-27 Page 6 7 Jul 1997 (char) to unsigned char for the calculation... Therefore the CRC error message was correct because there was a problem, but incorrect because the checksum on the top line is accurate if you allow for the high-ASCII characters. I've really enjoyed figuring this out for myself. I've spent a lot of time testing my routines for CRC calculation, and come to the conclusion that any nodelist utility really should check a byte at a time for illegal characters. It may really slow things down, but it's probably for the best. L8r, Brainwave ... Yes, Socrates himself is particularly missed. -- |Fidonet: Brian Wood 1:362/903@fidonet.org |Internet: 903!Brian.Wood@river.chattanooga.net | | Standard disclaimer: The views of this user are strictly his own. | River Canyon Rd. BBS <=> Chattanooga OnLine! Gateway to the World. -30- ----------------------------------------------------------------- From: "Mikhail Ramendik" To: "cbaker84@digital.net" Date: Mon, 30 Jun 97 21:28:35 -0300 Reply-To: "Mikhail Ramendik" Subject: For FidoNews: FTPoint in z1 wanted This is for Fidonews. Please put it into the appropriate section. I am Mikhail Ramendik of Moscow, Russia, 2:5020/768.45, mikhram@dataforce.net I have a good command of English and want to receive some echos from the z1 backbone. Notably HOLY_BIBLE and company, HISTORY and MILHISTORY . Even though some of them do get to z2, they're SLOW!!! And HOLY_BIBLE is NOT here AFAIK... What I am searching for is a Point in Zone 1 with Mail transfer via FTP (or if impossible - via VMODEM). I am a Point since 1993, have software tuned OK, will never generate dupes and annoy the bossnode. (Yes I have seen the commercial hub list. I wish I could use such a hub, but transferring the bucks from Russia is impossible) If anyone can help me join Z1 please email! Thanks in advance! ---------------- Mikhail Ramendik -mikhram@dataforce.net FIDONEWS 14-27 Page 7 7 Jul 1997 FidoNet: 2:5020/768.45 Praise be to the Father, the Son and the Holy Spirit -30- ----------------------------------------------------------------- --- Following message extracted from NETMAIL @ 1:18/14 --- By Christopher Baker on Fri Jul 04 19:03:38 1997 From: John Gardeniers @ 3:632/360 To: Editor @ 1:18/14 Date: 28 Jun 97 20:56:50 Subj: Fidowhere.art Hi Editor, As I figure it's better in this format than none at all, and I do find artspec a little off-putting, I've decided to post this to you as a message. Do with it what you will. :-) regards, John ------------------------------------------------------------------ Fidowhere (Where can I get Fidonews?) by John "Fuse" Gardeniers (3:632/360.70) In FIDO1425 there was yet another comment about the unavailability of Fidonews, so I thought I'd share my own experiences in that regard. When I became a Fido point last late last year one of the things I looked forward to was getting a regular copy of Fidonews. This had always been intermittent, to say the least, on various local BBSes. Indeed, many BBSs around here don't even carry a single issue. :-( Having obtained lists of the available message and file areas I immediately proceeded to link to the Nodelist and Fidonews areas. "Great" I thought, I'll most likely get the first one within a few days. It was not to be. :-( After a couple of weeks I contacted my boss to try to find out why the news wasn't arriving. Not being a reader of it herself, my boss was a little surprised that Fidonews wasn't arriving at her system either. The system in question is a major mail hub, not just an end leaf. A few messages here an there soon revealed that Fidonews wasn't available locally, at least not via Fidonet. We did learn that it was readily available via Internet! The idea of having to use the Internet to obtain Fidonet's newsletter struck me as just a little absurd. Due to some persistence on the part of my boss we finally had Fidonews being delivered to these parts via Fidonet itself, as it always should have been. Am I the only one who finds at strange that so many sysops FIDONEWS 14-27 Page 8 7 Jul 1997 didn't bother chasing it up? We are in the largest network in the state, so many systems must have been affected by the unavailability of the newsletter. I wonder how many sysops currently believe that Fidonews has ceased to exist. On a slightly more critical note, the fact that so little effort appears to be put in by so many people to get a copy at all says quite a lot about it's value. :-/ -30- ----------------------------------------------------------------- FIDONEWS 14-27 Page 9 7 Jul 1997 ================================================================= ARTICLES ================================================================= FidoSpine Distribution System Pledge 1. The FidoSpine Distribution System recognizes all echoes as listed in the Echolist for June 1, 1997 (ELIST706.*) along with their first-listed moderator as the Moderator-of-Record. 2. The FidoSpine Distribution System will initially carry all Fidonet Zone one echoes that appear in the June 1997 echo listing, plus some that are not. The FidoSpine Distribution System will use it's own echo distribution list, FIDONET.NOW. The FidoSpine Distribution System does not require echo listing renewals or minimum traffic levels for any echo(s). 3. The FidoSpine Distribution System recognizes the Moderator-of- Record as the "owner" of their echo. As such all moderator requests for feed cuts are honored, provided that the moderator follows the path from the 'problem' system and works backwards. Any FidoSpine Distribution System hub retains the right to not distribute any echo who's moderator's actions causes too much of a burden on their system or well being. 4. The FidoSpine Distribution System recognizes the validity of Fidonet Policy 4.07 in determining the legality and appropriateness of messages carried in echomail. Since the Moderator-of-Record is the "owner" of the echo, The FidoSpine Distribution System recognizes the moderator's responsibility in maintaining the legality and appropriateness of message traffic in their echo(es). The FidoSpine Distribution System is not responsible for the content of echomail traffic. 5. The FidoSpine Distribution System will work toward establishing SuperHubs in each zone and region. The FidoSpine Distribution System does not mandate any specific routing scheme, and allows each zone, region, and net to adopt and use their own methods. The FidoSpine Distribution System, where netmail and other traffic is concerned, will use routing charts provided by recognized Fidonet Coordinators (as indicated in the Fidonet Nodelist). 6. The FidoSpine Distribution System distribution system will not interfere with any traffic in any echo, aside from eliminating duplicate messages ("dupes") and adding necessary routing information in accord with Fidonet Technical Standards. 7. The FidoSpine Distribution System will accept input from any moderator as to a request to carry his/her echo. We will NOT require multiple requests from various NEC's and REC's to 'authorize' distribution of any echo. All that is required is that the moderator have properly established an entry in the current Echolist, and make a request of the FidoSpine Distribution System to distribute his/her echo. 8. The FidoSpine Distribution System may, from time to time, FIDONEWS 14-27 Page 10 7 Jul 1997 establish, and distribute, technical criteria that messages must meet in order to be carried on FidoSpine. Such criteria may include, but not be limited to, definitions of character set, Origin Line length, age of messages, technical specifications of the SEEN-BY's, the PATH, the tearlines, and assorted control lines. Bob Seaborn, 1:140/1 Ed Georgen, 1:2222/258 Jerry Gause, 1:3651/9 Jim Balcom, 1:13/25 Peter Rocca, 1:2401/0 ----------------------------------------------------------------- Observational Titbits by Lee Kindness, 2:259/7 Well, just a couple of observations... 3:3/20, the FTSC Chair alias address is no-longer in the nodelist, what gives? A number of people have been trying to form a new FTSC (without an IC) but these guys should perhaps show a bit more common- sense (use NET_DEV rather than FTSC_PUBLIC due to NET_DEV having better distribution) and a bit more 'get-up-and-go' (like contact me about all those FTSC additions/revisions I published in Fidonews a couple of weeks back). I wonder if we'll ever see an FTSC entry in the nodelist ever again... Hell, a united world-wide Fidonet is looking very shakey... ftp.fidonet.org is now an alias for ftp.paonline.com rather than the IEEE server it used to be on. Interesting to note that only FSC documents up to fsc-0090 are on the site (up to fsc-0093 exist on ftp.blaze.net.au - the 'former' FTSC internet site) while the two 'fta' documents by the would be new FTSC are present... >From 2:259/7, In dis-united Scotland... -- Lee Kindness shazze@on.bright.yelly.bowls.com Fidonet 2:259/7 wangi@earthling.net hufunglun http://www.scms.rgu.ac.uk/students/cs_yr94/lk ----------------------------------------------------------------- FIDONEWS 14-27 Page 11 7 Jul 1997 ================================================================= TRUE STORIES OF FIDONET ================================================================= [This is the inaugural True Story of FidoNet. It's old but it's true. Send yours today!] Ed. [In 1989 I was injured on-the-job and had little and then no access to my FidoNet computer which was at work. The members of my Net at the time, built me a computer to use at home to operate the one at work remotely.] --Original post: This file is my way of expressing my gratitude to the members of my Net (FidoNet Net 1:135, SFLorida NET, Miami_FL_USA) for a holiday gift they presented me in mid-December. Composed on 5 Jan 89. A Holiday Ode to Net 135 by Christopher Baker RC 18 / NC 135 Twas two weeks before Christmas and all thru my house, my body was aching, I started to grouse. "If I don't dump this backache and get back to work my Users and Sysops will think I'm a jerk." I'd been laid up at home for many a week and I had no computer through which I could speak. It's tough to do business without a remote and I'm sure many NCs thought things I can't quote. All the while in the background quite unknown to me, the folks of my own Net were planning a spree. They talked and they chatted and gathered up parts to build me a system for home, bless their hearts. They Netmailed and Echoed and telephoned, too, deciding just which part was what and from who. They assembled a system that was based on a Tandy; with modem and hard drive, I mean, it's a dandy! I was tired and cranky the night it was due and had NO idea this dream would come true. I had pains in my back and a pain in my head but my wife kept insisting I not go to bed. It didn't seem normal the way she cajoled. It wasn't till later she said, "I was told." So unknown to me I was being prepared for a real demonstration of how my Net cared. It was close to eleven P.M. when I said, FIDONEWS 14-27 Page 12 7 Jul 1997 "I can't stay up longer. I'm going to bed." Then suddenly and very much to my shock came a tap on the door and then a loud knock. "Ho, Ho, Ho!", said a voice not too clear through the door. "Open up! I have presents for you by the score!" The door was thrown wide to allow the sprite in but he wasn't in red; not a hair on his chin. He was thin as a rail and no Santa was he. I recognized Peter; our own NEC. "What the heck's going on?" I exclaimed to the air. He said, "Just a token to show that we care." He said nothing else but went straight to his work and set up the system then he turned with a smirk. "No more excuses!", he said, "Now, get cracking!" "Your traffic's piled up and the stuff keeps on stacking!" I stood there dumbfounded, amazed and confused. My mind boggled speechless and he seemed amused. "What? How? Who and why?", I managed to say. "It's nothing", said he, "now, get back in the fray!" It wouldn't sink in that such things still take place that confirm all your faith in the rest of the race. The best I could do was to stammer my thanks and then write this poem to honor our ranks. I still can't believe it and simply must say, "All the folks in my Net, you made my whole day!" "I never can thank you enough for this gift." "Your generous act brings a permanent lift!" So, all of the rest out in FidoNet land, keep your faith that our concept continues to stand. The FidoNet concept of help and of sharing is here. Look around and you'll see people caring. It's never too late to put egos aside. Let go some bygones and take them in stride. This Network is people and people are kind. When your urge is to flame them, please keep that in mind. To all of my Net, I say "Thank you, nth times!" To the rest of the world who are sick of my rhymes I say "I hope the New Year will bring you much joy!" Now, I think I'll stop here and go play with my toy! [grin] The End Happy Holidays and Happy New Year to the wacky world of FidoNet! Christopher Baker MetroFire, 1:135/14(0), 305-596-8611 FIDONEWS 14-27 Page 13 7 Jul 1997 Miami_FL_USA SFLorida Net 135, Miami_FL_USA Roster of Net 135 Santas: 1 RAM-SOFT_Archive_Library, Miami_FL, David_Gilbert & James Gilbert 2 Eclectic_BBS, South_Miami_FL, Tark_Henderson 3 Medical_Software_Exchange, Miami_FL, Richard_Kaplan 4 The_Kendall_BBS, Miami_FL, Mike_Janke 5 CAP-BBS, Miami_FL, Duane_Ellis 6 Dungeons_of_Darkness_OPUS, Miami_FL, Mike_Jones 7 Miami's_First_Fido, Miami_FL, Al_DelaTorre 8 Coral_Gables_Medterm_BBS, Coral_Gables_FL, Mario_Diaz 9 EPICS_Opus, Hialeah_FL, Sandy_Schurtz 10 AMS_Support-Net_135_NEC, Miami_FL, Peter_Adenauer 11 Power_Station, North_Miami_FL, Mike_Lombana 12 Off-Duty_Inc._BBS, Miami_FL, Kathryn_Fanning 20 FrontDoor_Headquarters, Miami_FL, Joaquim_Homrighausen 24 TURBO-Soft, Homestead_FL, David_Kerley 27 Bitsy's_Place, Miami_Beach_FL, Henry_VanLeer 30 SMURFIT_Latin_America_Opus, North_Miami_Beach_FL, Jeff_Wolach 33 Byte_Size_Bits, Homestead_FL, Jean_Prophet & Buddy Prophet 34 The_Jailhouse, North_Miami_FL, Kenny_Star 35 The_Sober_Way_Out, Miami_FL, Robert_Egan 36 Town_Crier_Opus, Miami_Shores_FL, Orville_Bullitt 38 C-Board, Miami_FL, Jack_Bowman 39 The Expressions_BBS, Miami_Springs_FL, Daniel_Johnston 40 The_Cable_Connection, Miami_FL, Jerry_Iovine 41 BBS1-PC!, Miami_FL, John_Theed 43 Key's_Paradise, Key_West_FL, Steve_Froeschke 46 Bullitt_-_80_Opus, North_Miami_FL, Guy_Bullitt 47 MOBS_Opus_Humor_South, North_Miami_FL, Andrew_Adler 48 The_Road_Runner, Hialeah_FL, Luis_Hernandez 88 Chatterbox_BBS, Miami_FL, Marc_Moyantcheff 204 BerkShire_Board, Miami_FL, Bill_Kraski 901 Miami's_Personal_Consultant, Miami_FL, Dave_Steinman 942 wHy_bE_NoRmaL?, Miami_Fl, Tim_LaVan, 990 Friends_of_Dorothy, Miami_FL, Scott_Samet Thank you all for the fabulous Tandy T1000 w/20 meg hard drive, 1200 bps modem, 384K RAM, floppy drive and completely configured with DOS and programs! It is a gift I will always cherish and never forget. You ARE an amazing and generous bunch of people and Sysops! TTFN. Chris -30- [That was a long time ago but I haven't forgotten that most of the folks in our net are not rotten.] [grin] Ed. ----------------------------------------------------------------- FIDONEWS 14-27 Page 14 7 Jul 1997 ================================================================= FIDONET HISTORY ================================================================= [This an abortive chapter of FidoNet History from 1989. This is the original EchoPol that was 'ratified' and then revoked by the IC of the period {David Dodell} as non-representative. With the recent REC Echomail effort, it might be well to reflect upon that which has not been enacted for going on ten years after Policy4. It has been reformatted to 70 columns for FidoNews and the spelling and punctuation corrected where necessary. The original is available at 1:18/14 for file-request as ECHOPOL.] Ed. GENERAL ECHOMAIL POLICY 1 April 22nd, 1989 PROLOGUE This document sets forth policy governing Echomail conferences and their distribution. If any item in this policy is in conflict with any existing or subsequent General FidoNet Policy, then General FidoNet Policy will be in effect. This Policy applies to Zone One Backbone Echomail conferences and to any other conferences for which the Moderator desires it to be applicable. Future changes to Echo Policy may be proposed by any FidoNet Sysop by submitting the proposal to their REC. The REC will then determine if the proposal should be brought before the rest of the RECs. If an REC decides not to bring a proposed change before the rest of the RECs, a message stating why must be sent. If 10% or more of the NCs and NECs in a region request that a proposal be brought before the RECs then that proposal must be brought before the RECs. A majority vote of the Regional Echomail Coordinators is required in order for a proposal to be formally voted on. If 10% or more of the NCs and NECs in the Zone request that a proposal be formally voted on, then that proposal must be formally voted on. Those eligible to vote on any proposals made by the REC structure will be the ZEC, RECs, NECs, NCs, RCs and ZC. Only one vote per person is allowed. Adoption of changes will require a simple majority of those voting to pass. In this document, "a simple majority" means more than 50 percent of those voting. A good faith attempt must be made to make all potential voters aware that a vote is occurring and make available all necessary information. I. HISTORY FIDONEWS 14-27 Page 15 7 Jul 1997 Echomail consists of the sharing of message bases or conferences between various independent network addresses. The Echomail concept started with a series of programs by Jeff Rush. Since the original implementation, many authors have written programs improving on the original idea. In spite of worries that the flow of Echomail would increase Netmail traffic to the point that the Network would collapse under its own weight, Echomail has been a success. To simplify the distribution of Echomail, a national Echomail Backbone formed whose primary purpose is the distribution of Echomail at a national level. Of recent introduction to the Backbone system has been the generous contribution of the Echomail Stars. As a result of the growth of Fidonet and the increase in the volume of Echomail, it has become necessary to set forth a formal policy governing Echomail. II. DEFINITIONS 1. ECHOMAIL: The process of sharing message bases between independent systems with unique net/node addresses. 2. ECHOMAIL CONFERENCES: An Echomail conference is a message base of forum design distributed under a specified conference name dealing with a defined area of interest. Notable examples include TECH, the National Technical Conference and COMM, the National Telecommunications Conference. 3. MODERATED CONFERENCE: A moderated conference is an Echomail conference for which a moderator has been appointed to supervise the flow and content of the conference. All conferences carried on the Backbone must be moderated. 4. SYSOP-ONLY CONFERENCE: A Sysop-Only Conference is one in which the Moderator has decided that the conference will be made available only to Sysops and not to users. 5. RESTRICTED DISTRIBUTION CONFERENCES: A restricted distribution conference is one which is restricted only to eligible recipients. Notable examples include REGCON, the Regional Coordinators Conference, COORD, the National Echomail Coordinators Conference, and MAGICK, a pre-register Echomail Conference. 6. ZONE ECHOMAIL COORDINATOR (ZEC): This individual is responsible for coordination of Echomail on a FidoNet Zone level. 7. REGIONAL ECHOMAIL COORDINATOR (REC): This individual is responsible for coordination of Echomail within his region. 8. NET ECHOMAIL COORDINATOR (NEC): This individual is responsible for coordination of Echomail at the Local Net level. 9. ECHOMAIL Backbone: The Echomail Backbone consists of FIDONEWS 14-27 Page 16 7 Jul 1997 voluntary members who provide services to enhance the national distribution of Echomail. The Backbone consists of nodes which handle a high volume of Echomail traffic and are responsible for distribution of Echomail down to the regional level. 10. NATIONAL ECHOMAIL LIST: The National Echomail List identifies the available national conferences, the conference moderator and requirements of the specified conference. The ZEC will appoint the keeper of the National Echomail List. 11. AUTOMATED CENSORSHIP: The term Automated Censorship refers to programs which cause messages to be removed from the intended conference or have their content altered. 12. FIDONET POLICY: The document which governs Fidonet as adopted by Fidonet. The document as of this writing is Policy3 and is subject to change. This policy is intended to become a part of general Fidonet policy. Until it is incorporated into General Fidonet policy, this document shall serve to define policy violations occurring in Echomail. 13. OPEN ACCESS CONFERENCE: This is a non-restricted conference open to all users who are willing to follow the posted conference rules. 14. TERMINAL NODE: A system which does not process echomail for pickup by another system. III. DUTIES OF ECHOMAIL COORDINATORS 1. GENERAL: It is the duty of the *ECs to make available to any Fidonet Sysop, any conference which the Sysop is not prohibited from receiving by not meeting requirements as mandated by the conference moderator. If for any reason the *EC does not have access via recognized distribution channels to a specific conference, they can not be expected to pass it on. If a *EC fails to make available any conference to qualified lower distribution levels, this shall be deemed to have violated the outlined duties of the position held. Such violation is cause for the removal as provided by this document. Nothing in this provision requires that a *EC must import any conference to the extent of adverse economic impact. It is recommended that cost sharing arrangements be employed. Where financially feasible for the supplier any conference on the Backbone must be made available (other than restricted conferences) when requested. An exception is when a *EC cuts a link to end unauthorized distribution of a conference. In this case, some otherwise authorized nodes may temporarily lose their link. FIDONEWS 14-27 Page 17 7 Jul 1997 A *EC shall do everything in their power to insure that: 1. All downstream links are educated as to this policy. 2. Downstream links know how to properly link into conferences. 3. Acceptable and unacceptable behavior in echomail conferences is explained. 4. Downstream links are not engaging in topologies that increase the risk of duplicate messages. 2. DUTIES OF ZONE ECHOMAIL COORDINATOR: It is the duty of the ZEC to coordinate the connections between the Echomail Backbone on both an inter-Zone and intra-Zone level as well as coordination of inter-regional connections. The ZEC will coordinate transmission of Echomail and to provide for routing in a manner that will avoid the transmission of duplicate messages within the same conference. It is also the duty of the ZEC to monitor compliance with this policy on both a national and international basis. 3. DUTIES OF REGIONAL ECHOMAIL COORDINATOR: It is the duty of the REC to provide for regional Echomail distribution. In addition, the REC will coordinate any inter-regional cross- linking of conference feeds with the REC of the participating region with the direct knowledge of the ZEC. The REC will provide for transmission and routing of Echomail within his/her region in a manner to avoid creation of duplicate messages within the same conference. It is the duty of the REC to monitor compliance with this policy at a regional level. 4. DUTIES OF NET ECHOMAIL COORDINATOR: It is the duty of the NEC to coordinate the intra-net Echomail and to cooperate with the REC and NECs of other nets to arrange for the inter-net transmittal of echomail. The REC may require the NEC to provide links for independent (regional) nodes. The NEC shall maintain a list of available Echomail Conferences within the net as well as the requirements of each Conference area as supplied by the conference moderator (Echolist). The NEC shall also monitor compliance with this policy at a net level. 5. DUTIES OF ECHOLIST COORDINATOR: It is the duty of the Echolist Coordinator to compile and make available a listing of national and international Echomail conferences and, optionally, conferences at various local levels. The content and format of the Echomail listing shall be at the sole discretion of the Echolist Coordinator, but shall include the conference name and moderator for each conference. The Echolist Coordinator shall also maintain a list of requirements applicable to each listed conference. 6. DUTIES OF ECHOMAIL CONFERENCE MODERATOR: It shall be the duty of the Echomail Conference Moderator to make in good faith every reasonable effort to insure that the moderated FIDONEWS 14-27 Page 18 7 Jul 1997 conference does not distribute or promote illegal activities or information as defined below in Section V Paragraph 2. The Moderator shall be responsible for insuring that messages contained in the conference corresponds to the conference theme. The Moderator shall report any violations of this policy to the proper Echomail coordinators and lodge any appropriate policy complaints as provided for in policy documents adopted by Fidonet. The Moderator shall post the conference rules in the conference at least once a month. The Moderator is to authorize the disconnection of the conference feed. Any Sysop the moderator believes is violating policy shall be reported to the offending node's nearest local echomail coordinator (may be a NEC, REC or in extreme situations, a ZEC); and the moderator shall formally authorize the feed to the offending node to be severed. The conference moderator is the sole judge - subject to review only by the ZEC (or his delegates) if a complaint is filed by the banished party. The Moderator may request in direct written form (netmail) that the *ECs disconnect a node from the conference when that node refuses to follow the published conference rules after at least 3 warnings. Knowingly feeding a conference to a node that has been severed by the Moderator is considered a violation of this echomail policy and is subject to suspension. The length of this suspension will be determined by a joint decision of the conference moderator and the nearest local echo coordinator of the node illegally feeding the conference to the original offending node or point. Echo conference complaints from a Sysop should be filed at the net level (NEC) or if the complaining party is an independent node then with their REC. The NEC or REC receiving such a complaint must take action in accordance with the provisions of this echomail policy. For severe or chronic infractions, the NEC, REC, or ZEC may file a complaint under general Fidonet policy for excessively annoying behavior. IV. APPOINTMENT AND ELECTION OF ECHOMAIL COORDINATORS AND MODERATORS. 1. GRANDFATHER CLAUSE: Those Zone, Regional, and Net Echomail Coordinators and Echomail Coordinators currently holding these positions as of the date of acceptance of this Echomail Policy shall continue to service in said capacity until resignation or replacement under this policy. 2. ELECTION OF ZONE ECHOMAIL COORDINATOR: The ZEC shall be elected as follows: a) upon resignation or replacement of the existing ZEC, the FidoNet Zone Coordinator (ZC) shall nominate at least five individuals to be voted upon. FIDONEWS 14-27 Page 19 7 Jul 1997 b) 10 days after the nominees are selected, an election