Hi Mark,
2011/1/22 Mark Sapiro mark@msapiro.net:
However, I have already wondered where to set the web URL. Right now, lists.domain2 still have lists.domain1 e.g. in the List-Archive header.
You want an additional add_virtualhost like
add_virtualhost('lists.domain2.tld', 'lists.domain2.tld')
This is so that you can go to http://lists.domain2.tld/mailman/create (or whatever this translates to in your installation) and create a list and it will be created with the proper http://lists.domain2.tld/mailman/ web_page_url and lists.domain2.tld host_name.
Ok, I added this and restarted mailman.
Also you can use "bin/newlist -u lists.domain2.tld" to create a list properly in this domain, and you can use
bin/withlist -l -r fix_url -u lists.domain2.tld existing-listname
to fix the web_page_url and host_name for an existing domain2 list (after doing that, you may need to run bin/genaliases to update virtual-mailman).
That doesn't seem to work for me, it throws out "option -u not recognized". :-( If I manually invoke fix_url.py, the -u option is indeed offered. What'sw rong?
This will make appropriate links with host lists.domain2.tld in the List-* headers in posts, on all dynamic web pages and all new or modified archive pages for the list. However, existing static archive pages will still have "listinfo" links with the old domain. These either have to be ignored, edited manually or updated by rebuilding the list's entire archive with "bin/arch --wipe listname".
Florian