EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson, 1:1
EL214 MOD-ADD to existing area - Rejected.


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

Hello Vincent,

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson,
1:1
EL214 MOD-ADD to existing area - Rejected.

Hmm. Expect a couple more of these.

Should I be using MOD-ADD or MOD-UPD?

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

Sunday April 26 2020 15:51, you wrote to me:

Hello Vincent,

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from
Alan Ianson,
1:1
EL214 MOD-ADD to existing area - Rejected.

Hmm. Expect a couple more of these.

Should I be using MOD-ADD or MOD-UPD?

MOD-UPD and use the original MOD and FROM when adding a COMOD1 as yourself with
a password.


On the next update now change MOD, FROM to you and on the next do a
COMOD1 DELETE but give the submission file name a 2, 3 etc at the end ie. COFFEE.ECO
COFFEE2.ECO
COFFEE3.ECO

etc.

Don't forget to double check the content of each before submitting them.

This way they will be processed in alphabetic order.

To remove yourself as a comod as you are now the mod.

Always ensure that the contact details are complete, i.e., the mandatory elements : first lastnames, netmail address EG:
Vincent Coen, 2:250/1

You can add leading comma and your email address so above would be:

Vincent Coen, 2:250/1, vbcoen=at=gmail.com (or {at} instead of =at= )

Vincent

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

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson, 1:1


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson, 1:1


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Roger Nelson,


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

Hello Alan!

Monday April 27 2020 23:30, I wrote to you:


I have changed them a bit with names ending 1, 2 & 3.
where 1 has you as COMOD1 and the mod and from is Roger
where 2 has you as mod and from
where 3 has comod1 delete


Lets see if that works.

Vincent

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

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Roger Nelson,


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson, 1:1


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson, 1:1


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

Hello Vincent!

** On 28.04.20 - 01:00, Vincent Coen wrote to Alan Ianson:

I have changed them a bit with names ending 1, 2 & 3.
where 1 has you as COMOD1 and the mod and from is Roger
where 2 has you as mod and from
where 3 has comod1 delete

Lets see if that works.
Vincent

Heheheh..

[3]
EL230 Errors found in MOD submission, see messages:
EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson,1:1

[2]
EL230 Errors found in MOD submission, see messages:
EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson,1:1

[1]
EL230 Errors found in MOD submission, see messages:
EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson,1:1


Ahhh... the joys of getting robots to cooperate.


../|ug

--- OpenXP 5.0.43
* Origin: /|ug's Point, Ont. CANADA (2:221/1.58)

Hello August!

Monday April 27 2020 21:29, you wrote to me:

Hello Vincent!

** On 28.04.20 - 01:00, Vincent Coen wrote to Alan Ianson:

I have changed them a bit with names ending 1, 2 & 3.
where 1 has you as COMOD1 and the mod and from is Roger
where 2 has you as mod and from
where 3 has comod1 delete

Lets see if that works.
Vincent

Heheheh..

[3]
EL230 Errors found in MOD submission, see messages:
EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson,1:1

[2]
EL230 Errors found in MOD submission, see messages:
EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson,1:1

[1]
EL230 Errors found in MOD submission, see messages:
EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Alan Ianson,1:1

Ahhh... the joys of getting robots to cooperate.

Going to take a very close look at the first submission and the program.


Vincent

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

EL230 Errors found in MOD submission, see messages:

EL225 Invalid (Co)MODerator given in FROM, Elist MOD was from Roger Nelson,


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

Hello Vincent!

** On Monday 27.04.20 - 13:09, Vincent Coen wrote to Alan Ianson:

On the next update now change MOD, FROM to you and on the next do a
COMOD1 DELETE but give the submission file name a 2, 3 etc at the end

ie. COFFEE.ECO
COFFEE2.ECO
COFFEE3.ECO

Would your parser break if the original echoname had a number after it?

eg. OS2

.: OS22.ECO, OS23.ECO, etc..


Just wondering.


../|ug

--- OpenXP 5.0.43
* Origin: (2:221/1.58)

Hello August!

Wednesday May 13 2020 10:10, you wrote to me:

Hello Vincent!

** On Monday 27.04.20 - 13:09, Vincent Coen wrote to Alan Ianson:

On the next update now change MOD, FROM to you and on the next do
a COMOD1 DELETE but give the submission file name a 2, 3 etc at
the end

ie. COFFEE.ECO
COFFEE2.ECO
COFFEE3.ECO

Would your parser break if the original echoname had a number after
it?

eg. OS2

.: OS22.ECO, OS23.ECO, etc..

Nope that is totally valid.


Vincent

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

Hello Vincent!

** On Wednesday 13.05.20 - 23:33, Vincent Coen wrote to August Abolins:

Would your parser break if the original echoname had a number after
it?

eg. OS2

.: OS22.ECO, OS23.ECO, etc..

Nope that is totally valid.

Then your parser is pretty darn good! Good work.


I do however have a couple of suggestions in your "operations manual":

ELIST Maintenance Program
=========================

But I'll make a separate post about it.


../|ug

--- OpenXP 5.0.43
* Origin: (2:221/1.58)