* Forwarded (from: echolist) by mark lewis using timEd/2 1.10.y2k+.
* Originally from mark lewis (1:3634/12) to Thom LaCosta.
* Original dated: Sat Dec 29, 21:16

 TL> * Copied (from: elist) by Thom LaCosta using timEd 1.10.y2k+. 

this hasn't appeared on my machine in the elist echo as shown by your
copied header above... it was probably detected as a dupe due to the copy
vis-a-vis forwarding ;)

[edit: it has appeared now...]

 TL> Hello All!

 TL> Some time ago someone was submitting updates and forging the name
 TL> and address of the moderator of the echo(es) in question.

please, thom... be very careful when using terms like "forging"
when talking about instances of others providing updating services for
moderators who don't, won't or can't make updates to your elist...

i've been offering this service for a long long time and have never forged
the name of any moderator... there is no reason for one to do such but i
guess that depends on what one views as forgery :?

if the moderator knows that the updates are being done by someone else and
they have the moderator's approval, then there's no forgery taking place...

 TL> It finally stopped when I threatened to file official complaints
 TL> against the node committing fraud.

 TL> It's happened again...and I have submitted an official complaint. 

 TL> If you are a moderator and your update didn't go through, it may be
 TL> because you are using the "service" of a person who offers to
 TL> submit your updates and make them appear that they are from you.

 TL> Don't be too surprized when your listing lapses and when you are
 TL> asked to answer questions about your participation and/or knowledge
 TL> of the fraudulent updates. 

i hope that none of the tags involved are any that i've been updating all
these years... i've not gotten any word about any official complaints or
such... can you maybe be a bit more specific??

)\/(ark

___ 
 - Origin:  (1:3634/12)