We are doing virtual hosting with LISTSERV 1.8d on Solaris. We are using
Apache for web service and sendmail for SMTP service. Based on our
experience, it appears there are three key elements to successful
implementation of virtual hosting on a LISTSERV server.

1. DNS - You must an A record for the virtual host name, in order to
         ensure that the host name on outbound mail is not rewritten
         by your SMTP service. You may want to add an MX record. It
         should not be necessary, however, some sites refuse mail from
         hosts and domains which do not have an MX record.

2. Web server configuration - Another respondent covered this for IIS.

3. LISTSERV configuration - Add the virtual host name to the MYDOMAIN
   statement in the go.user file, then restart LISTSERV.

   To identify the individual lists that are to be hosted on the
   virtual host, add a "List-Address=" statement to the header of each
   list which is to be hosted on the virtual host. The List-Address
   statement can be used to specify the complete list address. It may
   also be used to specify either the user portion or the host portion
   of the address. In this case, you need only the host portion of the
   list address, i.e., the virtual host name.

   Example: * List-Address= www.aquascapedesigns.com

List postings will use the virtual host name in the return address.
Our experience indicates that, in all other aspects of LISTSERV
operations, the virtual host name is ignored. The output of the
"lists" command includes all lists on the server, regardless of
their respective virtual host names, and there is nothing in the
"lists" output to indicate that any of the lists are associated with
different virtual host names. It also appears that you can use any
valid virtual host name to send commands for any list on the server,
or to post messages to any list on the server.

L-Soft has a white paper on virtual hosting. Send an email message to
[log in to unmask] and request a copy of the white paper on virtual
hosting. It may not answer all your questions, but it should help.

--
Paul Russell
Senior System Administrator
University of Notre Dame