On Thu, 2004-08-05 at 19:17, D. D. Brierton wrote: > On Thu, 2004-08-05 at 23:58, Alexander Dalloz wrote: > > I wouldn't at all put anything to /dev/null automatically. Just let it > > write to an mbox file or Maildir which you once a week or every 2 weeks > > observer with just a few, quick looks. Then, if nothing good in it, kill > > all confirmed SPAM. > > I guess that will be the right thing to do initially, to test it's > working. But eventually I want anything that is 99.9% probable spam to > go straight to the bit bucket. It isn't *that* time consuming to check > through spam to make sure it really is spam, but I've realised recently > that it makes me really really annoyed (at the spammers) and I could > just do without that. >From the sound of things you are running a full MTA using sendmail or procmail. If you really don't want to have to wade through the spam that spamassassin marks for you try greylisting. I implemented milter-greylist with sendmail. We were getting between 3000 and 6000 spam messages a day. After implementing greylisting we get 3 to 10 spam a day. (that is not a typo, 3 to 10) spamassassin tags the ones that still come in but the time it takes to check for false positives is negligible now. In addition the email server does not use nearly the resources it once did. Plus the savings on bandwidth since the server never receives the body of the spam messages. If you are using procmail there is software available that implements greylisting for that as well. Since implementing this I have been able to get back to doing real work instead of fighting spam so much. :) -- Scot L. Harris webid@xxxxxxxxxx if (!cost_analysis) goto darwinism; - Mike Galbraith explaining economics on linux-kernel
