Re: [Mailman-Developers] Exporting member info (including options)

On Aug 12, 2010, at 02:00 PM, Aaron Kreider wrote: >Is there a good way to export all of the member info for a list? Mailman 3 has two related, but incomplete approaches that might provide some useful examples. There is an "export" command that dumps the various configurations to an XML format f

Re: [Mailman-Developers] Exporting member info (including options)

Aaron Kreider wrote: >This worked. Now I get a JSON error: > >File "pickle2json.py", line 21, in ? > open(opts.json_data_path, 'w').write(json.dumps(unpickled_data)) > File "build/bdist.linux-x86_64/egg/simplejson/__init__.py", line 261, >in dumps > File "build/bdist.linux-x86_64/egg/sim

Re: [Mailman-Developers] Exporting member info (including options)

On 8/17/2010 7:12 PM, Mark Sapiro wrote: There are at least three ways around this. run your script from Mailman's bin/ directory and 'import paths' at the beginning of the script, or This worked. Now I get a JSON error: File "pickle2json.py", line 21, in ? open(opts.json_data_path, 'w')

Re: [Mailman-Developers] Exporting member info (including options)

Aaron Kreider wrote: > When I tried to depickle a list, I got an "Import Error No Module >named Mailman.Bouncer". > >I suspect this is for a list that has bounces. I was able to depickle a >much smaller list. Yes, the issue only occurs for lists with members that have bounce_info. There are

Re: [Mailman-Developers] Exporting member info (including options)

Aaron Kreider wrote: > >This is very strange - why are there fields in the mysql table that >aren't in use? >hide, nomail, ack, not_metoo, and plain > >I'm guessing they were either deprecated or the programmer planned to >use them in the future. They were not deprecated in the sense of having

Re: [Mailman-Developers] Exporting member info (including options)

When I tried to depickle a list, I got an "Import Error No Module named Mailman.Bouncer". I suspect this is for a list that has bounces. I was able to depickle a much smaller list. Could it be a users permission issue? I tried running the script as root, but it still gave me the error. I'm

Re: [Mailman-Developers] Exporting member info (including options)

Examination of (is that what you're using?) shows that it stores and uses user_options in the same way as OldStyleMermberships.py. hide, ack, not_metoo and plain are defined fields in the MySQL database table

Re: [Mailman-Developers] Exporting member info (including options)

Aaron Kreider wrote; > I'm figuring out where to get the information from the config.pck >(pickle file) for each list to populate the MySQL table. > >It seems like the MySQL format is extracting some of its fields from the >user_options fields, is this true? user_options is used by OldStyleMe

Re: [Mailman-Developers] Exporting member info (including options)

I'm figuring out where to get the information from the config.pck (pickle file) for each list to populate the MySQL table. It seems like the MySQL format is extracting some of its fields from the user_options fields, is this true? If this is true, it is confusing because several of the user_op

Re: [Mailman-Developers] Exporting member info (including options)

Bob Puff wrote: > >I thought when you kicked in the mysql adaptor, it populated the mysql table >with all that data... you're saying it doesn't, and you have to start from >scratch? If you start a new list with any of the MysqlMemberships.py adaptors that I have seen, it creates the necessary dat

Re: [Mailman-Developers] Exporting member info (including options)

> Aaron Kreider wrote: > > > Is there a good way to export all of the member info for a list? > > > >I want all the mailing list options as well as the email address, so > >that I can import it into MySQL and use the MySQL adaptor. > > There is a script at >

Re: [Mailman-Developers] Exporting member info (including options)

Aaron Kreider wrote: > Is there a good way to export all of the member info for a list? > >I want all the mailing list options as well as the email address, so >that I can import it into MySQL and use the MySQL adaptor. There is a script at

[Mailman-Developers] Exporting member info (including options)

Is there a good way to export all of the member info for a list? I want all the mailing list options as well as the email address, so that I can import it into MySQL and use the MySQL adaptor. I know "list_members" gives just the email addresses. Is the best method for me to use dbdump to ac