6.23. Mailman and nginx
This FAQ will try to illustrate how to setup Nginx (http://nginx.net/) for Mailman support.
Since Nginx does not supports CGI, we need an additional web server for serving CGI scripts.
In this FAQ I use thttpd (http://www.acme.com/software/thttpd/).
First of all, lets configure thttpd so that it can serve the CGI scripts defined in our system (I'm using Debian Etch).
Edit the /etc/thttpd/thttpd.conf and set:
Note that, by default, thttpd will generate index pages for directories and you usually do not want this.
You can either recompile thttd, undefining the GENERATE_INDEXES macro in config.h, or you can `chmod 711` the individual directories.
Restart thttpd with
Now lets configure nginx.
Create a new file in /etc/nginx/sites-available, as an example `lists.domain.com`, an create a symbolic link in /etc/nginx/sites-enabled to enable the new site.
This configuration assumes that a virtual server can be dedicated to Mailman.
NOTES: Nginx does not transfer, by default, the Server header from the proxied server response.
Moreover, if you enable `proxy_intercept_errors`, then all the errors from thttpd will be handled by nginx (but you need to create error pages, since a default nginx installation only has a custom 50x.html page).
This can be useful if you want to hide thttpd usage.
Last changed on Thu Nov 29 13:36:32 2007 by Manlio Perillo
7. What's new with Mailman 2.1?
Converted from the Mailman FAQ Wizard
This is one of many Frequently Asked Questions.