A few years ago, we switched from ListProc to Mailman. We didn't have as extensive a set of lists as do you however.
Remember that communications with the list owners is extremely important.
What we did was: 0. Have a firm timeframe to complete the change over. lists are going to be named the same, simple create a list in Mailman
- Try to weed out as many lists as you can that may not be used anymore.
- Set up Mailman in parallel with ListProc.
- Create new lists in Mailman to replace the lists in ListProc (we changed our naming convention so there wasn't a 1 to 1 move). If your
for each list to be moved from ListProc. 4. List owners of the Mailman lists should be the same as ListProc lists. 5. Communicate with the list owners of the ListProc lists and let them know how to access and configure the list on Mailman. 6. Give list owners time to make their changes (e.g. add moderators, set moderation, etc.) and test the list. 7. After list owner testing, populate the list (or have the list owner do it) membership. 8. Communicate with the list owners for a cutover time (either individually or all at once) to do any file conversions like archives, etc. 9. Monitor the process carefully. 10. Remember that firm timeframe, well some list owners are still going to miss it. Be prepared.
Overall, the process went very smoothly for us. We did not convert the archives. We did change how we populated several of our lists though which was a bit of a challange (we went from populating via a static mechanism once per year to dynamic LDAP populating).
Chris
On 3/2/2015 7:24 AM, Bill.Costa@unh.edu wrote:
I'm going to be migrating about 400 lists with 25K subscribers from ListProc to Mailman. I'm looking for whatever tools I can find to aid in the conversion process. Of particular concern is the creation of the replacement list in Mailman with a reasonable mapping of the ListProc settings into equivalent Mailman features, and of course the conversion of the subscribers. Archive conversion would be nice too, but is a much lower priority.
In my searching so far I've found a few bits and pieces, but nothing comprehensive. So before I get out the hammer and saw, I just want to make sure I'm not missing a good resource for doing this.
...BC