[Mailman-Developers] 2.1.8 documentation mismatch

Ian Eiloart iane at sussex.ac.uk
Wed Jun 7 16:51:54 CEST 2006



--On 7 June 2006 09:26:11 -0400 Barry Warsaw <barry at python.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, 07 Jun 2006 10:41:26 +0100
> Ian Eiloart <iane at sussex.ac.uk> wrote:
>
>> Even better would be to integrate Mailman into MTA's better, so that
>> the MTA can use Mailman data to reject spam.
>
> I think that will be problematic, given the wide variety of MTA
> extension frameworks.

Yes, of course.

> A better approach would be to structure the
> Mailman code in such a way that large parts of it can be used as a
> library, which could serve as the basis for sites writing their own MTA
> extension, or any other specialized Mailman-based application.

Perhaps. Even better would be to hold rosters in open databases. Exim, for 
example, can read sql, ldap, flat files and so on. I don't think it's 
Mailman's job to examine the content of messages - that's the job of a spam 
or virus filter.

> This is actually one of the main reasons why I've been moving the bulk
> of the bin and cron scripts to inside the top-level Mailman package for
> 2.2.  Those scripts need to be refactored a bit better, but they do
> provide some useful higher-level operations that other Python programs
> can now get access to (e.g. by putting /usr/local/mailman on your
> sys.path and doing good ol' imports).
>
> - -Barry
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
>
> iQCVAwUBRIbT93EjvBPtnXfVAQJVOAP/eS5fiGp/mWdoTmlp8p98t8fcMnpgbJ1m
> ljwezQR+3G4FTPI6lymYqAN0xAqYKl4Nwfg6/n3XfUsteD5KaHKuXuTC/FYdMy8B
> XEDjXpNaq0bF8uHQWyJM7LAEr8nuKOMMgAJyLKE/mk1KHGoyiXm6JXaJXu0VB8ib
> rAGvZ5QUl+4=
> =1Z8K
> -----END PGP SIGNATURE-----



-- 
Ian Eiloart
IT Services, University of Sussex


More information about the Mailman-Developers mailing list