At 12:20 PM +0100 2006-06-08, Ian Eiloart wrote:
> No, that's not true. What's required is that Mailman provide a simple API
> to allow MTA developers to ask Mailman whether a particular sender is
> permitted to post to the list. Holding rosters (a v3 proposal) in open
> databases would solve this problem - at least for Exim.
That's fine, for Exim.
> Although Mailman is capable of filtering on other factors, I don't think
> the number of cases is significant. However, it might be possible to extend
> the API to provide information on other list policies.
I disagree that it's not significant. If you want to extend the
"simple API" argument to other aspects of the filtering Mailman is
capable of doing, that's fine.
But you still have to have something to use that API to tell the
MTA what it needs to know and when, and I don't think we can
necessarily depend on the MTA authors to create that. Maybe the Exim
authors could and would do so quickly, but that's not the only MTA we
have to concern ourselves with.
--
Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
LOPSA member since December 2005. See <http://www.lopsa.org/>.
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
