Subj : Submission formats of .ECO files when taking over a echo
To   : August Abolins
From : Vincent Coen
Date : Mon May 04 2020 19:26:16

Hello August!

Monday May 04 2020 20:04, you wrote to me:

 > On 04/05/2020 12:22 p.m., Vincent Coen : All wrote:

 >> Some appear to be having a problem of working out what MOD-UPD files
 >> to send when taking over from one of the moderators who have left
 >> fido or died.
 >>
 >> Here I will show you an example based on one such echo that Bill was
 >> the moderator and this is spread over 3 ECO files but note that a
 >> password must be included of your choicing :
 > [snip]

 > So, basically, MOD and FROM should always match in each .ECO file.

 > [eg.]
 >> NHL1.ECO
 >> MOD Bill McGarrity, 1:266/404, bill.mcgarrity{at}tequilamockingbir
 >> FROM Bill McGarrity, 1:266/404

 > [eg.]
 >> NHL2.ECO
 >> MOD Dan Clough, 1:123/115
 >> FROM Dan Clough, 1:123/115, gamgees{at}gmail.com

 > [eg.]
 >> NHL3.ECO
 >> MOD Dan Clough, 1:123/115
 >> FROM Dan Clough, 1:123/115, gamgees{at}gmail.com

 >> Hope the above helps,

 > I had a feeling that that's what was out of sync in the .ECO files.


The FROM is important on the 1st one as a COMOD1 entry is supplied so it is
checked that a valid Mod/CoMod is in the FROM.

The 2nd the MOD is changed to the new MOD that also matches the COMOD1 entry
and along with any other changes such as ORIG if needed and the 3rd  one is
removing the temporary COMOD1 entry.

It is important that a password is supplied for all three otherwise an en 
error
will be reported and like wise if the 1st one is not the original Mod as on
record it will get rejected if the FROM entry is different.

All security checks have been covered here.



Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
 * Origin: The Elist Maintainer (2:250/1)

.