Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    ECHOLIST    |    [ADM] EchoList Access Conference    |    11,388 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 11,195 of 11,388    |
|    Vincent Coen to All    |
|    Echo's listed in ELIST system    |
|    09 Jan 22 16:29:52    |
      MSGID: 2:250/1@fidonet 61db2464       CHRS: UTF-8 2       TZUTC: 0000       TID: MBSE-FIDO 1.0.7.24 (GNU/Linux-x86_64)       Hello All!              I do encourage submissions for echo's not currently listed that may be on the       non-backbone backbone if they are active and/or some one will be promoting        them       in one or more of the various advert echo's.              You may submit these in the the name of ElistMaint / elistmaint (text case       immaterial to me as a email or netmail included (.ECO) type file content and I       will include them as soon as I modify the elist sources to cater for this.              Using emlistmaint is a catch all without the requirement of having to take        over       an echo area but allows any one interested in doing so to look after any such       listings.              It would help if there is a system acting as an origin/source for a echo to       specify it on the - wait for it, using the keyword ORIGin :)              The idea is to make elist have a more full view of echo's that are out there       that can be made available to all via the 'backbone' Hub system.              For example Dallas Hinton has around 900+ areas (some of which are usegroup       type areas but the rest look - well dead or should be as they relate to very       dead software - where the vendors have long gone but the others might well        come       back to life.              Small point, just because a echo is dead for a period say 12 months does not       mean it cannot come back to life with a bit of promotion (adverts etc) how        ever        may be 2 years, it should be considered DOA. Thoughts?              Don't forget the elist system can handle other nets other than Fido just add       them in with the Network name defined as required and the three reporting        files       will be generated at the same time as Fido and the current addition FSX.       Please use where ever possible the standard short designation for the network       name, even more so if it has a long name. The software has a list of these       other networks (that can be added too) that I list here showing the short and       long names (note that one has a possible extra long name) :              --        "ADV" "ADVNET"        "FIDO" "FIDONET"        "FMLY" "FMLYNET"        "FSX" "FSXNET"        "GAMES" "GAMESNET"        "GATOR" "GATORNET"        "GMS" "GMSNET"        "JUSTAX" "JUSTAXNET"        "LEAGUE10" "LEAGUE10NET"        "LINUX" "LINUXNET"        "MICRO" "MICRONET"        "PASCAL" "PASCALNET"        "RMINI" "RMININET"        "SDS" "SDSNET"        "STN" "STNNET" "STNET"        "VIR" "VIRNET"        "XNET"        "ZENET"        "ZYXEL" "ZYXELNET".       --              If there is any missing send a netmail or email and advise.       Netmail to 2:25/21 or 2:250/1 or a email to vbcoen |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca