On Wed, 10 Jul 2002 the voices made Ryan Cleary write:
> On Wed, 10 Jul 2002, Tony L. Svanstrom wrote:
>
> > On Wed, 10 Jul 2002 the voices made Darren Coleman write:
> >
> > > This is such a special case that it would probably be the wrong thing to
> > > do to insert additional rules into the public distribution of SA just to
> > > take account of this. Easiest solution is just to zero the rules or, if
> > > this isn't acceptable, write your own regexps to handle the cases you've
> > > mentioned - both on your own private installation.
> >
> > The correct solution is, of course, to whitelist the mailinglists...
>
> Unless you don't want to receive the spam that gets sent to the lists...
>
> I agree that adding the Linux kernel specific rules is a bit much, but
> there are already rules for diffs and pgp headers, so maybe the geek code
> rule might be worthwhile as an indication that the message is
> probably not non-spam.
The problem is that no matter how much you rewrite the rules some "languages"
(real languages, code, encodings and so on) will have words and phrases too
similar for there to not be at least some problems.
When it comes to mailinglists they shouldn't be open for anyone to post to,
and if there are any problems (with spam) the owner should deal with it.
/Tony
--
# Per scientiam ad libertatem! // Through knowledge towards freedom! #
# Genom kunskap mot frihet! =*= (c) 1999-2002 [EMAIL PROTECTED] =*= #
perl -e'print$_{$_} for sort%_=`lynx -source svanstrom.com/t`'
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Two, two, TWO treats in one.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
