[Mailman-Developers] 2.1.8 documentation mismatch

Barry Warsaw barry at python.org
Wed Jun 7 20:45:03 CEST 2006


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

On Wed, 7 Jun 2006 12:24:26 -0500
Brad Knowles <brad at stop.mail-abuse.org> wrote:

> 	It's not just the MTA extension frameworks, it's also the
> myriad of things that Mailman may choose to do or to look at when
> deciding what to do, based on content in the message.

I agree.

> 	I don't think it's feasible to completely re-write Mailman,
> or to completely re-write the MTAs, so that each of them has a deep 
> integral understanding of all the nuances and complexities of the 
> work that is being done by the other.
> 
> 	Short of doing a rewrite on that scale, I suspect that we're 
> going to continue to have these kinds of problems for some time.

There will certainly be limits to what you can do, but essentially the
idea is that the MTA would be asking Mailman what it would do with a
particular message.  Kind of like the MTA calling out to SpamAssassin
at various points in the SMTP protocol.

- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iQCVAwUBRIcer3EjvBPtnXfVAQKK5wP/fjgFY1rBOErUXr1y154MUSylRYGzEu7K
DqETUMsH/DuBB7Q+AUYxIeM0uS245p2jffGbWPI9pHl6Ysvb8NKo9tV+yMLlLaYs
GhyUZC29fBejqQI5EwvmDlWHSfXwku8S4yk7CFS2jnkOyfme0XMBwKj8YcLZ06aL
GdUMyKHq9XU=
=/bQu
-----END PGP SIGNATURE-----


More information about the Mailman-Developers mailing list