Re: [Mailman-Users] dumping a large list to a file

2003-01-22 Thread Matt Brown
On Wed, 2003-01-22 at 21:40, Jon Carnes wrote: > Another alternative is to move on up to version 2.1 and then to move all > your configurations/email addresses into an SQL database. Anyone have any pointers on where to start with this? I'd like to be able to store list info in an SQL (MySQL) datab

Re: [Mailman-Users] dumping a large list to a file

2003-01-22 Thread Dan Mick
Scott R. Every wrote: has anyone figured out a way to get just the good email addresses out of the mailman db? bin/list_members -h . . . --nomail[=why] / -n [why] Print the members that have delivery disabled. Optional argument can be "byadmin", "byuser", "bybounce", or

Re: [Mailman-Users] dumping a large list to a file

2003-01-22 Thread Jon Carnes
This question comes up fairly regularly, so I wouldn't be surprised if its covered in the FAQ. When your lists get really big and it takes forever to do any maintenance to the config.db then you should look at using a RAM disk. You can either set aside working RAM for use as a disk or purchase a

[Mailman-Users] dumping a large list to a file

2003-01-22 Thread Scott R. Every
I have a list with upwards of 600K emails on it. Many of the addresses on the list have the nomail bit set, yet when I use 'list_members' there seems to be no way to get only the valid emails(ie no nomail emails listed) I have a customer who needs to split this list into X number of pieces in