On 6/2/24 4:28 PM, Keith Christian wrote:

  1 Soon, I will be executing the first test imports from

Mailman2.1 to Mailman3.9.

  2 Planning to copy over the entire production Mailman2.1 to a new

directory structure on the Mailman 3.9 machine.

  3 Expecting that all .mbox and .pkl files will be present and no

special work has to be done to bring them over will a "full" mailman2.1 copy.

That's correct.

  4 Can the import21 program find the mailman2.1 .mbox and .pkl

files on its own and process them?

No. mailman import21 needs to be given the path to the config.pck to import and hyperkitty_import needs to be given the path to the .mbox.

  5 Other than the mailman2.1 instance being shut down, any other

prep that needs to be done?

Ideally there are no held messages or other moderator requests for the MM 2.1 list, i.e. deal with these before shutting down the list.

If there is a MM 2.1 digest.mbox it needs to be moved and converted for MM 3

I have attached a bash script I use on mail.python.org to migrate lists. Paths and some other things are specific to that installation, but you may find it useful. It calls a move_digest script which I've also attached

  6 Any special command line parameters to be aware of for import21?

Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE

Import Mailman 2.1 list data.  Requires the fully-qualified name of 

the list to import and the path to the Mailman 2.1 pickle file.

Options: -c, --charset TEXT Specify the encoding of strings in PICKLE_FILE if not utf-8 or a subset thereof. This will normally be the Mailman 2.1 charset of the list's preferred_language. -h, --help Show this message and exit.

  7 Is there a list of troubleshooting steps for commonly

encountered migration issues?

Not that I'm aware of.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan