[Mailman-Users] Cabalists and Users, A question of usage...
Barry A. Warsaw
bwarsaw at cnri.reston.va.us
Wed Nov 10 23:42:05 CET 1999
>>>>> "DB" == Dan Busarow <dan at dpcsys.com> writes:
DB> I haven't actually done this with mailman but see no reason
DB> why it shouldn't work. Oh, the html links included in emails
DB> would have to use the internal name, guess there is a problem
DB> there. :(
I wonder if you could play with Apache rewrite rules to get around
this. I've just set up a second faster machine onto which I will be
migrating all our Mailman lists (and testing the new code in the
meantime). I figured out that by using rewrite rules, I can migrate
lists one-at-a-time and the public would never know it.
What I'm doing is setting my second machine to act like it is running
off the primary python.org website. I.e. in my mm_cfg.py file I have:
DEFAULT_HOST_NAME = 'python.org'
DEFAULT_URL = 'http://www.python.org/mailman'
I can point the aliases on the old machine to the new machine. Then I
add the following Apache rewrite rules for each list I move:
RewriteRule /mailman/(.*)/mylist(.*) http://other.python.org/mailman/$1/mylist$2 [P]
RewriteRule /pipermail/mylist(.*) http://other.python.org/pipermail/mylist$2 [P]
Seems to work so far!
More information about the Mailman-Users