Michael Heseltine writes:
Do you have all of these apache modules enabled, proxy.conf, proxy_http.load and proxy.load, in particular proxy_http.load?
Well, mostly:
# a2enmod proxy_http.load Considering dependency proxy for proxy_http: Module proxy already enabled Module proxy_http already enabled # a2enmod proxy.load Module proxy already enabled # a2enmod proxy.conf ERROR: Module proxy.conf does not exist!
In my Debian configuration that module is needed because it contains the necessary directives to enable proxying. Do you have a "ProxyRequests On" and appropriate <Proxy> blocks elsewhere in your configuration? Is it possible that you have a location control in the <Proxy> block that blocks http proxying for Mailman's URL? (I agree that this doesn't make sense given the "protocol not found" error, but I can't see how this is a Mailman- side problem, either.) Is it possible you have an ftp or other non-http proxy and shut off the http proxy for security's sake?
Is it possible that the mod_proxy_http.load file is corrupt (or empty)? The a2*mod scripts do a thorough job of examining the file system, but don't check runtime functionality as far as I can see (but the last time I needed Perl I let Jeff Friedl do it for me, a loong time ago :-).
The bottom line, though, is that that error message has to do with the internal configuration of Apache, and as far as I can see it has nothing to do with Mailman itself.
Steve