• elist status

    From Vincent Coen@2:250/1 to All on Wed Apr 8 12:37:20 2020
    Hello All!

    elist now runs at exactly 30 minutes past the hour.

    So if you send in your echotag.ECO and echotag.RUL files to 2:25/21 or 2:250/1 after that time they will get processed on the next processing interval at 30 minutes past the hour.

    Plesae ensure that the mandatory keywords are in place correctly filled in.

    If you have rules you may create keyword RULETEXT and place all rules immediately following and finish with a line of
    -!-

    Any thing after that line will be ignored so old keyword lines can be placed there if you wish or you can add as first character a #.

    tThe keyword RULETEXT must be the LAST keyword in the submission as any other will be IGNORED.

    Any line starting with a # or for that matter a blank line (outside of a RULETEXT block will be ignored.


    For DESCription and rules text the width limit is 75 characters with a maximum of 15 lines for DESCription. The rules and be any length from 5 to even 500 although the longer they are the more ignored by posters will occur !

    Ensure that all submissions include the keywords:
    FROM
    TAG
    GROUP
    LANG
    MOD

    and MOD-ADD also include:
    TITLe
    DESC

    Any others as needed for both MOD-ADD and MOD-UPD.

    If Mods have lost misplaced their submission MOD-UPD or MOD-ADD files let me know and I can program elist to send out (to their netmail address) a archive containing all echo's under there moderatorship but you will have to allow a few days for moe to program and test that option.

    Note that such ADD / UPD will not have any content for PASSword so you can create new one's.

    Another option is for elist to reandom generate these passwords, your choice but it will be for all or none and I will need an additional day or so to program and test that. Just have to find a suitable random password generator for 10 - 20 characters.


    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.73 to Vincent Coen on Thu Apr 9 02:15:06 2020
    On 2020 Apr 08 12:37:20, you wrote to All:

    For DESCription and rules text the width limit is 75 characters with a maximum of 15 lines for DESCription.

    does this mean 75 characters after the required "DESC " on each line making 80 characters per line max?

    The rules and be any length from 5 to even 500 although the longer
    they are the more ignored by posters will occur !

    here, when you say "any length" are you meaning "any number of lines"?

    and lastly, i'm confused about a few things regarding the .ECO files:
    1. your system cannot process netmails for entry updates?
    2. does the filename and extension /have/ to be UPPERCASE?
    3. do the ECO files have to be attached to a message or just the raw
    file dropped in your inbound?
    4. if we send ECO files, there /must/ be a SUBJ line in them?
    4a. with only valid values of MOD-ADD, MOD-UPD, MOD-DEL, or HELP?
    4b. when your system starts processing netmails, will that SUBJ
    line cause problems if it is in the netmail update/addition?

    i'm looking for clarification on all of the above before i dump a load of ~40 updates on you... i don't want to post them as netmails and cause you to have to manually export, edit, and submit them to your processor...

    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty,
    ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... Oil's too costly. Chop down more of the tropical forest and burn it!
    ---
    * Origin: (1:3634/12.73)
  • From Jeff Smith@1:282/1031 to mark lewis on Thu Apr 9 03:11:34 2020
    Hello mark!

    09 Apr 20 02:15, you wrote to Vincent Coen:


    and lastly, i'm confused about a few things regarding the .ECO files:
    1. your system cannot process netmails for entry updates?
    2. does the filename and extension /have/ to be UPPERCASE?
    3. do the ECO files have to be attached to a message or just the raw
    file dropped in your inbound?
    4. if we send ECO files, there /must/ be a SUBJ line in them?
    4a. with only valid values of MOD-ADD, MOD-UPD, MOD-DEL, or HELP?
    4b. when your system starts processing netmails, will that SUBJ
    line cause problems if it is in the netmail update/addition?

    I was/am curious about these questions also. I had previously used BBBS to generate netmails from text files to the Elist aka to update echos. That doesn't look to currently work as I sent a netmail update and it generated
    a number of errors. One of which was missing keywords such as:

    SUBJect MOD-UPD or MOD-ADD or MOD-DEL
    FROM zone:net/node{@domain}

    I converted a single update file (<echo tag>.ECO) using the current syntax
    and it was processed ok. I simply setup a filebox for 2:25/21 and put the update file in the filebox.

    Jeff


    --- Mystic v1.12 A46 (2020/03/29) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From Vincent Coen@2:250/1 to mark lewis on Fri Apr 10 16:11:37 2020
    Hello mark!

    Thursday April 09 2020 02:15, you wrote to me:

    For DESCription and rules text the width limit is 75 characters
    with a maximum of 15 lines for DESCription.

    does this mean 75 characters after the required "DESC " on each line
    making 80 characters per line max?

    Yes 75 after the keyword and space.

    The rules and be any length from 5 to even 500 although the
    longer they are the more ignored by posters will occur !

    here, when you say "any length" are you meaning "any number of lines"?

    Any number of lines for rules.
    DESC can have only a maximum of 15 lines as that is the space availble in the data base. This is a limit that has been in place for what 20+ years.

    and lastly, i'm confused about a few things regarding the .ECO files:
    1. your system cannot process netmails for entry updates?

    Correct I have not yet found anything that allows me to read JAM netmails and there fore gives me an option to create a file for processing.
    I will carry on looking same as for email in/out processing. For the moment all submissions must be as files that are dropped off at 2:2521 or 2:250/1.

    2. does the filename and extension /have/ to be UPPERCASE?

    No, they can be lower case as elist will search for files with extensions of .eco, .ECO, .rul and .RUL.

    3. do the ECO files have to be attached to a message or just the raw
    file dropped in your inbound?

    Just the files but if your system requires that they be attached to a netmail that is fine. Just make sure the netmail goes to 2:25/21 (or 2:250/1).


    4. if we send ECO files, there /must/ be a SUBJ line in them?
    4a. with only valid values of MOD-ADD, MOD-UPD, MOD-DEL, or HELP?
    4b. when your system starts processing netmails, will that SUBJ
    line cause problems if it is in the netmail update/addition?

    There are a few keywords that are mandatory - they MUST be supplied.

    SUBJ With MOD-ADD or MOD-UPD or MOD-DEL
    TAG Echo tag name
    FROM Your contact details in the format first last name, netmail address
    {, email address} where {} is optional.
    Example 1 is Vincent Coen, 2:250/1, vbcoen=at=gmail.com
    [ or {at} in place of =at= ]

    Example 2 is Vincent Coen, 2:250/1

    The use of the comma separating netnail and if used email IS required.

    i'm looking for clarification on all of the above before i dump a load
    of ~40 updates on you... i don't want to post them as netmails and
    cause you to have to manually export, edit, and submit them to your processor...

    No problem glad to clarify but are you saying that the help file is not being help full ?

    If so I will have to look at re writing it but most came from Dana with updates
    from Ben.

    When you are ready send one with what you now think is correct and see what happens when elist processes it and this occurs every 30 minutes past the hour.

    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.73 to Vincent Coen on Sat Apr 11 12:41:14 2020
    On 2020 Apr 10 16:11:36, you wrote to me:

    For DESCription and rules text the width limit is 75 characters
    with a maximum of 15 lines for DESCription.

    does this mean 75 characters after the required "DESC " on each line
    making 80 characters per line max?

    Yes 75 after the keyword and space.

    ok so 80 characters max per line all total... gotcha...

    The rules and be any length from 5 to even 500 although the
    longer they are the more ignored by posters will occur !

    here, when you say "any length" are you meaning "any number of lines"?

    Any number of lines for rules.

    ok...

    DESC can have only a maximum of 15 lines as that is the space
    availble in the data base. This is a limit that has been in place for
    what 20+ years.

    yeah, i was asking specifically about the rules part and also subtly offering an edit to the wording there ;)

    and lastly, i'm confused about a few things regarding the .ECO files:
    1. your system cannot process netmails for entry updates?

    Correct I have not yet found anything that allows me to read JAM netmails and there fore gives me an option to create a file for processing. I will carry on looking same as for email in/out processing. For the moment all submissions must be as files that are dropped off at 2:2521 or 2:250/1.

    can't you use something in mbse or some of its existing code? reading JAM netmails should be no different than reading JAM echomail... there's only a couple of slight differences between the two and JAM is only a storage format...

    2. does the filename and extension /have/ to be UPPERCASE?

    No, they can be lower case as elist will search for files with extensions of .eco, .ECO, .rul and .RUL.

    ok... i was asking because everything had them in uppercase and i know that some systems are case sensitive at the file level...

    3. do the ECO files have to be attached to a message or just the raw
    file dropped in your inbound?

    Just the files but if your system requires that they be attached to a netmail that is fine. Just make sure the netmail goes to 2:25/21 (or 2:250/1).

    ok... binkd outboxes will work fine for this, then... my new system works a lot
    differently than my old RA/FD/FE setup did... doing a filebox for this particular task will be the easiest method and not involve the message base code at all...

    4. if we send ECO files, there /must/ be a SUBJ line in them?
    4a. with only valid values of MOD-ADD, MOD-UPD, MOD-DEL, or HELP?
    4b. when your system starts processing netmails, will that SUBJ
    line cause problems if it is in the netmail update/addition?

    There are a few keywords that are mandatory - they MUST be supplied.

    when using ECO and RUL files... ok...

    SUBJ With MOD-ADD or MOD-UPD or MOD-DEL
    TAG Echo tag name
    FROM Your contact details in the format first last name, netmail address
    {, email address} where {} is optional.

    ok, so you want FROM instead of REPLY and i only need to add SUBJ to my existing files... gotcha...

    i'm looking for clarification on all of the above before i dump a load
    of ~40 updates on you... i don't want to post them as netmails and
    cause you to have to manually export, edit, and submit them to your
    processor...

    No problem glad to clarify but are you saying that the help file is not being help full ?

    i was saying that some of the wording was slightly confusing... mainly because... i dunno... i guess i was not seeing a clear delineation between using netmail and using ECO/RUL files...

    If so I will have to look at re writing it but most came from Dana
    with updates from Ben.

    i understand...

    When you are ready send one with what you now think is correct and see what happens when elist processes it and this occurs every 30 minutes
    past the hour.

    i'll be pumping them out "shortly... -ish" ;)

    thanks for the clarifications!


    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty,
    ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... There's a difference between criticism & abuse but most don't know it.
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Vincent Coen on Tue Apr 14 22:51:14 2020
    On 2020 Apr 11 12:41:14, I wrote to you:

    When you are ready send one with what you now think is correct and
    see what happens when elist processes it and this occurs every 30
    minutes past the hour.

    i'll be pumping them out "shortly... -ish" ;)

    so i dropped one in the filebox i have for 2:25/21 and off it went but there's been no reply and no posts in here today... did i break the bot? i have another
    39 to pelt you with ;)

    the timestamps are UTC-0400

    + 14 Apr 04:31:26 [28761] call to 2:25/21@fidonet
    14 Apr 04:31:26 [28761] trying applewood.linkpc.net [80.229.38.173]...
    14 Apr 04:31:26 [28761] connected
    + 14 Apr 04:31:26 [28761] outgoing session with applewood.linkpc.net:24554 [80.229.38.173]
    - 14 Apr 04:31:27 [28761] OPT CRAM-MD5-6f2c6a1081609b1f6d6610a6a382d718
    + 14 Apr 04:31:27 [28761] Remote requests MD mode
    - 14 Apr 04:31:27 [28761] OPT CRC
    - 14 Apr 04:31:27 [28761] SYS Air Applewood BBS
    - 14 Apr 04:31:27 [28761] ZYZ Vincent Coen
    - 14 Apr 04:31:27 [28761] LOC Hatfield, Hertfordshire, U.K.
    - 14 Apr 04:31:27 [28761] NDL CM,XA,IBN,IFC,ITN
    - 14 Apr 04:31:27 [28761] TIME Tue, 14 Apr 2020 09:31:27 +0100
    - 14 Apr 04:31:27 [28761] VER mbcico/1.0.7.13/GNU/Linux-x86_64 binkp/1.1
    - 14 Apr 04:31:27 [28761] PHN applewood.linkpc.net
    - 14 Apr 04:31:27 [28761] OPM Air Applewood BBS Linux System
    + 14 Apr 04:31:27 [28761] addr: 2:250/1@fidonet
    + 14 Apr 04:31:27 [28761] addr: 2:250/32@fidonet
    + 14 Apr 04:31:27 [28761] addr: 2:25/21@fidonet
    + 14 Apr 04:31:27 [28761] sending /sbbs/ftn/fileboxes/fidonet/2/25/21/to/arrowbridge.eco as arrowbridge.eco (695)
    - 14 Apr 04:31:27 [28761] OPT EXTCMD GZ BZ2 PLZ CRC
    + 14 Apr 04:31:27 [28761] Remote supports EXTCMD mode
    + 14 Apr 04:31:27 [28761] Remote supports GZ mode
    + 14 Apr 04:31:27 [28761] Remote supports BZ2 mode
    - 14 Apr 04:31:27 [28761] TRF 0 0
    + 14 Apr 04:31:27 [28761] Remote has 0b of mail and 0b of files for us
    + 14 Apr 04:31:28 [28761] sent: /sbbs/ftn/fileboxes/fidonet/2/25/21/to/arrowbridge.eco (695, 695.00 CPS, 2:25/21@fidonet)
    + 14 Apr 04:31:28 [28761] done (to 2:25/21@fidonet, OK, S/R: 1/0 (695/0 bytes))
    14 Apr 04:31:28 [28761] session closed, quitting...


    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty,
    ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... Today is a good day to bribe a high ranking public official.
    ---
    * Origin: (1:3634/12.73)