REPLY: 2:280/464 64c9f9b2   
   MSGID: 2:250/1@fidonet 64ca7261   
   CHRS: UTF-8 2   
   TZUTC: 0100   
   TID: MBSE-FIDO 1.0.8.4 (Linux-x86_64)   
   Hello Wilfred!   
      
   Wednesday August 02 2023 08:35, you wrote to me:   
      
    > Hi Vincent,   
      
    > On 2023-08-01 16:30:01, you wrote to Mike Powell:   
      
    ==>>> Echo Successfully Updated.   
      
    VC>> EL210 ==> Rules file WEATHER.TROPIC.RUL has been Updated.   
      
    VC>> TAGname: WEATHER.TROPIC                      Group: FIDO   
      
    VC>>   TITLe: International Tropical/High Seas Weather Alerts   
      
    VC>>   Language:     ENGLISH   
      
    VC>>   DESCription:   
    VC>>     This echo is a companion to the Z1 WEATHER echo.   
    VC>>     This echo contains tropical weather advisories for the   
    VC>> Atlantic   
    VC>>     Pacific, and Indian Oceans, as well as high seas forcasts/   
    VC>>     advisories.  Discussion of tropical systems is also on-topic   
    VC>>     and encouraged.   
      
    > In the ELIST.RPT for this month it is shown as:   
      
    >   DESCription:   
    >>> THERE IS NO DESCRIPTION ON FILE FOR THIS ECHO <<   
      
      
    > In the previous edition it was ok...   
      
   Update rerun and seems to be correct.   
      
   I have no idea why this happened for this area as the other updates appears to   
   be ok - unless you know different.   
      
   Please advise if you find any other oddities.   
      
   Annoyingly, if it happens again I will have to rebuild the program to produce    
   full run time trace that will show the code executed to see if the issue can    
   be   
   located although it will be a right pain to trace the actual code for THAT   
   specific echo other than by counting.  Tracing produces a lot of output.   
      
   I seem to recall this has happened in the past for THIS echo, most odd.   
      
   Looking at the submission file the only may be oddities are it has mod and   
   comod with email addresses but nothing that looks wrong, volume that is very   
   high but cannot test it as it one of the few echos that I am not getting -   
   possibly because of zero traffic as I cleared out last year a lot of dead   
   wood. Needless to say that could not be a logical reason for the issue as    
   elist   
   does not check volume against actual, although early on it did but was   
   presenting possible problems if my system was losing any traffic (unlikely but   
   possible). Yet another feature that was removed as unneeded but may be nice to   
   have.   
      
   @Mike Powell, if you are reading this pls change the volume to what is actual   
   occurring for the echo as I find it very hard to take that 1,500 per month is   
   any where near actual count on any fido echo let alone this one.   
      
   Vincent   
      
   --- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707   
    * Origin: The Elist Maintainer (2:250/1)   
   SEEN-BY: 1/123 15/0 18/200 25/0 21 90/1 105/81 106/201 123/131 129/305   
   SEEN-BY: 153/7715 218/700 221/1 226/30 227/114 229/110 112 113 206   
   SEEN-BY: 229/307 317 400 426 428 470 664 700 250/0 1 3 4 5 6 7 8 11   
   SEEN-BY: 250/13 14 263/0 266/512 275/1000 282/1038 291/111 292/854   
   SEEN-BY: 317/3 320/219 322/757 342/200 396/45 460/58 467/4 633/280   
   SEEN-BY: 712/848 1321 3634/12 5075/35   
   PATH: 250/1 292/854 229/426