LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"A. Harry Williams" <HARRY@MARIST>
Fri, 18 Nov 88 17:19:40 EST
text/plain (42 lines)
I have written an XEDIT macro called LISTDEL that I will make available
to anyone who sends me mail.  It isn't perfect, but it is designed to
run as either a macro for PEEK or with RiceMail.  There is no doc.
You say LISTDEL in many rejection notices, and it will delete that person
from the list using the QUIET option.  Here is the comment from the
begining of the macro
 
/******************************************************************\
*                                                                 *
*  Xedit EXEC to build a listserv job to delete users from a list *
*                                                                 *
*  There are 4 possible arguments: (none), IMMED, DELAY, FILE     *
*  (none) - try and parse, displaying result                      *
*  IMMED - Send a message to immediately delete person from list  *
*  DELAY - Place the cmd to issue the message on the cmd line     *
*  FILE - Build a batch job to be sent to a listserv to delete    *
*                                                                 *
*  Written by A. Harry Williams - Marist College - May 1988       *
*                                                                 *
\******************************************************************/
 
 
The command is a TELL x AT y QUIET DELHERE z u@n PW=pswd.
 
The y is parse from the rejection notice.  x is gotten from the
GLOBALV used for LSVPUT, as is the password.  A nickname is used
if it exists in the names files.  (This is designed for usage
with DELAY option in RiceMail because of lack of space.)
DELHERE is used because if a list was never exploded, or the
person might have been added at the wrong place.  The node
has been parsed, and listserv forwards a del, before checking the
current list.  There are some rejections it has problems with,
especially those that listserv say comes from [log in to unmask]
It usually parses those as listname POSTMASTER.  It also has
problems with multiple reciprients on a node, but it recognizes
that it is having problems.
  It also works with deletion requests from Listserv.
 
Send me the requests, and I'll box up a DIST2 job later next week.
 
  Harry

ATOM RSS1 RSS2