On Thu, 27 Jun 2002 mailman-users-request@python.org wrote:

Subject: [Mailman-Users] Mailman, Virtual Hosts and SUEXEC

The server owners run suexec for security, so, it's either expose the machine to hackers by running mailman and others as root, or expose the identity of the server owner to the customers of the resellers, and there HAS to be a way to make mailman run under suexec and still allow the url admin be the virtual host, like it is without suexec! Please, is there any solution to this? SD

Assuming I'm understanding the question, one potential solution would be to have each virtualhost have it's own mailman installation. An ugly solution, to be sure, but a solution. Another *potential* solution depends on a bunch of things I'm not sure of, but I'll toss it out anyway. Assuming that all the vhosts list address are something like 'lists.virtualhost.com', one could theoretically have ServerAlias entries for the mailman VirtualHost for each of the other virtualhosts:

<VirtualHost 1.1.1.1> ServerName lists.serverprovider.net ServerAlias lists.virtualhost.com ServerAlias lists.customer.net ServerAlias mailman.anothercustomer.org User mailman Group mailman ... ... </Virtualhost>

However, this depends on at least two things...

• a seperate hostname for the list URL for each virtualhost (for example, you couldn't have it it 'www.virtualhost.com', since that hostname already exists in a different virtualhost block),

• mailman dealing with it correctly

...and while the former would simply be a question of finagling it from your provider, the latter would involve mailman handling it correctly. And I've no idea if it does (although I suspect it doesn't).

--n

Here we have a game that combines the charm of a Pentagon briefing with the excitement of double-entry bookkeeping. I don't get it. -- Cecil Adams, on D&D