I would think you could make it work "outside the system" by setting reply-to-poster, then changing the alias for the list to go both to the list processing command, and to a dummy-user . Then pipe the dummy user's mail into something that is web-accessible. You could use another mailman list, and either keep the membership lists in sync or give the second list a password that you advertise on the first list, or make it public. Or, you could use some mail-to-web gateway other than mailman.
But I agree that in practice this wouldn't work too well. (although, there will never be long chains of messages, because nobody will be able to reply to a reply) ------------------------------------------------------ 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
