[Mailman-Users] Mailman and virtual domains...

[Grant Taylor]

On 7/9/2009 4:55 PM, Mark Sapiro wrote:
> It looks like you've found answers to most of your questions, but to 
> summarize, assuming you have the requisite add_virtualhost() 
> directives, when creating a list from the web, it gets created in the 
> domain of the url used to access the create page.

Yes I do have two add_virtualhost() directives.  Per the Defaults.py 
file comments I also am setting DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST 
as the compile time config of the package from the distribution does not 
match my needs.

    DEFAULT_EMAIL_HOST = 'maillists.example.net'
    DEFAULT_URL_HOST = 'maillists.example.net'
    add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
    add_virtualhost('groups.example.com', 'groups.example.com')

> The domain of an existing list or lists can be changed by running 
> fix_url under withlist.

*nod*

> The -u/--urlhost and -e/--emailhost options are relatively recent 
> additions to newlist. The existing interactive dialog wasn't changed 
> when these were added for backwards compatibility reasons.

Ah.  That makes sense.

> In the past, and still, you can specify the domain for a list by 
> specifying the listname as LISTNAME at WEB_HOST. This is the same as 
> specifying the list name as LISTNAME together with the 
> --urlhost=WEB_HOST option. Note that this can be confusing because 
> LISTNAME at WEB_HOST is not necessarily the list posting address which 
> is LISTNAME at EMAIL_HOST. This is explained in the help for newlist.

I got the (mis)understanding that the LISTNAME at WEB_HOST was deprecated 
and might be removed at some point.  Is this not the case?

I guess I should ask, what is the preferred method to do it going 
forward?  (If I'm going to learn it, I'd like to learn the proper and 
preferred way.)



Grant. . . .