I want to provide some extra services for people who sign up for specific mailman lists.
Is there a way to have apache2 Auth* directives query username and password from mailman? I was imagining something like: <Location /foo> AuthType Basic AuthName "Some service" AuthMailManList FooList require valid-user </Location> Thanks for your help! Details: Specifically, I wanted to let mailing list subscribers access a matching TRAC project. This way, I don't have to let anonymous have write access to everything (I know the search-engine-linking idiots and spammers will fill the wiki and such with crap). But at the same time, I can let nearly anyone edit the wiki and I know that the user has a valid email address. I could just write a "registration" application to send the email, verify the result, write it to a DB and all that junk myself, but mailman *has* all this code and the database of users is nearly the same, if not the same. So why write duplicate code to duplicate the data! I have one possible work around which I'm not keen to impliment. I could just write a python script to do a "list_lists" and then pull out the users and passwords and put them in a database compatible with Apache (either a postgresql db or a .htpasswd file or something). That *is* assuming I can pull passwords out of mailman, either as plaintext or something I can hash to (like md5sum) to put in the apache source. Ciao! ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
