Just take a dump of the database and move to other one, almost everything is stored in database. Outside of database, if you need to move log files and currently pending emails in shunt or held queue (broken or pending emails), you need to move the 'var' directory of Core and it's configuration.
If you are using docker installation, database container holds the database and '/opt/mailman/core/var' is what you are looking for.
Thanks, Abhilash Raj (Apologies for top post)
On October 18, 2017 1:29:58 PM PDT, Dmitry Makovey <dmakovey@stanford.edu> wrote:
On 10/18/2017 11:10 AM, Mark Sapiro wrote:
On 10/18/2017 08:56 AM, Dmitry Makovey wrote:
Hi,
I am drawing a blank looking for documentation for mailman3 migrations. How can one dump existing settings for mailman and import it into another instance?
The Mailman 3 command 'mailman import21' is what does this
however there are issues in that not all 2.1 settings are imported at all or correctly and in at least one case on an announce only list,
membership wasn't imported.
I intend to work on this, but haven't got as far as even documenting
<http://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/import.htm...>, the the
problems, much less coming up with fixes.
isn't above more about MM2 -> MM3 moves? I can't file .pck files for MM3 setup thus assuming there are some other files/commands I need to tackle to move MM3 from host to host.
-- Sr System and DevOps Engineer SoM IRT
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.