
                                ECHOLIST
                      The EchoMail Conference List
                       FREQUENTLY ASKED QUESTIONS

01 Sep 95                                                  ELIST509.FAQ

   The Echolist Coordinator at 1:1/201 receives quite a bit of netmail
   asking a variety of questions on the operation of the Echolist, or
   Elist, and it seems reasonable to try to answer these in a publicly
   available document, hence this FAQ file.

   Contents:

        New Elist Entry
        Who to Contact
        Checking information
        Backbone Distribution
        Reply Netmail
        Correct Address
        Lost Password
        Inactive Co-Moderator
        Missing Moderator
        Expired Echo Tags
        Echo Highjacking
        Elist Numbering System
        Elist Software


   New Elist Entry
   ===============

   I'm new at this and I'm not sure how to get my echo on the Elist.

   Answer:  Obtain the file ELMODnnn.LZH either by local file request
            from your Echomail Coordinator or Hub, or by freq from
            1:1/201 using the magic name ELMOD.  Follow the instructions
            contained in this file carefully, and your Elist entry will
            be confirmed by netmail from 1:1/201.


   Who to Contact
   ==============

   I have some questions regarding Elisting.  Whom should I contact?

   Answer:  As Elist Coordinator I am responsible for maintaining the
            software and the data files, and ensuring their
            distribution.  For reasons of time I can answer individual
            inquiries only where the answer is not available elsewhere.
            Here are the best options:

   Elist update format:       read ELMOD.
   Getting files locally:     write to Net Echomail Coordinator.
   Latest Elist files:        freq ELIST, ELRUL or ELMOD from 1:1/201.
   Other Elist questions:     read ELFAQ (this file).
   Moderator disputes:        write to Jason Steck, Echomail Ombudsman.
   Echo highjackings:         write to Jason Steck, Echomail Ombudsman.
   Forgot Elist password:     write to Marge Robbins, REC 14.
   Echo content objections:   write to head of distribution system.
   Understanding help files:  write to Net Echomail Coordinator.
   No luck after all that:    write to Region Echomail Coordinator.
   Still no luck:             write to Adrian Walker, Echolist Coordinator.


   Checking information
   ====================

   I'd like some information on my Elist entry - would you check it?

   Answer:  Because the Elist contains over 1400 echoes, it is not
            possible for the Echolist Coordinator to provide information
            or guidance to each Moderator separately.  The Elist archive
            (ELISTnnn.LZH) contains this FAQ file and the ELMODnnn.TXT
            file which between them provide answers to most of the
            commonly asked questions.

            The ECHO QUERY function is available as an automated method
            of obtaining the current listing for any echo, and its
            format is described in ELMOD.

            If your question is still not answered after reading these,
            your next approach, in order, is to ask your sysop, your
            Net's NEC, and finally your Region's REC.  Only if you can
            not get the answer from these people should you write to the
            Elist coordinator.  Once I re-program the day to have 48
            hours I will again be able to handle such inquiries.  ;)


   Backbone Distribution
   =====================

   If I get my echo listed in the Elist, does that mean that it is 'on
   the Backbone'?

   Answer:  No.  The Elist is only a reference, providing information to
            anyone interested in reading it.  In fact, it is used by the
            operators of several different distribution systems.  If you
            wish your echo distributed by a group of Hubs, you should
            obtain any instructions they may have for getting added to
            their distribution system.  This may include having an Elist
            entry, but that and any other steps are up to them.


   Reply Netmail
   =============

   I've dropped off an Elist update.  How will I know whether it was
   received?

   Answer:  The Elist software will generate a routed netmail
            acknowledgement of any message addressed to it.  This
            includes MOD UPD messages, MOD RUL messages, and ECHO QUERY
            messages.

            Alternatively, if you have specified OPTION HOLD the reply
            will be waiting for you to pick up about 1 hour later (In
            fact it is usually ready 75 seconds later, but if I'm
            processing a major mail dump your update may be processed at
            the end of that cycle).

            By using the ECHO QUERY function explained in the ELMOD
            file, you can obtain a copy of the latest database entry for
            a particular echo.  Please note that Query messages are
            processed using the data on file PRIOR TO the arrival of the
            query message - any updates which arrived at the same time
            will not be reflected in the query.

            A successful update is also acknowledged by an automated
            daily posting in the ECHOLIST echo.

            Any messages incorrectly formatted, but correctly addressed,
            will receive a written acknowledgement, and missing data
            will be noted. If in doubt about formatting the message
            consult the current version of ELMOD.


   Correct Address
   ===============

   How does the Elist software know when to process a netmail update?

   Answer:  The Elist software is run every time inbound mail is
            received.  It searches the netmail directory at 1:1/201
            looking for any messages addressed to 'ECHOLIST' at that
            address.  All other messages are ignored by it.

            In particular it is important to avoid addressing the update
            to 'Adrian Walker' at 1:1/201, this being one of the more
            common addressing errors.  I try to readdress these messages
            to permit the software to read them, but I can only do that
            when I get time.

            With non passworded sessions the packets are inspected
            automatically to make sure that they are netmail and if so
            they are moved into the secure inbound area for processing.


   Lost Password
   =============

   I've lost my Elist password.  Can you send it to me?

   Answer:  Sorry but no, Elist passwords are not divulged, and since
            security would require that the Echolist Coordinator send
            the reply message by direct mail, this entails expense.
            Also such a message unfortunately can not be placed on hold
            since an unscrupulous person could preconfigure his system
            to represent a particular node when polling.

            A Moderator in this position should explain the situation to
            Marge Robbins, REC for Region 14, who has agreed to
            coordinate the verification of a moderator prior to
            the release of a password.

            If you are able to find a senior Coordinator or Echomail
            Coordinator who personally knows you as moderator and who is
            willing to vouch for this request coming from the same
            person, then Marge will request that I release the password
            to her for forwarding to you.  This ensures that the
            password only goes to the legitimate moderator.  The
            password transfer to Marge is conducted by a secure routed
            mail link.


   Inactive Co-Moderator
   ====================

   My co-Moderator has the Elist password but has not updated the entry
   which is now about to expire.  I do not have the password.  Can you
   provide it to me?

   Answer:  Sorry but no, Elist passwords are not divulged.  (is there
            an echo here?)  If the Moderator of an echo has chosen not
            to give the co-Moderator the Elist password, it is assumed
            there is a reason for this, and the Echolist Coordinator
            will not compromise the security of the password.

            This is an issue which should be resolved with the other
            Moderator.  If this proves impossible, Jason Steck, Zone 1
            Echomail Ombudsman, has agreed to mediate any such disputes
            to attempt to help the moderators resolve their differences.


   Missing Moderator
   =================

   An echo I am interested in appears to have no moderator, but is still
   operating.  What can I do to revive it?

   Answer:  This is an issue for the participants of the echo to decide
            on.  Sometimes they accept a willing volunteer, and other
            times they hold an election.  Once the decision is made, the
            new moderator should update the Elist entry.

            If the new moderator does not have the Elist password,
            evidence should be submitted to Marge Robbins, REC for
            Region 14, who has agreed to coordinate the verification of
            such an individual, showing that the previous moderator is
            no longer listed in a commonly-available nodelist, and that
            the participants have chosen a replacement Moderator.

            If an update is accepted in this circumstance, the new
            moderator still takes full responsibility for resolving with
            echo participants any disputes over moderatorship.


   Expired Echo Tags
   =================

   I noticed that an echo I am interested in has been deleted from the
   Elist.  Can I take over the tag and send in an update myself?

   Answer:  No.  When an Elist entry expires after 6 months without
            being updated, the listing for it is removed from the Elist
            file.  Any password associated with it, however, is retained
            in the password database for some time thereafter.

            That is done to prevent someone from taking over an echo in
            the first few months after an Elist entry lapses, without
            proper agreement from the previous moderator or
            participants.

            The expiry of an Elist entry does not necessarily mean that
            the echo in question has disappeared, and experience has
            shown that an unscrupulous person wishing to highjack an
            echo tends to misuse the Elist confirmation as "proof" that
            he/she is now the moderator of such echoes.


   Echo Highjacking
   ================

   My echo was dropped from the Elist several months ago because I had
   not updated the listing and now someone else has Elisted it and
   claims to be the Moderator.  Can you give me back my echo?

   Answer:  The Elist does not confer Moderatorship on anyone.  It only
            records information submitted by a Moderator, and to protect
            that information from alteration by others a password
            feature is available and its use encouraged.  If a Moderator
            chooses not to use the password feature, others may get
            access to the listing.

            This is an issue which should be resolved with the other
            Moderator, since the Echolist Coordinator does not get
            involved in disputes over Moderatorship of an echo.

            If this proves impossible, Jason Steck, Zone 1 Echomail
            Ombudsman, has agreed to mediate any such disputes to
            attempt to help the moderators resolve their differences.


   Elist Numbering System
   ======================

   What does the Elist 'nnn' numbering system mean?

   Answer:  The Elist files are numbered by taking the last digit of the
            year (example:  5 for 1995) followed by the month number
            (example:  07 for July).  Thus the files issued in July 1995
            are numbered 507 - ELIST507.LZH contains ELIST507.TXT,
            ELMOD507.TXT and ELIST507.FAQ.


   Elist Software
   ==============

   What software is used to process the Elist and may I have a copy?

   Answer:  The version 3 software is written in Borland Turbo Pascal
            version 7 and is custom written for the Elist tasks.  It
            runs on a DOS platform and on a single pass reads the
            inbound messages, prepares a response, extracts data from
            update messages, and performs lookup and password checking
            functions.  Separate related programs perform the sorting,
            updating, expiry warning and deletion functions.  It is not
            available for distribution.


   Questions which can not be answered by the appropriate NEC or REC may
   be addressed to the Echolist Coordinator (Adrian Walker) at 1:1/201
   by netmail.

                              ---ooo000ooo---
