Hello All!


I am now happy, well as far as I can be that elist v5.0.117 is working to a
reasonable level :)

It is now being re-issued as elist v5.1.000 for a live run very shortly.

I will be running it against echo ELIST which will show auto updates creating
the database (file).
It will show the original dates of the last update as from ELIST.RPT dated May
2019, and this means that moderators will need to update their entries.

It could be after all this time that there are moderator change that have
occurred.

If you have a problem doing an update please advise but the simple way is to 
do
a UPD submission with the new mod as COMOD1 before passing the submission 
files
to them.
The system will allow any moderator including a co-moderator to do a UPD
submission.
This is to allow any of the recorded moderators to submit an update if the
moderator has left Fido etc.

At the moment the system is set to issue expiry Warnings after six months and
is pre programmed to do so on every WARN run which is set to be every month 
but
this means that a echo will not get deleted until month 11 after the date of
the last update.

Strikes me as some what too long, so is it reasonable to do it weekly which
will give 4+ weeks after the first warning is is that short ?

The reporting has been changed to allow for the generation of the ELIST.NO 
file
that shows deleted echo's and will also be up to date, i.e., any newly added
Echo's will be removed from the master NO file.

All submissions (as echo tag name.ECO and echotagname.RUL files) must, at 
least
for the moment be sent only as files and dropped off direct, to my netmail
addresses of 2:250/1 or 2:25/21.  For example the files for echo MBSE are
MBSE.ECO  and MBSE.RUL

Of course the rules can be inserted in the submission file between keyword
RULETEXT

and
-!-  or
-+-

and must be the last block in the submission files as anything after, will be
ignored.

I intend to revisit the elisthlp file that will be included in with the ELST
monthly archive along (as it has in the past) with ELIST.RPT, ELIST.NA and the
new ELIST.NO if there is any content as well as a archve containing the
directory (rules) containing all current rules files (as updated by moderator
submissions as upper case files names).

The use of upper case files names is to support any sysop running a BBS that
requires it.

There might also be additional text files such as a README to prvide 
additional
help over than the normal elisthlp.txt file at least until I can refresh it in
a easy to read format. Any questions asked regarding usage will also mean a
re-look at the supplied help file to fix the need to ask such questions where
ever possible.


Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707