On Nov 1, 2009, at 9:06 PM, Stephen J. Turnbull wrote:
If you really want Mailman to do the authentication, you can either use the Approved header field, which is not very secure, or you can use the 3rd-party patch to use public-key signatures which somebody else mentioned. I'm pretty sure that should work OK because the theory is straightforward, but haven't reviewed it or used it myself,
In theory, it would also be possible for Mailman to trust authentication information that the receiving MTA placed into the headers. It's the same as having Mailman inspect spam headers that some upstream-to-Mailman spam filter places into the message to determine whether the message should reach the list membership.
-Barry
PGP.sig
Description: This is a digitally signed message part
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org