Thanks for the answers...

...it's good to now understand some of the issues.

The "twice through the list server" thing works very well for me on my list,
but once someone has been detected as a bouncer, is there any way for me to
tell the list server to stop distributing post from them? I am currently
deleting the subscriber the instant I see the first bounce (with 2000
members, I can't afford to be nice about it) but I still see round after
round of bounces come through from the same person.

---
James Newton (PICList Admin #3)
mailto:[log in to unmask] 1-619-652-0593
PIC/PICList FAQ: http://www.piclist.com or .org

-----Original Message-----
From: LISTSERV list owners' forum
[mailto:[log in to unmask]]On Behalf Of Rich Greenberg
Sent: Wednesday, March 28, 2001 11:41
To: [log in to unmask]
Subject: Re: Duplicate Posting problem


On: Wed, Mar 28, 2001 at 12:45:49PM -0500,J Newton Wrote:

} Why can't LSOFT just look for the fact that the message has passed through
} the list server twice?

Because it would have too many false positives.  Look at the headers
from your post (The one I am answering):

> Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com
[209.119.0.109])
>         by mail1.panix.com (Postfix) with ESMTP
>         id 691FC4894D; Wed, 28 Mar 2001 13:09:13 -0500 (EST)
> Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com
(LSMT
> P for Digital Unix v1.1b) with SMTP id
<[log in to unmask]>; Wed,
>  28 Mar 2001 13:09:13 -0500
> Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM
(LISTSERV-TCP/IP
>           release 1.8d) with spool id 90506895 for
>           [log in to unmask]; Wed, 28 Mar 2001 13:09:00 -0500
> Approved-By: [log in to unmask]
> Received: from 209.119.0.7 by PEACH.EASE.LSOFT.COM (SMTPL release 1.0d)
with
>           TCP; Wed, 28 Mar 2001 12:45:50 -0500
> Received: from PEACH.EASE.LSOFT.COM by wnt.dc.lsoft.com (LSMTP for Windows
NT
>           v1.1b) with SMTP id <[log in to unmask]>; Wed, 28 Mar
2001
>           12:45:50 -0500