[Mailman-Developers] Google Summer of Code - Spam Defense

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Apr 2, 2008, at 1:02 PM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>> Mailman to something like SpamAssassin.  One of course would be a
>> fairly simple handler to recognize SA headers and do the appropriate
>> thing.
>
> Why have a Handler when you can already use header scanning in the
> privacy filters?  Ie, isn't this a documentation or UI problem rather
> than a Handler problem?

I'm really thinking about Mailman 3's rule architecture.  I think it's  
going to be much better to have narrower rules for specific purposes,  
as they can be packaged in plugins, enabled separately etc.  A generic  
header regexp matcher could be used, but would probably be a bit more  
difficult to use.

>> Your idea of having a call out to SA to scan the message is valid
>> too though, because I don't think everybody is able to hook it into
>> their MTA, for whatever reason.  This wouldn't be on by default,
>> but it should be an option.
>
> Even if you can't hook it into the MTA, it's certainly possible to do
> this via procmail, etc.  There are so many ways to do this already.
> Why doesn't TOOWTDI apply here?

Because I think you're talking about different sites having different  
administrative domains.  In some, it will make sense to do it as far  
upstream as possible, but in others, it's going to be left to the list  
admin, so they should at least have the ability to enable such filters  
if nobody else will.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkf0PlYACgkQ2YZpQepbvXE7GQCfZQfB5JzwxtoomyXSkraMuO7r
FYAAoJ5/FD294hMx2s0/QLDkJD9XNec1
=VHlH
-----END PGP SIGNATURE-----