From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: RE:Re: The spam problem.
Date: 13 Aug 2002 16:47:40 GMT [thread overview]
Message-ID: <ajbd7c$ala$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20020813064215.GZ32427@mea-ext.zmailer.org
In article <20020813064215.GZ32427@mea-ext.zmailer.org>,
Matti Aarnio <matti.aarnio@zmailer.org> wrote:
| Quite so. We don't aim for 100% blocking, we can tolerate a few
| leaking thru each month. A few each day would be too much.
|
| I have been monitoring what our filters do catch; sometimes
| there are things I prefer not to be captured, which means we
| have to fine-tune the filters a bit.. I am also sometimes
| (rarely) sending a note to the message originators that their
| traffic is being captured.
If you have a human to do a little of the work, you can build filters to
do a three category triage; pass, fail, and human review. This allows
the filters to be be MUCH tighter, but assumes 7*24 moderation of some
sort.
Not a recommendation, just a thought. I have this set up on lists and
posting hosts, and it works reasonably well, taking about five minutes a
few times a day on the weekend.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2002-08-13 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 21:09 RE:Re: The spam problem Matt_Domsch
2002-08-13 6:42 ` Matti Aarnio
2002-08-13 16:47 ` bill davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-14 9:43 Hell.Surfers
[not found] <20BF5713E14D5B48AA289F72BD372D6821CB15@AUSXMPC122.aus.amer .dell.com>
2002-08-13 4:46 ` Mike Galbraith
[not found] <861530955@toto.iv>
2002-08-12 20:32 ` Peter Chubb
2002-08-14 12:55 ` Denis Vlasenko
2002-08-12 5:01 Hell.Surfers
2002-08-12 5:15 ` Jim Roland
2002-08-12 7:35 ` David Schwartz
2002-08-12 3:04 Hell.Surfers
2002-08-13 3:19 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ajbd7c$ala$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox