So then: Are the command line scripts the best way to create a duplicate set of configurations, mailing list lists, and list members on another mailman running on another server, or is it possible (and preferable) to figure out which mailman files should be copied over to the second server to create the duplicate settings, lists, and members?

If I were automating this process would I rsync the specific files, or write a cron script to run the various python scripts, send them over to the other server and then have the other server run a cron script to import the settings, lists and members....

Thanks,
Jeff



Mark Sapiro wrote:

Mauricio Tavares wrote:



Let's see if I make sense. I know I can create a mailing list config file as an ascii file and then feed it in (I forgot the name of the command so I am not going to worry about it) to the mailing list to create its binary config file. When I go to the admin page, I can also change its settings. But, let's say I come up with really neat settings and would like to apply them to a few more mailing lists. Is there a way I can save the configuration of a given mailing list back to an ascii file so I can do any minor changes and feed it to the other lists?




 bin/config_list --help

It works in both directions.


--
Mark Sapiro <[EMAIL PROTECTED]>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
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/






------------------------------------------------------ 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/

Reply via email to