• Re: FBS EL209 ==9 ==> Echo has been Flagged for Deletion ???.

    From Paul Hayton@3:770/100 to Vincent Coen on Tue Dec 5 12:35:26 2023
    On 04 Dec 2023 at 02:15p, Vincent Coen pondered and said...

    Thank for that but I will still have to try and find out why it happened and fix it.
    Found somewhere it could be happening but do not understand why yet :(

    all good, and best wishes :)

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Vincent Coen@2:250/1 to All on Mon Dec 4 23:51:10 2023
    Hello All!

    Tuesday December 05 2023 12:35, Paul wrote to me:

    On 04 Dec 2023 at 02:15p, Vincent Coen pondered and said...

    Thank for that but I will still have to try and find out why it
    happened and fix it. Found somewhere it could be happening but do
    not understand why yet :(

    all good, and best wishes :)

    Just a note that I have made changes to the code but only next month or two will show if it is the correct fix.

    However to help research this for the next few months I have included additional text after the text Warning Cnt with Status n where n can be 0 - echo is in a normal state, 1 = Expriy warning issued and lastly which should NOT occur 2 = deleted (transferred to the backbone).

    At some point we all need to look at your message bases to see if the echos in BACKBONE network contain real traffic (i.e., not rules postings, or hello any one here etc messages). In which case I can remove the dead wood - OK echos.

    This applies more to the echo Hubs having checked with their uplink to confirm they are linked.

    From here at 2:250/1, there is a fair number of them that are empty of traffic.

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.8.4/GoldED+/LNX 1.1.5-b20180707
    * Origin: The Elist Maintainer (2:250/1)