In message <[EMAIL PROTECTED]> on Wed, Feb 05, 2003 at 11:22:38AM +0800, James Devenish wrote: > In message <[EMAIL PROTECTED]> > on Tue, Feb 04, 2003 at 10:09:25PM -0500, Jon Carnes wrote: > > Look at ~mailman/bin/fix_url.py. [...] > I wasn't clear on when I would be prompted for an address.
Whoops, I now see that the description is on the """ line, above the synopsis sentence. But the code makes it look like it sets the list's web address to be the same as the default, and the list then uses that stored value rather than the default. So I would people generally have to consider doing fix_url when doing a site-wide web address change? General questions (almost rhetorical, since Mailman seems to be working for me for the time being): - is this behaviour generally true of the way mm_cfg.py is used by Mailman? - should Mailman users expect other hidden variables to require updating in a migration? (Though, given everything we changed in our system, it does seem to be the only problem.) The reason I ask if that this extra migration step is something that we were not exposed to during installation or regular maintenance, and which I have failed to intuitively find in the various "lister server admin" docs. ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
