Pete --
 
We have had some nasty experinces
with semi-documented features before, and want me to check on whether there
might be nasty side-consequences, etc. to using "filter" -- and/or to
see if there might be a more general solution to the problem.
The documentation wasn't especially clear, from what Noel, the
LISTSERV administrator here, and I could find.
It appeared that setting a simple "safe" flag, without even using "filter,"
might do the trick and prevent other similar problems, too.
But it was hard to tell. Any thoughts/advice on this?
With such a large list, I'm hesitant to try too many experiments.
 
Thanks,
--Marc
 
=======================================================================
==================Pete's message re "filter" is repeated below here====
=======================================================================
 
====================================
>>Ps.  Here's a suggestion made by one of our subscribers.
>>Does anyone have first-hand experience with "filter" and KNOW
>>for certain whether this would be a good thing to do?
>>The documentation was less than clear on the matter.
>> ======================
>> Have your listserv manager update your mini-air list definition
>> headers with something like:
 
>>        * filter= also,*postmast*@*,*postmstr*@*
 
>>        This will / should help prevent such loops.
>>        ==============================
 
>Well, since I: was/am the subscriber (who made the suggestion), have
>given help to your site's listmgr on searching the archives (via
>LSTSRV-L), and am subscribed herein, my answer is, YES, it would be a
>good thing to do.
 
>BUT, caveat emptor: that's Latin, for don't send the net-lawyers after
>me if there is some other problem.  ;-)
 
>--  co-owner INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L
>[log in to unmask] "No joyriders on the Info Super Hiway!"+1 814 863 1843
>31 Shields Bldg. -- Penn State Univ -- Uni>versity Park, PA 16802-1202 USA