From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17938 invoked from network); 24 Sep 2002 05:03:55 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 24 Sep 2002 05:03:55 -0000 Received: (qmail 29787 invoked by alias); 24 Sep 2002 05:03:41 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5379 Received: (qmail 29773 invoked from network); 24 Sep 2002 05:03:40 -0000 To: zsh-users@sunsite.dk Path: not-for-mail From: Geoff Wing X-Newsgroups: lists.zsh.users Subject: Re: spam sucks Date: Tue, 24 Sep 2002 05:03:35 +0000 (UTC) Organization: PrimeNet Computer Consultants Message-ID: References: <20020923233105.GA12367@spoon.pkl.net> <20020924043115.GA16363@dman.com> Reply-To: mason@primenet.com.au NNTP-Posting-Host: sparkles.primenet.com.au X-Trace: coral.primenet.com.au 1032843815 17930 203.43.15.10 (24 Sep 2002 05:03:35 GMT) X-Complaints-To: usenet@coral.primenet.com.au NNTP-Posting-Date: Tue, 24 Sep 2002 05:03:35 +0000 (UTC) User-Agent: slrn/0.9.7.4 (NetBSD) Clint Adams typed: :> SpamAssassin has so far caught the vast majority of them. I have it :> setup to work through procmail, which mailman can also do, and is :> aparently a good idea. : Still, spamassassin tags plenty of false positives, lets actual spam : through, and requires someone to look over its shoulder to resolve the : former problem, at least. One point here: the users list and workers list have _never_ had a valid email message only composed of html. All messages I receive like that are put into a (very) low priority reading queue (just in case someone does send such an unlikely beast). For people using procmail, just insert a bitbucket recipe for them. Simplistic version below: :0: # dump the rubbish sent through zsh lists * ^Mailing-List: contact zsh- * ^Content-Type: (text/html|multipart/alternative) /dev/null Regards, -- Geoff Wing : Rxvt Stuff : Zsh Stuff :