• Re: EL230 Errors found i

    From Dale Shipp@1:261/1466 to Vincent Coen on Fri Mar 27 02:00:02 2020
    On 03-26-20 19:13, Vincent Coen <=-
    spoke to Dale Shipp about EL230 Errors found in MO <=-


    EL230 Errors found in MOD submission, see messages:

    EL219 Error Unknown keyword found: TOT
    EL202 Error TAGname not specified.

    I read the responses elsewhere today, and did do some changes based on
    them. I took out TOT (not sure what it might have once meant). But I
    do not understand why TAG is not specified. The line
    TAG COOKING
    was the second line on most of the submissions.
    The last submission was sent at 17:59:25 , EDT and followed what you
    sent me in email (I think). Did that one take?

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)


    ... Shipwrecked on Hesperus in Columbia, Maryland. 02:05:47, 27 Mar 2020
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From Vincent Coen@2:250/1 to Dale Shipp on Fri Mar 27 23:38:23 2020
    Hello Dale!

    Friday March 27 2020 02:00, you wrote to me:

    On 03-26-20 19:13, Vincent Coen <=-
    spoke to Dale Shipp about EL230 Errors found in MO <=-


    EL230 Errors found in MOD submission, see messages:

    EL219 Error Unknown keyword found: TOT
    EL202 Error TAGname not specified.

    I read the responses elsewhere today, and did do some changes based on
    them. I took out TOT (not sure what it might have once meant). But I
    do not understand why TAG is not specified. The line
    TAG COOKING
    was the second line on most of the submissions.
    The last submission was sent at 17:59:25 , EDT and followed what you
    sent me in email (I think). Did that one take?

    You submissions arrival may have clashed or not with my edit of the .ECO file, but regardless it went through woth no problems . I did post a copy of it
    sans
    the password here I seem to recall.

    The first problem with the original file was the keyword and sub was incorrect you had
    MOD UPD

    That got confused with a MOD keyword so it all started to go to pot from there :)

    That line should have been :
    SUBJ MOD-UPD

    and as you the invalid work TOT just got ignored (with a error message) and processing continued until all keywords was read.

    This is how elist now works and after reading the last line in the .ECO file it
    then checks for errors in addition it may have picked up so far.

    Then it reject it with another message.

    This way if you submit a MOD-UPD or MOD-ADD with multiple problems hopefully they all get reported on other than the example you had with the line MOD UPD which elist tried to send a msg to UPD then realised it was a bad address.

    Joking, it found that out earlier.

    Hope the above helps you,


    Vincent

    --- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From mark lewis@1:3634/12 to Dale Shipp on Sat Mar 28 13:14:06 2020
    Re: Re: EL230 Errors found i
    By: Dale Shipp to Vincent Coen on Fri Mar 27 2020 02:00:02


    I read the responses elsewhere today, and did do some changes based on them. I took out TOT (not sure what it might have once meant). But I

    from ECHOMOD v3.11...

    ----->8 snip 8<-----

    The keywords are
    %TAG <areatag>
    %TITL <brief area description>
    %DESC <description of the echo>
    %MOD <moderator name>, <moderator node>
    %COMOD <co-moderator name>, <co-moderator node>
    %TOT <number of nodes carrying this conference>
    %VOL <number of messages>/Month
    %REST <Flag restrictions>
    %NOTE <freeform restrictions>
    %ORIG <origination of the distribution>
    %DIST <distribution>
    %GATE <gateways>
    %GROUP <group echo belongs with>
    %RULE <rule file>
    %CREA <creation date>
    %UPDA <update date>
    %ADDR <Moderator's Address>
    %ADDR2 <CoModerator's Address>
    %MSGR <Messenger>
    %MSGA <Messenger's Address>
    %% literal %

    ----->8 snip 8<-----

    i also note that there should be no problem with various spaces between the tags and their contents...


    )\/(ark
    --- SBBSecho 3.10-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Dale Shipp@1:261/1466 to Mark Lewis on Sun Mar 29 02:50:00 2020
    On 03-28-20 13:14, Mark Lewis <=-
    spoke to Dale Shipp about Re: EL230 Errors found i <=-


    Re: Re: EL230 Errors found i
    By: Dale Shipp to Vincent Coen on Fri Mar 27 2020 02:00:02


    I read the responses elsewhere today, and did do some changes based on them. I took out TOT (not sure what it might have once meant). But I

    from ECHOMOD v3.11...

    ----->8 snip 8<-----

    The keywords are
    %TAG <areatag>
    %TITL <brief area description>
    %DESC <description of the echo>
    %MOD <moderator name>, <moderator node>
    %COMOD <co-moderator name>, <co-moderator node>
    %TOT <number of nodes carrying this conference>
    %VOL <number of messages>/Month
    %REST <Flag restrictions>
    %NOTE <freeform restrictions>
    %ORIG <origination of the distribution>
    %DIST <distribution>
    %GATE <gateways>
    %GROUP <group echo belongs with>
    %RULE <rule file>
    %CREA <creation date>
    %UPDA <update date>
    %ADDR <Moderator's Address>
    %ADDR2 <CoModerator's Address>
    %MSGR <Messenger>
    %MSGA <Messenger's Address>
    %% literal %

    ----->8 snip 8<-----

    i also note that there should be no problem with various
    spaces between the tags and their contents...

    I suspect what you are posting is from a previous help file. I made the
    edits which Vincent suggested (no extra spaces, COMOD1, delet TOT) and
    the listing was accepted.
    I had sent exactly the same thing that the moderator had used for
    previous program -- but things changed.

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)


    ... Shipwrecked on Hesperus in Columbia, Maryland. 01:52:56, 29 Mar 2020
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From mark lewis@1:3634/12 to Dale Shipp on Sun Mar 29 08:59:52 2020
    Re: Re: EL230 Errors found i
    By: Dale Shipp to Mark Lewis on Sun Mar 29 2020 01:50:00


    from ECHOMOD v3.11...
    [...]

    I suspect what you are posting is from a previous help file.

    yes, as noted... you had said you didn't know what it was used for so i showed you ;)

    I made the edits which Vincent suggested (no extra spaces, COMOD1,
    delet TOT) and the listing was accepted.

    i'm sure ;)

    I had sent exactly the same thing that the moderator had used for
    previous program -- but things changed.

    i planned on sending exactly what i've been using, too... i do not relish the idea of having to edit all of them from their existing format which has been in use for ~20+ years through several echolist programs and echolist keepers... i'm not sure what i'm going to do now... i have also been waiting to see if the other project comes online soon and how they handle the existing update templates... afterall, it is the moderators that choose which, if any, echolist they support with their entries...


    )\/(ark
    --- SBBSecho 3.10-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)