If you just want to change the default for new lists, you'll want to
change mm_cfg.py so that DEFAULTURLHOST and DEFAULTEMAILHOST use the
new domain. This will only have an effect on new lists.
When converting old lists, you'll need to change the values of those
variables for each list you want to change. The archives will be
untouched by this action.
On 3-Jul-08, at 11:50 AM, [EMAIL PROTECTED] wrote:
I'm running mailman on a server that has an existing domain
(abc.domain.com) and resolves to some IP address X. Couple of 100
lists running in this setup.
I've recently gotten another DNS entry defined (xyz.domain.com)
that also resolves to IP address X.
I'd like to setup new mailman lists to use the new domain--
[EMAIL PROTECTED] What do I need to change to support this?
Note that I'd like the existing mailman lists in the near-term to
continue to use there existing "abc.domain.com" domain.
Now, once mailman supports new lists in the new domain, I might
want to convert all exiting mailman lists to use the new domain.
Is this easy/straightforward? I'd like the archives to be
maintained as well during this conversion process.
Thanks
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%
40python.org/
Unsubscribe: http://mail.python.org/mailman/options/mailman-users/
terri%40zone12.com
Security Policy: http://wiki.list.org/x/QIA9
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9