Subj : Echo Savior Rides Again
To   : ANDREA SANTOS
From : Thom LaCosta
Date : Sat May 12 2001 10:12 am

ANDREA SANTOS wrote in a message to ROY WITT:


 AS> If this is the case, and I'm not sure I have all the messages
 AS> onhand in two places to check, I was not notified by any method
 AS> when mine almost expired.  Had sent in updates somewhere in the
 AS> Fall of 2000.  Sent them again after 2001.  IIRC, Thom then routed
 AS> mail for me to Jerry Gause telling me I would need to resend the
 AS> updates.  

To be more accurate, all mail from the robot leaves here and is sent via 
1:140/1  Ifr there is a routing problem, it needs to be addressed to 1:140/1, 
not the Echolist Keeper.


 AS> Prior to a year ago, I didn't carry ECHOLIST.  A former Net135
 AS> node, now user, asked me to, but I didn't have it turned on so had
 AS> no idea my echos didn't take.  I've never received email or netmail
 AS> notification from the EK confirming my echos were updated, so
 AS> unless you're reading ECHOLIST, you don't know.   

But, if you had read the docs for the echolist, you'd see that the Echolist 
Robot sends out confirmations.  There are some moderators, having read that, 
actually query me if they don't get a confirmation message.

Admitedly, there are some moderators that either don't read the docs or don't 
take the time to query if they don't get a confirmation message..and an even 
smaller nunber who whine while not doing anything to ascertain the nature of 
the problem.


-> Some users, the really smart ones, would figure out after weeks go by 
-> that the moderator didn't have the password to update the listing.  
-> Hence, an echo hijacking takes place.

Relisting an expired echotag is not hijacking.


Thom LaCosta
baltimoremd@baltimoremd.com
http://www.baltimoremd.com/ 
---
 * Origin: Home of The Other Robot (1:261/1352)

.