9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] spam filtering
Date: Mon, 24 Feb 2003 14:17:29 -0500	[thread overview]
Message-ID: <Pine.LNX.4.30.0302241405250.2991-100000@athena> (raw)
In-Reply-To: <Pine.LNX.4.30.0302241051430.2991-100000@athena>

Scott,

I downloaded 2.0.13 since 2.0.11 wasn't
available.  The file
	$MAILMAN/Mailman/Handlers/SpamDetect.py
where MAILMAN is your install directory
is a hard coded spam filter file.  Adding
an RE for html or anything other combination
of incantations seems easy.  The current code
does an OR (if any RE matches, fail).  I would
suggest adding an AND mechanism such that
any message lacking 'RE:' in the subject
header gets sent through a rigorous set
of RE filters (html, nigerian, etc).  I can
come up with something if you don't want to.

Btw, that's some nasty Python.  I hope it's
not representative of the language.

Cheers,

Sam


On Mon, 24 Feb 2003, Sam wrote:

>
> > As Scott said yesterday, the list uses Mailman.
> > http://www.gnu.org/software/mailman/mailman.html
> > As he also said, he can't do anything that isn't a stock
> > Mailman option.  If you want to suggest something,
> > please look in the documentation first.
> >
>
> Actually, what he said was anything that wasn't a stock
> option "would require actual work."  I took that to
> mean we're looking for a least effort solution to the
> problem, not that we're handcuffed by mailman.  I
> think it's already been stated that the stock features
> aren't sufficient.  Before I go hacking, which version
> are we using?
>
> Sam
>
>
>




      reply	other threads:[~2003-02-24 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 13:49 [9fans] (no subject) David Presotto
2003-02-24 15:11 ` Sam
2003-02-24 15:14   ` [9fans] spam filtering Russ Cox
2003-02-24 16:04     ` Sam
2003-02-24 19:17       ` Sam [this message]

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=Pine.LNX.4.30.0302241405250.2991-100000@athena \
    --to=sah@softcardsystems.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).