[Mailman-Users] Re: Mailman3 list migration possibly new domain

[Andrew Hodgson]

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 l...@domain1.com, if I import 
>> that into a new Mailman3 list l...@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. 
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Mailman3 list migration possibly new domain

[Barry S. Finkel]

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 l...@domain1.com, if I import that 
into a new Mailman3 list l...@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
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Mailman3 list migration possibly new domain

[Mark Sapiro]

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 

However, this is currently a low level operation that has to be done via
`mailman shell` or external modification of Mailman's database. See
 and
.

Likewise you can change the name, e.g. l...@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 The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/