[Mailman-Users] duplicating a mailman list?

[Jon Carnes]

D'oh!  My bad... I meant ~mailman/bin/config_list

===
  Configure a list from a text file description.

Usage: config_list [options] listname

Options:
 --inputfile filename
 -i filename
  Configure the list by assigning each module-global variable in the
  file to an attribute on the list object, then saving the list.  The
  named file is loaded with execfile() and must be legal Python code.
  Any variable that isn't already an attribute of the list object is
  ignored (a warning message is printed).  See also the -c option.

  A special variable named `mlist' is put into the globals during the
  execfile, which is bound to the actual MailList object.  This lets you
  do all manner of bizarre thing to the list object, but BEWARE!  Using
  this can severely (and possibly irreparably) damage your mailing list!

--outputfile filename
-o filename
  Instead of configuring the list, print out a list's configuration
  variables in a format suitable for input using this script.  In this
  way, you can easily capture the configuration settings for a
  particular list and imprint those settings on another list.  filename
  is the file to output the settings to.  If filename is `-', standard
  out is used.

--checkonly
-c
  With this option, the modified list is not actually changed.  Only
  useful with -i.

--verbose
-v
  Print the name of each attribute as it is being changed.  Only useful
  with -i.

--help
-h
  Print this help message and exit.

The options -o and -i are mutually exclusive.
===

Sorry about the mis-fire, I meant that you can create nice templates for
mailing list types (or styles) using:
   ~mailman/bin/config_list -o <filename> <listname>

Then edit <filename> to only modify the specific configuration option of
a mailing list that you want changed.  Any configuration option deleted
from the file will be left alone on the list that you feed this back
into. You feed these settings into a list by using:
   ~mailman/bin/config_list -i <filename> <listname>

Hope this is more helpful!

Jon Carnes

===
On Sat, 2002-10-19 at 13:48, Jon Carnes wrote:
> I've seen a python script that does this - it was posted to this list,
> so it must be in the archives.  What you really need to do, is edit your
> ~mailman/Mailman/mm_cfg.py file and add in the defaults that you
> prefer.  Then when you create a new list, the defaults will be set
> properly to your standards.
> 
> Alternately, you can dump out a lists configuration by using
> ~mailman/bin/dumpdb
> 
> You can modify the output and then feed that back into a list (using
> dumpdb again) to modify its configuration!  Dumpdb is a great tool and
> you can use it to dump out and save various mailing list "syles" (like
> announcement only lists, general discussion lists, or moderated private
> lists, etc...)
> 
> Good Luck - Jon Carnes
> 
> On Sat, 2002-10-19 at 08:46, Erez Zadok wrote:
> > [I've used mailman for a few years now, but I'm new to this list.]
> > 
> > How do I create an identical duplicate of a list by another new name?
> > 
> > I'm using mailman 2.0.13.  I'm generally very happy with it.  When I need to
> > create a new list, it takes me time to create it, b/c for the most part I
> > want to configure that list identically to other lists (esp. wrt
> > privacy/protection features).  Specifically I want to turn on/off certain
> > features, etc.  I do so by creating a new list, then going through the Web
> > interface for the old and new list, and setting the options by hand.  It's a
> > pain and time consuming.
> > 
> > I could not find a python script to duplicate one list to another.  I'd like
> > to copy everything: configuration, archives, and subscribership.  Actually,
> > I mostly care about configuration.  I don't mind if the subscribership and
> > archives are duplicated or not (I can handle those relatively automatically
> > by other means).
> > 
> > If someone had written a python script to "cp oldlist newlist" please let me
> > know.  (I couldn't find it in the faqs either.)
> > 
> > I also couldn't find this feature in the short list of new mailman 2.1
> > features.  Is something like that planned for 2.1?