|
Sender: |
The Revised LISTSERV Distribution List <LSTSRV-L@DEARN> |
Subject: |
|
From: |
Eric Thomas <ERIC@FRECP11> |
Date: |
Sun, 1 Nov 1987 12:21 SET |
Reply-To: |
The Revised LISTSERV Distribution List <LSTSRV-L@DEARN> |
A last note on the TCSSERVE saga: I personally think it would be a good idea
to keep a TCSSERVE userid running at TCSVM. It would ignore anything sent to
it as mail (maybe CP TRANSFER it to John), but would process incoming
messages. A very simple parser would identify the request, and it would issue
a GIVE command to LISTSERV to cause files to be delivered to the invoker. It
would also send a message back explaining about the new way to send commands,
etc. This would have provided a better continuity for the end-user. Example:
tell tcsserve at tcsvm sendme edate exec
R;
FROM TCSVM(TCSSERVE): * TCSSERVE has been moved over to [log in to unmask]
FROM TCSVM(TCSSERVE): * For more information, send a NEWS command to TCSSERVE.
FROM TCSVM(LISTSERV): * TCSSERVE@TCSVM has requested that file "EDATE EXEC"
FROM TCSVM(LISTSERV): * be sent to you.
FROM TCSVM(LISTSERV): * File "EDATE EXEC" has been sent to you in Disk-Dump
format.
I think that LISTSERV owners who would be planning such a conversion should
use a similar approach, so as to avoid electronic news magazines reporting
that "TCSSERVE has been phased out" :-)
Eric
|
|
|