home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   ELIST      [ADM] ELIST Conference      7,279 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 6,161 of 7,279   
   Vincent Coen to All   
   Action on Expiry of an echo   
   02 Feb 24 15:02:21   
   
   MSGID: 2:25/0@fidonet 65bd0803   
   CHRS: UTF-8 2   
   TZUTC: 0000   
   TID: MBSE-FIDO 1.0.8.4 (Linux-x86_64)   
   Hello All!   
      
   Messages reporting that an echo HAS expired is is due to be deleted is not   
   actually correct in that the echo is transferred over to BACKBONE from ELIST   
   and that the moderator on record will change to elistmaint.   
      
   elistmaint does NOT actually do any moderating but is assigned as that is the   
   way the Elist software works in order not to lose the echo.   
      
   This may mean that some echos's that are now dead of traffic should be Deleted   
   - at least of effective (meaning no user postings but could be postings of   
   rules or an 'Anyone here' message) traffic.  These type of postings should be   
   ignored in working out if the echo is dead as such clearly do not signify that   
   it is active.   
      
   If an echo is in fact dead of traffic and has been for some time such as 12   
   months etc, then a ELIST reader can report this fact here so if no one says   
   otherwise (traffic wise) then the echo can be deleted by the Elist maintainer   
   - currently myself.   
      
   This helps to keep the BACKBONE list as up to date as possible with minimum   
   effort while also helping to double check if an echo is dead as there can   
   always be a break in connectivity for some BBS systems.   
      
   So Posting a request HERE, will allow others to verify that their system is   
   also showing a dead echo. Clearly any one who actually has read traffic can :   
      
   1. Examine Echo in question to verify this, excluding postings of Rules or   
   anyone here etc as they do NOT count as real traffic.   
      
   2. Report an echo that does have traffic where we can request their uplink   
   details and the path information to see what they have a disconnect for that   
   echo.   
      
   It all helps in trying to maintain successful Echo systems.   
      
   While this is really geared for Fidonet it can be used for any other network   
   using this facility such as FSXNET etc. We all lead some times busy lives and   
   do not always keep up to date with echo traffic so this function will help us   
   all.   
      
   .. and yes I know I have repeated some elements of the explanation but that is   
   to help insure that one one misses it :)   
      
   Vincent   
      
   --- Mageia Linux v8 X64/Mbse v1.0.8.4/GoldED+/LNX 1.1.5-b20180707   
    * Origin: The Elist Maintainer (2:25/0)   
   SEEN-BY: 1/120 10/0 1 15/0 18/0 200 25/0 21 50/109 90/1 102/401 103/1   
   SEEN-BY: 103/705 105/81 106/201 116/116 123/0 25 180 200 755 3001   
   SEEN-BY: 128/260 129/305 135/115 225 153/7715 214/22 218/0 1 215 601   
   SEEN-BY: 218/700 720 840 850 860 870 880 930 221/1 6 222/2 226/30   
   SEEN-BY: 227/114 229/110 112 113 206 307 317 400 426 428 470 664 700   
   SEEN-BY: 240/1120 250/0 1 3 4 5 6 7 8 11 13 14 263/0 266/512 275/1000   
   SEEN-BY: 280/464 282/1038 291/111 292/854 299/6 301/1 113 320/219   
   SEEN-BY: 322/757 335/364 342/200 396/45 460/58 467/4 888 633/280 712/848   
   SEEN-BY: 712/1321 2320/105 3634/0 12 24 27 56 57 119 5001/100 5005/49   
   SEEN-BY: 5020/715 846 1042 4441 5030/49 5054/8 5061/133 5075/35 128   
   SEEN-BY: 5083/444 5090/958   
   PATH: 250/1 3634/12 5020/1042 301/1 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca