I have just switched over to lighttpd, and in the process had to hack up mailman a bit to make it go. I have an ebuild that does the same hacking, as well as a lighttpd-mailman.conf file that is installed by the ebuild. I'll attach it here for you and other interested parties. It works great for me.
Created attachment 113427 [details] files/lighttpd-mailman.conf This is the config file for lighttpd which enables all the mailman magic. It is installed by the ebuild into /etc/lighttpd/mailman.conf, and must be enabled by adding the line: include "mailman.conf" to the /etc/lighttpd/lighttpd.conf file, as is explained in the post install instructions of the ebuild.
Created attachment 113429 [details] mailman-2.1.9-r1.ebuild This is the ebuild that does all the magic, allowing you to install mailman for lighttpd. Main changes: - Now has IUSE="apache apache2 lighttpd ..." < You must choose exactly one of these three, and the ebuild will shut you down if more than one is on. - For USE="apache" or USE="apache2", this ebuild should function exactly the same. - For USE="lighttpd", it configures mailman with --with-cgi-gid=lighttpd, hacks the IMAGE_LOGOS path in mm_cfg.py.dist (and in the existing mm_cfg.py if it is not set there) to be '/mm-icons/', and installs the 'lighttpd-mailman.conf' in the appropriate place, which enables /mailman/, /mm-icons/, and /pipermail/ appropriately.
>- Now has IUSE="apache apache2 lighttpd ..." < You must choose exactly one of > these three, and the ebuild will shut you down if more than one is on. I would like to suggest that it is ok to have none of these use flags set, as it isn't really a requirement to manage mailman through a webserver (although it is certainly more convenient). Another good reason for this is that your email server and webserver might not be the same machine (if the mailman directory is setup as an share, since obviously they need to use the same databases).
the latest mailman ebuild is now pretty much webserver independent, so I consider this as fixed.
