TIP: Click on subject to list as thread! ANSI
echo: elist
to: ALL
from: VINCENT COEN
date: 2020-04-05 15:49:00
subject: Submission Help File

                 Quick Help for Moderators

            EList v5.0  -  The Elist program
           Copyright (c) 2019 by Vincent Coen.


     Note: The information in this guide was taken from A Moderator's
     Guide to ECHOBASE (c) Dana Bell, with changes by Ben Ritchey and
     then customized by Vincent Coen.

     This file may be designated as the file to be sent in response to
     fatal errors and requests for HELP.

     EList v5 is a database program that maintains a database of
     echomail conference information.  This particular program was
     written to meet the need to maintain and distribute echomail
     conference lists within FIDONet and with other networks.

     The FIDONet echolists published by this program include ELIST.NA
     a short, areafix uplink file format distributed monthly,
     ELIST.RPT, a longer descriptive file distributed on a monthly
     basis and ELIST.NO a short list of newly deleted echo's on a
     monthly basis.
     The last file ELIST.NO is now produced, as Ben did not 
     produce it, may be it has out lived it's usefulness how ever.
     it  will be a rolling list in that it will only contain deleted 
     Echos with any renewed one's at any later date being removed.

     Moderators may add or update entries to the list by writing to
     ELIST or via Netmail, when these options are available as
     announced in ELIST.

     Currently such Additions, Updates or Deletions to the Echomail
     database should be sent as files as ECHOtag.RUL for any rules
     file and as ECHOtag.ECO as MOD-ADD, MOD-UPD or as MOD-DEL
     requests and these subjects must also be placed after the keyword
     SUBJect.

     Once Elist can process Netmail msgs they will be converted to a
     individual ECHOtag.ECO file and processed the same way without
     any more changes to the program. It is hoped that the same will
     apply to Emails
     The program will read these files and update the EList database,
     then post a reply to the ELIST conference and via Netmail.
     (Note: the Reply-to keyword overrides the FROM address if present)
     otherwise the FROM is always used.

     Address netmail messages

     To:   ECHOLIST, (2:25/21)
     Subj: MOD-ADD or MOD-UPD or MOD-DEL

     It is hoped that Updates via Email will be also available some
     time in the future via elistmaint@dykegrove.plus.net and this
     facility will be announced in the ELIST echo area once available
     along with any update to the email address used as well as usage
     of netmail to directly deliver such messages instead of using
     files.  

     NOTE that only dropping off the files tag.ECO and tag.RUL to
     2:25/21 or 2:250/1   is supported for the moment.

     For the moment delivery of MOD-ADD, MOD-UPD and MOD-DEL messages
     MUST come as files only, along with any rules file with the
     following file names :
     For MOD-ADD, UPD and DEL as echotag.ECO
     For rules files as echotag.RUL
     Where echotag is the Echo area tag that is up to 36 characters
     in length.  Note that for MOD requests you can also add the subject
     to the end of the extension i.e.,
     MBSE.ECOMOD-ADD or MBSE.ECOMOD-UPD
     [ Note that there is NO space between MOO and UPD or ADD only a
     hyphen. ]

     Use the following keywords to set the fields of your echo list
     submission and note that only the upper case characters are significant
     e.g., only SUBJ is needed for SUBJect.
     All keywords shown starting with * are mandatory - they MUST be provided.

     For keywords FROM, MOD, COMODn and REPLY the following is the format for
     your contact address where text with {} are optional extras and as 
needed:

     Contact Address:
      A1      A2        A3       Sub field class name as used below.
     , [, ]   Note the separating commas.
     A1  name = first last names i.e., Fred Bloggs - Compulsory
                 [ note the space between name elements ]
     A2  node = zone:net/node {@domain} i.e.,
                 2:345/678  -  Compulsory
     A3  email = name@emailaddress i.e., fbloggs@gmail.com You can use '{at}' 
                 or '=at=' in place of the at sign [@] and this will
                 be the one used in ELIST reporting.
     You may omit the elements between [] but name is needed to respond to
     an update in the ELIST echo so that a problem or not can be addressed
     to the specific poster along with the netmail address for sending a
     direct message as well. If omitted you a posting could be addressed to
     SYSOP, UNKnown, 'No Idea' and other variations depending on where in the
     elist program the posting report is issued (helps in debugging).
     None of which, aids the moderator doing a search on their name to check
     the latest postings.   


  *SUBJect       MOD-UPD or MOD-ADD or MOD-DEL
                 A space can be between MOD and next word instead of
                 the '-'. When netmail and emails submissions are accepted
                 MOD-ADD, MOD-UPD or MOD-DEL must be in the message subject
                 line - hence one of the reasons for the need of this keyword.

  *FROM          Details of the sender of message where any replies regarding
                 errors or confirmation of status of submission is made to.
                   x72.

   ORIGin          x36.

   DISTribution   Any text describing x72.

   GATEway            Any text describing x72.

  *GROUP          * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)                                                                                                                                                                                                                                                   

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.