extracting a lists's setting to move the list to a new domain
Hi,
I cant find anything on extracting a list's settings, owners etc and then using those to create a new list on a new domain.
Is there a simple operational command to extract and inject?
regards
Steven
On 9/20/20 4:35 PM, Steven Jones wrote:
I cant find anything on extracting a list's settings, owners etc and then using those to create a new list on a new domain.
Is there a simple operational command to extract and inject?
Do you have root or admin access to the server? There are tools in the bin directory that allows for such functions via the command line. You can retrieve your list roster using the who command via email. Also the list/listname/config.pck has all that information but again you need to have root access to the server to retrieve that. Here are some directions to use the WHO command:
Send an e-mail to listname-request@yourlistdomain.com. (Replace the listname and your listdomain.com with your own list specific information)
In the subject line, type “who password”. Do not add the quotes, and substitute ‘password’ with your list administrator or moderator password.
The mailman server will reply to the who command with a break down of your membership roster between regular (non-digest members) members and digest members. It will even include their full name if it was added previously to the roster.
-- Brian Carpenter Harmonylists.com Emwd.com
On 9/20/20 1:42 PM, Brian Carpenter wrote:
On 9/20/20 4:35 PM, Steven Jones wrote:
I cant find anything on extracting a list's settings, owners etc and then using those to create a new list on a new domain.
Is there a simple operational command to extract and inject?
The tool for this is mailman's bin/config_list which can both esport and import list configuration but not list membership.
Do you have root or admin access to the server? There are tools in the bin directory that allows for such functions via the command line. You can retrieve your list roster using the who command via email. Also the list/listname/config.pck has all that information but again you need to have root access to the server to retrieve that. Here are some directions to use the WHO command:
As Brian notes, the email who
command can be ysed to extract list
membership as can the command line bin/list_members, and either of these
lists can be used as input to bin/add_members or the admin Mass
Subscribe function, but these operations do not preserve user options,
passwords, etc.
The one single way to move everything is to obtain a copy of Mailman's lists/<listname>/config.pck file and move it, and maybe also get the lists archives/private/<listname>.mbox/<listname>.mbox file and use it to rebuild the archive.
See <https://wiki.list.org/x/4030682> for more info.
All the above assumes the new domain is on a different server. If it is just a different virtual domain on the same server, see <https://wiki.list.org/x/4030617>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
As a lowly list admin with a number of cPanel-hosted Mailman2 lists, I cannot avail myself of such tools without opening a ticket with my ISP. While they have been very responsive in the past, I don't feel that's a generosity of which I should frequently avail myself. Also, I wanted to have a backup from which I could recreate any list, as well as a tracking process for all changes I make.
So I wrote two Rexx program, one to extract the membership information, including all the admin settings available via the web interface. The other program extracts almost all of the list configuration settings/values accessible via the admin web interface. ("Almost all" because some screens have never changed from their defaults, and I haven't gotten around to including them.)
All they require is the Regina interpreter and the REXX/CURL function library (libcurl), both GPL'd offerings, if anyone is at all interested.
-Chip-
On 9/20/2020 6:38 PM, Mark Sapiro wrote:
On 9/20/20 1:42 PM, Brian Carpenter wrote:
On 9/20/20 4:35 PM, Steven Jones wrote:
I cant find anything on extracting a list's settings, owners etc and then using those to create a new list on a new domain.
Is there a simple operational command to extract and inject?
The tool for this is mailman's bin/config_list which can both esport and import list configuration but not list membership.
Do you have root or admin access to the server? There are tools in the bin directory that allows for such functions via the command line. You can retrieve your list roster using the who command via email. Also the list/listname/config.pck has all that information but again you need to have root access to the server to retrieve that. Here are some directions to use the WHO command:
As Brian notes, the email
who
command can be ysed to extract list membership as can the command line bin/list_members, and either of these lists can be used as input to bin/add_members or the admin Mass Subscribe function, but these operations do not preserve user options, passwords, etc.The one single way to move everything is to obtain a copy of Mailman's lists/<listname>/config.pck file and move it, and maybe also get the lists archives/private/<listname>.mbox/<listname>.mbox file and use it to rebuild the archive.
See <https://wiki.list.org/x/4030682> for more info.
All the above assumes the new domain is on a different server. If it is just a different virtual domain on the same server, see <https://wiki.list.org/x/4030617>.
On 9/20/20 5:22 PM, Chip Davis wrote:
So I wrote two Rexx program, one to extract the membership information, including all the admin settings available via the web interface.
I neglected to mention the scripts at <https://www.msapiro.net/scripts/mailman-subscribers.py> and <https://www.msapiro.net/scripts/mailman-subscribers3.py> (mirrored at <https://fog.ccsf.edu/~msapiro/scripts/mailman-subscribers.py and https://fog.ccsf.edu/~msapiro/scripts/mailman-subscribers3.py).
These script can screen scrape the web admin membership list to obtain, among other options, a csv file of members and their options. They are the same except mailman-subscribers3.py is a python 3 script and mailman-subscribers.py is python 2.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks
regards
Steven
From: Mark Sapiro <mark@msapiro.net> Sent: Monday, 21 September 2020 10:38 AM To: mailman-users@python.org <mailman-users@python.org> Subject: [Mailman-Users] Re: extracting a lists's setting to move the list to a new domain
On 9/20/20 1:42 PM, Brian Carpenter wrote:
On 9/20/20 4:35 PM, Steven Jones wrote:
I cant find anything on extracting a list's settings, owners etc and then using those to create a new list on a new domain.
Is there a simple operational command to extract and inject?
The tool for this is mailman's bin/config_list which can both esport and import list configuration but not list membership.
Do you have root or admin access to the server? There are tools in the bin directory that allows for such functions via the command line. You can retrieve your list roster using the who command via email. Also the list/listname/config.pck has all that information but again you need to have root access to the server to retrieve that. Here are some directions to use the WHO command:
As Brian notes, the email who
command can be ysed to extract list
membership as can the command line bin/list_members, and either of these
lists can be used as input to bin/add_members or the admin Mass
Subscribe function, but these operations do not preserve user options,
passwords, etc.
The one single way to move everything is to obtain a copy of Mailman's lists/<listname>/config.pck file and move it, and maybe also get the lists archives/private/<listname>.mbox/<listname>.mbox file and use it to rebuild the archive.
All the above assumes the new domain is on a different server. If it is just a different virtual domain on the same server, see <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.list.org%2Fx%2F4030617&data=02%7C01%7Csteven.jones%40vuw.ac.nz%7C75293fc02bd3424b75ce08d85db604a6%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C637362383683015426&sdata=wWY3UdGgl6lZd5dV%2FZjI%2FDu5G2OJX4HBzGQ8rZBJfWo%3D&reserved=0>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.pytho... Mailman FAQ: https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.list.o... Security Policy: https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.list.o... Searchable Archives: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mail-a... https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.pytho...
On 09/20/2020 8:35 PM Steven Jones <steven.jones@vuw.ac.nz> wrote: I cant find anything on extracting a list's settings, owners etc and then using those to create a new list on a new domain.
Is there a simple operational command to extract and inject?
If you have privileged access you can run the following commands on your server to retrieve everything. Your file paths might be different so you'll need to adjust accordingly.
$ cd ~/ $ sudo -s $ mkdir LISTNAME-files $ cd LISTNAME-files $ /usr/lib/mailman/bin/list_members -f -r LISTNAME > LISTNAME.regular $ /usr/lib/mailman/bin/list_members -f -d LISTNAME > LISTNAME.digest $ cp /var/lib/mailman/archives/private/LISTNAME.mbox/LISTNAME.mbox ./LISTNAME.mbox $ tar -czvf LISTNAME.attachments.tgz /var/lib/mailman/archives/private/LISTNAME/attachment $ cp /var/lib/mailman/lists/LISTNAME/config.pck ./LISTNAME.pck $ cd ../ $ tar -czvf LISTNAME-files.tgz LISTNAME-files
Copy LISTNAME-files.tgz to anywhere on the new server and unpack. Create the new list.
Then for the new list, copy the config.pck into place, and also the ".mbox" and archive attachments.
Fix the URLs with: bin/withlist -l -r fix_url LISTAME -u DOMAINNAME
The lists settings and subscribers are in the config.pck so you shouldn't need to do any more.
/Mark
participants (5)
-
Brian Carpenter
-
Chip Davis
-
Mark Dale
-
Mark Sapiro
-
Steven Jones