MSGID: 2:25/0@fidonet 6596dc3d   
   CHRS: UTF-8 2   
   TZUTC: 0000   
   TID: MBSE-FIDO 1.0.8.4 (Linux-x86_64)   
   Hello All!   
      
   A reminder that all echo's that expire are automatically moved over to the   
   Backbone file as taken over by elistmaint as moderator and this is because    
   that   
   is the only way the Elist software can work. This process occurs between TWO   
   and THREE months after the first message advising of expiry which is 10 months   
   after last update (which is always extended to the last day of the month),   
   i.e., 1 month for the first warning, one for warning of deletion followed by   
   the final warning of actual, hence the reasoning of 13 months in all from the   
   last echo update being submitted.   
      
   The extra time allows for people being on holiday or working away for up to 13   
   weeks.   
      
   Clearly it is wise to have this Echo on your read list with your message    
   reader   
   of choice.   
      
   In fact elistmaint is NOT a moderator in any way other than looking after the   
   listing of the specific echo.   
      
   Clearly if a moderator wishes to delete an echo, usually due to to no traffic,   
   they can do so in the normal way by submitting a file with MOD-DEL in place of   
   MOD-UPD and that will actually delete the echo from the system.   
      
   Next is regarding Echo's that are only on BACKBONE.RPT / .NA lists and here   
   they stay unless traffic is zero (excluding rule or 'Anyone here' type posts.   
      
   For these, I have been a bit lax and will have to look through them and    
   compare   
   traffic at 2:250/1 which does get the lot but I did a clean up early last year   
   removing dead wood (zero traffic for 12 months or more) but may be time for   
   another cycle.   
      
   Any ELIST reader can advise that this is the case for any echo's they have   
   noticed in their system having checked with uplinks that there is a connection   
   from them to uplink and uplink from where ever they are connected to.  These   
   requests should be posted here so every one can see then and check with their   
   own system to confirm traffic volume.   
      
   At which point they will get deleted.   
      
   Note that Elist software creates and updates files BACKBONE.NA and    
   BACKBONE.RPT   
   where the former can act as the master list of echos for you mail tossing   
   program that can then auto add them in to your system without any manual   
   involvement.  Well that is the way it works here using mbse as the mailer,   
   file, echo & mail tossing software.   
      
   As you may well be aware that there is a lot of echos's listed in BACKBONE.RPT   
   with many having NO Description and this is because they were brought over    
   from   
   the last one produced by Ben's system in 2019 or where about.   
      
   Again if an echo is active with no description and possibly no title and you   
   know it please provide then to myself so I can update the system.   
      
   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 15/0 18/0 200 25/0 21 90/1 103/705 105/81 106/201 116/116   
   SEEN-BY: 123/0 25 180 200 755 3001 124/5016 128/260 129/305 135/115   
   SEEN-BY: 135/225 153/757 7715 154/30 203/0 218/700 221/0 1 6 222/2   
   SEEN-BY: 226/30 227/114 229/110 112 113 206 307 317 400 426 428 470   
   SEEN-BY: 229/664 700 240/1120 5832 250/0 1 3 4 5 6 7 8 11 13 14 263/0   
   SEEN-BY: 266/512 275/1000 280/464 5003 282/1038 291/111 292/854 8125   
   SEEN-BY: 299/6 301/1 113 310/31 320/219 322/757 335/364 341/66 234   
   SEEN-BY: 342/200 396/45 423/120 460/58 128 256 1124 467/4 888 633/280   
   SEEN-BY: 712/848 1321 770/1 2320/105 3634/0 12 24 27 56 57 119 5001/100   
   SEEN-BY: 5005/49 5020/400 715 846 1042 4441 5030/49 5054/8 30 5061/133   
   SEEN-BY: 5075/35 128 5083/444 5090/958   
   PATH: 250/1 3634/12 5020/1042 301/1 280/464 460/58 229/426