1. Forum
  2. Fidonet
  3. ELIST

  • elist status #2

    From Vincent Coen@2:250/1 to All on Tue Apr 21 18:21:50 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: The Elist Maintainer (2:250/1)