LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

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

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

Print Reply
"A. Ralph Papakhian" <[log in to unmask]>
Mon, 5 Jun 1995 14:27:27 EST
text/plain (42 lines)
Hi. Can someone at lstown-l help with these questions? --ralph p.
 
*GO*   Cordially, forever more,
*!!*   A. Ralph Papakhian, Music Library (Co-Listowner for MLA-L@IUBVM)
*IU*   Indiana University, Bloomington, IN 47405
       (812) 855-2970  [log in to unmask] [log in to unmask]
 
----------------------------Original message----------------------------
So, as most of us have undoubtedly discovered by now, there are major
differences in the error-handling routines of the new version of
LISTSERV.  Can anyone provide better information than the
documentation (e.g. info from other discussion lists)?
 
Specifically:
 
INFO KEYWORDS (Appendix B of the complete manual) discusses
Auto-Delete=Full-Auto and Auto-Delete=Manual but not
Auto-Delete=Semi-Auto, which just happens to be the default in most
cases. (!)
 
The Auto-Delete=Delay(n) option is completely incomprehensible to me.
What is LISTSERV doing, exactly?  If the Delay is set to 4, does
deletion occur only if errors are recorded on days 1, 2, 3, and 4?  Or
only if errors occur on days 1 and 4?  One part of the documentation
says:
 
"For instance, if Delay(7) and a subscriber's mail regularly bounces
on the weekend, LISTSERV will wait until [t]he next weekend to decide
whether or not to delete him, at which point the subscriber will
bounce mail again and start the process all over.  The bottom line is
that LISTSERV might as well have gone ahead and deleted the subscriber
as soon as the first bounce occurred."
[from Appendix B of List Owner's Manual (c)1995 by L-Soft
international, Inc. copied here without permission]
 
"Start the process over" and "Might as well have gone ahead and
deleted the subscriber" seem to me to be contradictory.  Or...?
 
 
A very confused SLAJOB Listowner,
Spencer M. Anspach

ATOM RSS1 RSS2