Thanks and it is now working. Regarding migration I have tried importing the config pickle of mailman 2 in mailman 3 and we are able to get the list and member settings.
Also I have observed that we can import config pickle of a list only once in mailman 3. I mean if I make changes in the new list in mm3 and then I try again import21 the settings are remaining same as changed but not reverting to as mm2. Also if there are any pending requests in MM2 we cannot import them. Correct me if I am wrong. So as of now this the only way we can achieve the migration..?? By importing each and every list config file..?? Regards Sandeep Sent from my iPhone > On 15-Aug-2019, at 10:53 AM, Abhilash Raj <maxk...@asynchronous.in> wrote: > > > >> On Wed, Aug 14, 2019, at 10:28 AM, Abhilash Raj wrote: >> >> >>> On Wed, Aug 14, 2019, at 10:08 AM, Stephen J. Turnbull wrote: >>> sandeep kumar writes: >>> >>>> Now that we are ready to go into production. We are currently >>>> running mailman 2 in our production. Now the biggest challenge is >>>> we have to migrate around 3000 lists from mailman 2 to mailman 3. >>>> Is there any documentation >>> >>> There's a small amount, but we're not satisfied with it. We have an >>> on-going Season of Docs project to create migration documentation. >>> >>>> or any inputs from the team would be appreciated and will be very >>>> helpful. >>> >>> Abhilash and Mark have substantial experience with migrating lists, >>> and operating Mailman 2 in parallel with Mailman 3 (ie, gradual >>> migration, not the same list on both servers!) However, they've been >>> doing this at scale of dozens of lists, maybe a dozen at a time. >> >> >> I've also been (very slowly) working on automating the workflow for >> migration to a level that it requires minimal user intervention. This >> hasn't been tested or completed yet[1]. >> >> It is mostly complete, but if you can help complete it, it should >> be a bit nicer than manually porting every list (i.e. multiple-commands per >> list right now) vs single command with exception handling to keep >> working till it reaches end. For 3k lists, it might be useful :) >> >> >> [1]:https://gitlab.com/mailman/mailman/merge_requests/531 >> >>> >>> I hope that some of our really large-scale users will have something >>> to say, but the cases I'm aware of are at your stage more or less -- >>> no post-mortems yet that I know of. >>> >>>> Iam trying to access docs.mailman3.org but it is not opening don't >>>> why.? >>> >>> It appears that recent Firefox is very picky about the TLS versions it >>> will connect to, and somehow mailman3.org doesn't support that. >>> Abhilash? >> >> DNS records need updating, I'm gonna poke at Barry. > > It should now be working! > >> >>> >>> In the meantime, try other browsers which may not be so picky about >>> crypto algorithms. Also you can try mailman.readthedocs.io. >>> >>> Steve >>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> > > -- > thanks, > Abhilash Raj (maxking) _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
