1. Forum
  2. FidoNet
  3. ELIST

  • MUFFIN EL230 Errors found in MOD submission, see messages:

    From Vincent Coen@2:250/1 to Sean Dennis on Wed May 13 13:30:01 2020

    EL230 Errors found in MOD submission, see messages:

    EL219 Error Unknown keyword found: TOT
    EL204 Error Messenger (From) is missing.


    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: The Elist Maintainer (2:250/1)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Mar 10 00:30:01 2021

    EL230 Errors found in MOD submission, see messages:

    EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Sean Dennis, 1:1


    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: The Elist Maintainer (2:250/1)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Mar 10 01:30:01 2021

    EL230 Errors found in MOD submission, see messages:

    EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Sean Dennis, 1:1


    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: The Elist Maintainer (2:250/1)
  • From Sean Dennis@1:18/200 to Vincent Coen on Tue Mar 9 20:08:15 2021
    Hello Vincent,

    Wednesday March 10 2021 00:30, you wrote to me:

    EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Sean Dennis, 1:1

    I don't have a COMOD line in that ECO file, Vince. What would be causing the problem with that? Please note for MUFFIN and TUB, I use 1:1/110, a zone-level address that's in the nodelist.

    Later,
    Sean

    --- GoldED/2 3.0.1
    * Origin: Outpost BBS * bbs.outpostbbs.net:10123 (1:18/200)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Mar 10 15:26:08 2021
    Hello Sean!

    Tuesday March 09 2021 20:08, you wrote to me:

    Hello Vincent,

    Wednesday March 10 2021 00:30, you wrote to me:

    EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from
    Sean Dennis, 1:1

    I don't have a COMOD line in that ECO file, Vince. What would be
    causing the problem with that? Please note for MUFFIN and TUB, I use 1:1/110, a zone-level address that's in the nodelist.

    You are sending in a update addressed in FROM, MOD etc as 1:1/110 BUT in the existing data for this echo the address is for 1:18/200 for FROM, REPLY-TO, MOD
    and ORIG although for this one it is only as referenced so not checked for.

    Resubmit again but using the registered address in all these fields.

    Vincent

    --- Mageia Linux v7.1 X64/Mbse v1.0.7.21/GoldED+/LNX 1.1.5-b20180707
    * Origin: The Elist Maintainer (2:250/1)
  • From Sean Dennis@1:18/200 to Vincent Coen on Wed Mar 10 18:09:01 2021
    Hello Vincent,

    Wednesday March 10 2021 15:26, you wrote to me:

    Resubmit again but using the registered address in all these fields.

    Okay. So if I want to use the other address, I should send in a MOD DEL with the current address, wait for the echo to be removed, then send in a MOD ADD with the new address?

    Later,
    Sean

    --- GoldED/2 3.0.1
    * Origin: Outpost BBS * bbs.outpostbbs.net:10123 (1:18/200)
  • From Vincent Coen@2:250/1 to Sean Dennis on Thu Mar 11 17:34:47 2021
    Hello Sean!

    Wednesday March 10 2021 18:09, you wrote to me:

    Hello Vincent,

    Wednesday March 10 2021 15:26, you wrote to me:

    Resubmit again but using the registered address in all these
    fields.

    Okay. So if I want to use the other address, I should send in a MOD
    DEL with the current address, wait for the echo to be removed, then
    send in a MOD ADD with the new address?

    You can but there are other ways of sorting this out :


    1. Send in an amended MOD-UPD in the name and address of the existing MOD
    with the keyword FROM name, address
    Change MOD to the new address if only that is changed (i.e., not the name).
    Update keywords ORIG if needed

    Wait for the update process to check if it worked then update your master copy of the MOD-UPD file so that the old address in all keywords is changed to the new.

    2. As in (1) with FROM and but here add keyword COMOD1 name, new address
    In a new MOD-UPD file say called ECHONAME2.ECO (as they are done in
    alphabetic order) Change FROM, MOD and ORIG to the new address.

    3. Now using the new address issue keyword COMOD1 DELETE

    Process complete providing system did not find any errors with your submission such as spelling etc.

    Vincent

    --- Mageia Linux v7.1 X64/Mbse v1.0.7.21/GoldED+/LNX 1.1.5-b20180707
    * Origin: The Elist Maintainer (2:250/1)
  • From Vincent Coen@2:250/1 to Sean Dennis on Thu Dec 23 22:30:01 2021

    EL230 Errors found in MOD submission, see messages:

    EL213 UPD to non existing area - Rejected.


    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: The Elist Maintainer (2:250/1)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Feb 9 20:30:01 2022

    EL230 Errors found in MOD submission, see messages:

    EL213 UPD to non existing area - Rejected.


    --- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
    * Origin: The Elist Maintainer (2:250/1)
  • From Elistmaint@2:25/21 to SYSOP on Mon Feb 6 11:30:02 2023

    EL230 Errors found in MOD submission, see messages:

    EL233 Error GROUP not specified.


    --- MBSE BBS v1.0.8 (Linux-armv7l)
    * Origin: Elist Maintainer at 2:25/21 (2:25/21)
  • From Elistmaint@2:25/21 to All on Wed Feb 8 09:30:01 2023

    EL230 Errors found in MOD submission, see messages:

    EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from
    EL229 Warning Invalid address changed to MODs Name


    --- MBSE BBS v1.0.8 (Linux-armv7l)
    * Origin: Elist Maintainer at 2:25/21 (2:25/21)