home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hot Shareware 32
/
hot34.iso
/
ficheros
/
VUBBS
/
ELIST804.ZIP
/
ELFAQ804.TXT
< prev
next >
Wrap
Text File
|
1998-04-01
|
20KB
|
441 lines
ECHOLIST
The EchoMail Conference List
FREQUENTLY ASKED QUESTIONS
01 Apr 98 ELFAQ804.TXT
Change - addition of FAQ # 19
*****************************
The Echolist Coordinator at 1:153/752 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.
Changes since the last issue are highlighted in the left margin with
the pipe symbol '|'.
Contents:
1. New Elist Entry
2. Who to Contact
3. Checking information
4. Backbone Distribution
5. Reply Netmail
6. Correct Address
7. Lost Password <=== The most frequent question! :)
8. Inactive Co-Moderator
9. Missing Moderator
10. Unlisted Moderator
11. Expired Echo Tags
12. Echo Highjacking
13. Elist Numbering System
14. Elist Software
15. Elist & Backbone expiry periods
16. Elist publication/purging times
17. Duplicate Elist entries
18. Node number for sending updates
| 19. Z1 vs Z2 Elist updating
1. 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.ZIP either by local file request
from your Echomail Coordinator or Hub, by freq from
1:153/752 using the magic name ELMOD, or from the Internet
Web page http://www.portal.ca/~awalker/elist.htm. Follow
the instructions contained in this file carefully, and your
Elist entry will be confirmed by netmail from 1:153/752.
2. Who to Contact
=================
I have some questions regarding Elisting. Whom should I contact?
Answer: The Elist Coordinator is only responsible for maintaining
the software and the data files, and ensuring their
distribution. For reasons of time, individual inquiries can
not usually be answered. Here are the best options:
Elist update format: read ELMOD.
Other Elist questions: read ELFAQ (this file).
Latest Elist files: freq ELIST, ELRUL or ELMOD from 1:153/752.
Getting files locally: Net Echomail Coordinator.
Moderator disputes: Echomail Ombudsman.
Echo highjackings: Echomail Ombudsman.
Forgot Elist password: Password Backup (Bruce Bodger).
Co-moderator has password: Password Backup (Bruce Bodger).
Echo content objections: Head of distribution system.
Understanding help files: Net Echomail Coordinator.
Other questions: Moderators in MOD_COUNCIL or ECHOLIST echo.
No luck after all that: Region Echomail Coordinator.
3. Checking information
=======================
I'd like some information on my Elist entry - would you check it?
Answer: Because the Elist contains over 1500 echoes, it is not
possible for the Echolist Coordinator to provide information
or guidance to each Moderator separately. The Elist archive
(ELISTnnn.ZIP) contains this FAQ file and the ELMODnnn.TXT
file which between them provide answers to most of the
commonly asked questions.
To check the status of an echo's listing, you have the
following options:
1. The ECHO QUERY and OPTION HOLD functions detailed in ELMOD.
2. The postings of successful updates in the ECHOLIST echo.
3. The weekly posting of the ELTAG summary in the ECHOLIST echo.
4. File requesting the magic name ELTAG from 1:153/752.
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. Please avoid
netmailing the Echolist Coordinator until you have checked
all the above sources of information.
4. 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.
5. 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 60 seconds later, but if the
Echolist system is 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. In such cases none of the information in the
update is used to update the database. If in doubt about
formatting the message consult the current version of ELMOD.
6. 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:153/752
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:153/752, this being one of the more
common addressing errors. These messages are ignored by the
Robot and get deleted.
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.
With Internet email updates, the email is scanned for the
presence of Elist date and moved into the netmail area for
normal processing. Afterwards, the Elist reply message is
scanned for an Internet address and moved into the email
area for SMTP forwarding.
7. Lost Password
================
I've lost my Elist password. Can you send it to me?
Answer: Sorry but no. The Echolist software functions largely
unattended, so such requests are ignored by the Robot, and
the Echolist Coordinator does not answer such requests
personally.
A Moderator in this position should explain the situation to
the Elist Password Backup (Bruce Bodger), and will need to
convince him that there is good reason to provide him or her
with the echo's password.
If he approves of the password release, he may request that
the Echolist Coordinator release the password to him for
forwarding to you. This ensures that the password only goes
to the legitimate moderator. The password transfer to the
Elist Password Backup is conducted by a secure routed mail
link.
8. Inactive Co-Moderator
========================
My co-Moderator has the Elist password but has not updated the entry
which is now about to expire. He is still in the nodelist or active
in the echo, so he has not gone missing. I do not have the password.
Can you provide it to me?
Answer: Elist passwords are not divulged. 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 Robot will not compromise the security of the
password.
This is an issue which should be resolved with the other
Moderator. If this proves impossible, the Zone 1 Echomail
Ombudsman, has agreed to mediate any such disputes to
attempt to help the moderators resolve their differences.
9. Missing Moderator
====================
An echo I am interested in appears to have no moderator, but is still
operating. Its Elist entry is about to expire. What can I do to
revive it?
Answer: Generally, moderator selection 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.
The Elist Password Backup (Bruce Bodger) may provide an
echo's password to a replacement moderator AFTER the echo has
become unlisted if, in his opinion, the original moderator
has abandoned the echo.
10. Unlisted Moderator
====================
An echo's listed moderator is not reachable at the address specified
in the Elist entry. He is either not in the Fidonet nodelist, or can
not be reached from Fidonet, or his Internet email address is not
accessible. What should be done?
Answer: The Elist, for reasons of time available, does not verify
addresses to see if they are usable. If they are not, the
Moderator will not receive any update messages. As long as
the echo poses no problem which would require contact by the
Echolist Coordinator, and the entry remains current, the
echo may remain listed.
If a problem results in the Echolist Coordinator being
unable to reach the Moderator after a reasonable effort, the
echo's listing will be dropped immediately with no grace
period, and the password will be purged from the database.
At that time anyone may list the echo under their own name.
As a result, it is *strongly* recommended that Moderators
ensure that their Elisted netmail/email address is current
and correct! :)
11. 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: It depends on how long ago the echo listing expired.
When an Elist entry expires after 6 months without being
updated, the listing for it is removed from the Elist
distribution file. The echo's record is automatically
purged from the database 30 days later, so prior to that
time only the holder of the password may relist the echo.
After that time, the echo tag can be listed by anyone who
wishes to do so, and there is no recourse for the previous
user of the tag, nor will any correspondence be entered into
on the subject.
NOTE:
Warning, expiry and purging are performed when the Elist is
published on the first of each month, so for calculation
purposes the software assumes that an echo was updated on
the first of the month following the actual update.
12. 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.
Data for expired echo listings is not purged from the
database until 30 days after the listing has been removed
from the monthly distribution file. After that the tag may
be listed by anyone wishing to do so. Such a listing is not
considered a highjacking, and the Echolist Coordinator will
not answer correspondence in these cases.
13. 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.ZIP contains ELIST507.TXT,
ELMOD507.TXT and ELIST507.FAQ.
14. 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 deletion, and Zone 2 Elist
conversion and merge functions. It is not available for
distribution.
15. Elist & Backbone expiry periods
===================================
I am confused about the various time periods for Elist updates and
expiry, and their relationship to North American Backbone warning and
expiry periods.
Answer: Although the Elist and the North American Backbone are
independent (see FAQ #4 above), here is the combined schedule
of Elist and Backbone expiry dates which moderators whose
echoes are carried on this Backbone should be aware of:
1. Elist update submitted by moderator.
2. 5 months after update, Elist warning of expiry.
3. 6 months after update, Elist expiry and deletion.
4. 6 months after update, Backbone moves echo from BACKBONE.NA
to BACKBONE.NO.
5. 7 months after update, Elist password purged.
6. 9 months after update, Backbone deletes echo from BACKBONE.NO
and stops distribution.
NOTE:
1. If an echo is missing its moderator, the above schedule
allows a new moderator to relist the echo after password
purging but still 2 months before the Backbone stops
distributing the echo (ie between steps 5 and 6 above).
This has been arranged to prevent any need to divulge
passwords to other than the listed moderator.
2. Warning, expiry and purging are performed when the Elist is
published on the first of each month, so for calculation
purposes the software assumes that an echo was updated on
the first of the month following the actual update.
Example: an echo last updated on the 14th March will
receive its 5-month warning, not on 14th August, but on 01
September (5 COMPLETE months later), and all further time
periods will be the first of the succeeding months.
16. Elist publication/purging times
===================================
I have tried to relist an expired echo on the first of the month,
when I thought the password had been purged. My update was rejected.
Why?
Answer: The preparation of the monthly files is done by a
manually-supervised 220-line batch file, and it gets done
anywhere from about 7 pm on the 31st to 3 pm on the 1st,
depending on when the Echolist Coordinator is free.
Occasionally commitments delay this for a couple of days.
This allows help files to be updated, which can only be done
manually.
If the update is rejected, it simply means that the new
Elist has not "gone to press" yet. Try again later that
day, or a day or two later.
17. Duplicate Elist entries
===========================
I have noticed that some entries in the Elist have duplicate tags.
Why is that, and how do I determine which one to use?
Answer: The Echolist does not permit duplicate tags for its own
updated entries. At publication time, however, the Fidonet
Zone 2 Elist is merged with the database, and some duplicate
tag names appear as a result. An enhancement is planned for
the merging routine to prune out these duplicates before
publication.
All entries from the Zone 2 Elist contain the line:
Flags: <From Z2 Elist>
As a result, normal updated entries can be distinguished
from merged Zone 2 duplicate tags, until the enhancement is
put in place.
18. Node number for sending updates
===================================
The Echolist Coordinator uses node numbers 1:153/751, 1:153/752 and
and 1:1/201. Does it matter which I send my updates to?
Answer: No - 1:1/201 is the same system as 1:153/751, and 751 and
752 are linked by a lan, with 752 running the Echolist
software. Updates can be addressed to any of these node
numbers and will be processed in the normal way equally
quickly.
| 19. Z1 vs Z2 Elist updating
| ===================================
|
| Can I update the entries in the Zone 1 Echolist when I update my
| Zone 2 Echolist entry, and will I get an update response from the Zone 1
| Echolist when I make changes to the Z2 Echolist?
|
| Answer: No - the two Echolist's are independent, and their Robots
| respond only to update messages sent directly to that Robot,
| not to the contents of the other Echolist. Each Echolist,
| however, merges the contents of the other at publication
| time each month, so if an echo appears in one Echolist, it
| will automatically appear in the other on the next
| publication date. As a result, it is only necessary to list
| an echo in one Echolist.
---ooo000ooo---
