From owner-freebsd-chat Mon Feb 12 8: 1:44 2001 Delivered-To: freebsd-chat@freebsd.org Received: from fling.sanbi.ac.za (fling.sanbi.ac.za [196.38.142.119]) by hub.freebsd.org (Postfix) with ESMTP id 0543637B491 for ; Mon, 12 Feb 2001 08:01:40 -0800 (PST) Received: from johann by fling.sanbi.ac.za with local (Exim 3.13 #4) id 14SLPf-000B64-00; Mon, 12 Feb 2001 18:01:15 +0200 Date: Mon, 12 Feb 2001 18:01:15 +0200 From: Johann Visagie To: Peter Wemm Cc: chat@FreeBSD.ORG Subject: Re: FreeBSD Postfix and Majordomo security (was FreeBSD Ports Security Advisory: FreeBSD-SA-01:INSERT_NUMBER_HERE) Message-ID: <20010212180115.A42554@fling.sanbi.ac.za> References: <009c01c093e5$d1cd7230$94cba8c0@hh.kew.com> <200102111357.f1BDvGU36876@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102111357.f1BDvGU36876@mobile.wemm.org>; from peter@netplex.com.au on Sun, Feb 11, 2001 at 05:57:16AM -0800 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm on 2001-02-11 (Sun) at 05:57:16 -0800: > > Regarding spam, the thought just occurred to me that we can catch a lot of > it by checking that the list name appears in a To: or CC: line somewhere. > eg: If mail to -current does not have '.*current@freebsd.org' in the To: or > CC: line (most spam has got fakeuser@hotmail.com or something), then bounce > it. > > I suspect that would catch almost all of the spam that currently slips > through the content filters. My own very subjective experience (i.e. I didn't try to keep any hard stats) on the lists I run is that this is good for catching probably 95% or more of current spam. Let's hope the authors of mass mailers don't get wise to this. :-/ -- Johann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message