FAQ
Dear list,

I am faced with the situation of forking a list of several hundred
subscribers in such a way that the result is two lists with exactly
the same subscriber set, but with different settings.

I am aware of list_members and sync_members, but that will not
migrate nomail and digest users properly.

I have also searched the web and the FAQ and found a bit of a hint
here and there, but no solution to the problem.

I have seen the mailman-subscribers.py scripts, and cannot get it
working (possibly my fault, still trying), but even if I did,
sync_members cannot import nomail subscribers (or user passwords),
so it would not really help to have a dump.

Is anyone aware of a method to port subscriber sets from one list to
another, without copying the settings?

Or should I just duplicate the list
(/var/lib/mailman/{archives,lists}) and then proceed to reconfigure
the new one? In that case, does it matter that the old one will be
on a 2.1.5 instance while the new one is 2.1.9?

Thanks for any comments.

--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net at madduck

"i am a deeply superficial person."
-- andy warhol

spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url : http://mail.python.org/pipermail/mailman-users/attachments/20070828/d2340f25/attachment.pgp

Search Discussions

  • Mark Sapiro at Aug 29, 2007 at 12:49 am

    martin f krafft wrote:
    I am faced with the situation of forking a list of several hundred
    subscribers in such a way that the result is two lists with exactly
    the same subscriber set, but with different settings. <snip>
    Or should I just duplicate the list
    (/var/lib/mailman/{archives,lists}) and then proceed to reconfigure
    the new one? In that case, does it matter that the old one will be
    on a 2.1.5 instance while the new one is 2.1.9?

    Unless you want to write your own Python script to populate the new
    list from the old, I think duplication is your easiest choice. Here's
    an outline of what I suggest you can do.

    1) Create the new list on the 2.1.9 installation. This step is not
    necessary, but it simplifies archive considerations. Do not configure
    anything on the new list until after step 2.

    2) remove the lists/newlistname/config.pck and
    lists/newlistname/config.pck.last files from the 2.1.9 server and then
    copy the lists/oldlistname/config.pck from the 2.1.5 server to
    lists/newlistname/config.pck on the 2.1.9 server.

    3) Now configure the new list. It will have all the old list's
    membership with member options and all the old list settings including
    things like real_name and subject_prefix which you will probably want
    to change (real_name will initially be 'oldlistname' except for case -
    you will only be able to change it to 'newlistname' except for case).

    4) You will probably need to run fix_url on the new list assuming the
    host names are different.

    The first time the list is accessed after copying the old config.pck,
    Mailman will upgrade the config.pck automatically and you will then
    have a 2.1.9 format config.pck and config.pck.last.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Martin f krafft at Aug 29, 2007 at 3:26 pm

    also sprach Mark Sapiro [2007.08.29.0249 +0200]:
    Unless you want to write your own Python script to populate the new
    list from the old, I think duplication is your easiest choice. Here's
    an outline of what I suggest you can do.
    This sounds like sound advice. Thanks, Mark.

    --
    martin; (greetings from the heart of the sun.)
    \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net at madduck

    "my father, a good man, told me:
    'never lose your ignorance; you cannot replace it.'"
    -- erich maria remarque

    spamtraps: madduck.bogus at madduck.net
    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: not available
    Type: application/pgp-signature
    Size: 189 bytes
    Desc: Digital signature (see http://martin-krafft.net/gpg/)
    Url : http://mail.python.org/pipermail/mailman-users/attachments/20070829/0acbfca5/attachment.pgp

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedAug 28, '07 at 1:23p
activeAug 29, '07 at 3:26p
posts3
users2
websitelist.org

2 users in discussion

Martin f krafft: 2 posts Mark Sapiro: 1 post

People

Translate

site design / logo © 2022 Grokbase