On 8/1/2003 10:13 PM, STEPHEN HART wrote to CHRIS CRANFORD

->  ->> -+--+--- Forwarded Message -+--+--+-
->  ->> Original: DATE..... 7/20/2003 10:24 AM
->  ->> Original: FROM..... STEPHEN HART
->  ->> Original: TO....... Z1B OPERATIONS

-> Darn.  I had planned to change the "to field" to address my message
-> to "All" but I rushed my reply and forgot.  Anyroad, my message was
-> just intended to reassure regular MooseChat participants that the
-> EchoList entry had been taken care of...

Not a problem at all Stephen.

-> Yes.  I've even ended-up forwarding them to echo moderators who were
-> temporarily out of touch.

Good man!

-> Meanwhile, I just realized that I'd confused the netmail warning the
-> EchoList Robot sends with the "expired echolist" warning send by what
-> I'm guessing is a robot program using the "Z1B operations" name.

Sometimes I wish it was a "robot" :-) ... It's all manually done here.
I actually have a secondary account setup at 1:379/1200 which I use to
administrate the Z1B Backbone's Operation (aka Z1B OPERATIONS). :-)

-> Hmmmm. I'll be interested to see whether the EchoList Robot also send
-> e-mail warnings.  Tho, what with no worries about calling when my
-> long-distance plan makes it less expensive, I might do something
-> "really wild" and just make sure that I send updates before
I need any
-> warnings at all.  ;-)

ECHOLIST updates do send warnings (I think I recall seeing them a while
back); however I have an event that is setup which runs monthly to send
Thom's system an update for all my moderated echos.

I typically send them via EMAIL to avoid any long distance costs and to
also avoid routed netmail which can sometimes get caught in transit and
never makes it to Thom's ECHOLIST processing system.

-> Thanks, and also thank you for the feedback on using e-mail to contact
-> the EchoList robot.  Seems like I really should drag myself into the
-> twentieth century and go with the e-mail method.

It's proven to be more reliable for me than NETMAIL.  I'm not saying
anything is bad with NETMAIL; however it's more of a direct approach in
my case since I route all my outbound NETMAIL not for a peer or network
member of Net 379.

Thanks,
Chris

--- Mail-ennium/32 v1.01.301.11c/#01-0001