1. Forum
  2. FidoNet
  3. ELIST

  • 2nd FDECHO update attempt

    From mark lewis@1:3634/12 to Vincent Coen on Wed Apr 22 16:05:59 2020

    can you tell me the status of the 2nd attempt to update the FDECHO listing? i added myself as COMOD1 and resent it because the first attempt seemed to be rejected because it was not from the listed moderator... it is one of those echos i provide an elist updating service for... i do not recall seeing a response from the bot concerning it...


    )\/(ark
    --- SBBSecho 3.10-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Vincent Coen@2:250/1 to mark lewis on Thu Apr 23 13:18:47 2020
    Hello mark and every one else!

    Wednesday April 22 2020 16:05, you wrote to me:


    can you tell me the status of the 2nd attempt to update the FDECHO
    listing? i added myself as COMOD1 and resent it because the first
    attempt seemed to be rejected because it was not from the listed moderator... it is one of those echos i provide an elist updating
    service for... i do not recall seeing a response from the bot
    concerning it...

    You made a mistake in the first submission of this sequence:

    You should have set the FROM keyword to that of the moderator when also
    setting COMOD1 up as elist detected the update was not from a moderator.

    The trick is to get the mod to set a comod up as you, and submit that file.

    Then when that gets a error free ack, send in the next one with your name/address as FROM and do anything else needed.

    elist would confirm the change was from one of the Co Mods and act upon it.

    It this clear ?

    These checks are to ensure that only a moderator can make changes along with any co moderator (this is a addition) as previous versiosn did not allow for this.

    Hopefully this will help a comod to take over an echo even if temporarily when a mod is unable or has left the net.

    One of the benefits of all echos having at least one co mod as a back up, but that does 'assume' the comod's have a copy of the mod-upd submission file
    which includes the password and are requested to keep an eye out for the WARNING expiring message at least from 2. This is the reason why all
    such warnings from 2 onwards are also posted to all comods as well.

    Vincent

    --- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
    * Origin: The Elist Maintainer (2:250/1)
  • From Vincent Coen@2:250/1 to mark lewis on Thu Apr 23 13:35:08 2020
    Hello mark!

    Wednesday April 22 2020 16:05, you wrote to me:


    can you tell me the status of the 2nd attempt to update the FDECHO
    listing? i added myself as COMOD1 and resent it because the first
    attempt seemed to be rejected because it was not from the listed moderator... it is one of those echos i provide an elist updating
    service for... i do not recall seeing a response from the bot
    concerning it...


    You are now a comod but the verification went to the MOD as I made him the subject in the FROM keyword.

    Now YOU can make any changes.

    Use this method for any other echos that have this issue.

    Vincent

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