Hello All!

When doing an UPDATE run I have found an issue that if a error in the submission is found, the
program issues a error message and does not continue with processing the rest of the keywords.in
that MOD-ADD or UPD submission. This is what happens to the older version as far as I can see.

This can cause a problem if the FROM, TAG keywords has not yet been read, so that the warning is
not sent to the right address or not addressed to anyone in ELIST or even the subject of the
posting is missing the Echo name (Tag) etc, etc.

This at least for the FROM keyword has been exasperated by the extra checks now made for a
Contact Address that the first two elements must be present [first last name, netmail address]
and the last (the email address) is optional.
This was not done in the previous version/s as far as I can tell.

If the email address is present then a report will be sent to it as well as via netmail abd the
ELIST echo.

This will happen after the email code has been set up but I am ignoring this for the moment as
the rest of the elist system takes priority and the email posting is just a hook into another
process.

Personally I do not read netmail's or Echo areas on a daily basis, more like weekly at best
although does depend on what else is happening in my day to day life but I always read my emails
even if to keep the time spent under control as happens when I go on holiday say for two weeks
and I can get 200+ per day so normally reading them multi times per day help keep it under
control even if many are deleted just looking at the subject and from lines :).

So the program is being redesigned / reprogrammed to support that the full ADD / UPD submission
is read and reported on if any errors etc are found, This way there could be more than one
problem being reported such as missing mandatory keywords, bad contact addresses etc

If any thing it will cut down on the number of submission attempts made by some moderators when
such reports are made.

At the moment if any errors are found, the error message report is followed by a copy of the
current elist help file and this in any event is part of the ELIST archive sent each month so I
am wondering if it is really necessary to sent it ?

Currently it is sent inside or separately to the error msg both to ELIST and to the mods netmail
address and strikes me as extreme over kill and just clutters up the ELIST echo.

So in this instance, the idea is to do away with posting it and just adjust the comment in any
error msg that currently says:

-!-
Subj: MOD ADD or UPD errors - Help file

See separate file or msg
--

Changing it simply to :

See Help file in the ELIST archive [ or even just not bother with it. ]

Opinions ?


and yes testing is going a pace but found some sillies which for some, the above will help to
fix.

Needless to say the bug list is getting smaller, even sigle digits.

Oh, the warning and error messages have a preceding code number such as EL201 to most of them and
I will use these to provide a small help element in the manual to describe the fix for the
problem being reported where it is needed. At the moment it is helping to find where in the code
it is being used that help bug finding and fixing. So the prefixs may well be mored out once the
program is in production ( live ).

Vince

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:2/21)