Mailman3 list migration possibly new domain
Hi,
I have a list to migrate to Mailman3 from Mailman2 but the domain of the list may change at some point in the future. I was hoping to marry up the 2 events but its not looking likely at the moment.
From what I have tested the Hyperkitty archives can be imported into any list so long as it exists. My question relates to importing the Mailman configuration files.
If we take a Mailman configuration file for list@domain1.com<mailto:list@domain1.com>, if I import that into a new Mailman3 list list@domain2.com<mailto:list@domain2.com> will it cause a problem? Taking that a step further could we import list@domain1.com<mailto:list@domain1.com> into list2@domain2.com<mailto:list2@domain2.com>?
I am aware I could just export the users and re-import into a new list if all else fails.
Suggestions welcome. Thanks. Andrew.
On 5/30/20 1:41 PM, Andrew Hodgson wrote:
Hi,
I have a list to migrate to Mailman3 from Mailman2 but the domain of the list may change at some point in the future. I was hoping to marry up the 2 events but its not looking likely at the moment.
From what I have tested the Hyperkitty archives can be imported into any list so long as it exists. My question relates to importing the Mailman configuration files.
If we take a Mailman configuration file for list@domain1.com, if I import that into a new Mailman3 list list@domain2.com will it cause a problem?
No problem. The Mailman 2.1 list doesn't have domain information anyway.
Taking that a step further could we import list@domain1.com into list2@domain2.com?
That works too. I have done this on mail.python.org. On mpo, I also do things like setting a virtual mapping in the MTA from 2.1name@python.org to 3name@python.org and adding 2.1name@python.org to acceptable_aliases of the 3name@python.org list, but you may not be concerned about posts to the old address.
After import you may want to edit the list's Display name and Subject prefix because they will be imported and reflect the list@domain1.com values.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
On 5/30/20 1:41 PM, Andrew Hodgson wrote:
Hi,
I have a list to migrate to Mailman3 from Mailman2 but the domain of the list may change at some point in the future. I was hoping to marry up the 2 events but its not looking likely at the moment.
From what I have tested the Hyperkitty archives can be imported into any list so long as it exists. My question relates to importing the Mailman configuration files.
If we take a Mailman configuration file for list@domain1.com, if I import that into a new Mailman3 list list@domain2.com will it cause a problem?
No problem. The Mailman 2.1 list doesn't have domain information anyway.
Thanks for this. Once converted to Mailman3 can I move a list to another domain on the same Mailman instance or change the list name? Ideally I would do the switch when moving to Mailman3 but I don't know when the domain migration will happen and really want to close off moving these lists.
Thanks. Andrew.
On 5/31/2020 6:55 AM, Andrew Hodgson wrote:
Mark Sapiro wrote:
On 5/30/20 1:41 PM, Andrew Hodgson wrote:
Hi,
I have a list to migrate to Mailman3 from Mailman2 but the domain of the list may change at some point in the future. I was hoping to marry up the 2 events but its not looking likely at the moment.
From what I have tested the Hyperkitty archives can be imported into any list so long as it exists. My question relates to importing the Mailman configuration files.
If we take a Mailman configuration file for list@domain1.com, if I import that into a new Mailman3 list list@domain2.com will it cause a problem?
No problem. The Mailman 2.1 list doesn't have domain information anyway.
Thanks for this. Once converted to Mailman3 can I move a list to another domain on the same Mailman instance or change the list name? Ideally I would do the switch when moving to Mailman3 but I don't know when the domain migration will happen and really want to close off moving these lists.
Thanks. Andrew.
I would never make two big changes at one time (for some definition of "big"). When I was a systems programmer on an IBM mainframe, one day we made two big changes at once. And a strange thing happened. It took a number of persons adding traces to the code to determine what was happening. And I looked at both pieces of code, ran successful-branch traces, and still was unable to determine exactly what had changed in each piece of the operating system to cause the problem. By that time, of course, we had modified the software to get around the problem.
I would consider changing a domain AND migrating Mailman to be two "big" changes that should not occur at the same time.
--Barry Finkel
On 5/31/20 4:55 AM, Andrew Hodgson wrote:
Thanks for this. Once converted to Mailman3 can I move a list to another domain on the same Mailman instance or change the list name? Ideally I would do the switch when moving to Mailman3 but I don't know when the domain migration will happen and really want to close off moving these lists.
You can change the list_name and/or mail_host, i.e., the name and/or domain in the list posting and other addresses, but you can't change the list_id - see section 4. at <https://www.rfc-editor.org/rfc/rfc2919.html>
However, this is currently a low level operation that has to be done via
mailman shell or external modification of Mailman's database. See
<https://gitlab.com/mailman/mailman/-/issues/156> and
<https://gitlab.com/mailman/mailman/-/issues/428>.
Likewise you can change the name, e.g. list@example.com, and
display_name, e.g. List, but not the list_id, e.g. list.example.com, in
HyperKitty, but again this is currently a low level operation that has
to be done via django-admin shell or external modification of Django's
database.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Andrew Hodgson -
Barry S. Finkel -
Mark Sapiro