Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)
Hello,
I already have some success in auto-migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm), using a new container (not upgrading the existing installation, which is obsolete e.g. 32 bit x86). I am doing this using custom scripts. The idea being to be able to import most of the existing configuration and archives, let the list administrators test the new system, and progressively advertise this to users. Then, the old container will be disabled.
The basic stuff works (From: domain is OK, HTTP transport works, mail go out, etc)
I however bumped into the following problem:
How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer?
Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR.
Thank you for any input.
On Sat, May 25, 2024 at 5:05 PM <schaefer@alphanet.ch> wrote:
Hello,
I already have some success in auto-migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm), using a new container (not upgrading the existing installation, which is obsolete e.g. 32 bit x86). I am doing this using custom scripts. The idea being to be able to import most of the existing configuration and archives, let the list administrators test the new system, and progressively advertise this to users. Then, the old container will be disabled.
The basic stuff works (From: domain is OK, HTTP transport works, mail go out, etc)
lsnip]
Also, I have a question: if I import my 2.1 config for each ml, will DKIM
work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR.
I remember that when I imported my 2.1 configs to MM3, the DKIM workarounds just worked.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 5/25/24 10:00 AM, schaefer@alphanet.ch wrote:
How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer?
The host name displayed in the web UI is based on the SITE_ID setting in Django's settings. This is a system configuration not associated with any lists. it references an entry in the django_sites table in the database.
As far as the comment/display name in From: is concerned, what specific
emails are you talking about? I don't know where example.com would
come from unless you mean email from Django in which case look at your
setting for ADMINS in your Django settings.
Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR.
The mailman import21 command will properly import the Mailman 2.1
from_is_list and Sender filters -> dmarc_* DMARC mitigation settings.
If you have some customization in this area, that probably won't be handled.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hello,
On Sat, May 25, 2024 at 11:38:40AM -0400, Mark Sapiro wrote:
The host name displayed in the web UI is based on the SITE_ID setting in Django's settings. This is a system configuration not associated with any lists. it references an entry in the django_sites table in the database.
Thank you, will look into this.
As far as the comment/display name in From: is concerned, what specific emails are you talking about?
This. Sorry, I mixed From: with Subject: and the content:
Date: Sat, 25 May 2024 13:37:29 -0000 From: postorius@lists2.alphanet.ch To: schaefer@XXX Subject: [example.com] Please Confirm Your E-mail Address
Hello from example.com!
You're receiving this e-mail because user Schaefer-XXX has given your e-mail +address to register an account on example.com.
To confirm this is correct, go to [ ... ]
Thank you for using example.com! example.com
I guess it's the same SITE_ID setting in Django's DB:
$ grep SITE_ID /usr/share/mailman3-web/settings.py
SITE_ID = 1
However, I guess it's the default creation, by the Debian package, of the SQLite local database which presumably was done with example.com.
I will anyway switch to a remote PostgreSQL database, and thus create a new one with the correct names. That should fix it.
for ADMINS in your Django settings.
ADMINS = ( ('Mailman Suite Admin', 'schaefer@alphanet.ch'), )
That looks correct.
The
mailman import21command will properly import the Mailman 2.1 from_is_list and Sender filters -> dmarc_* DMARC mitigation settings.
Thank you. Aka mailman-wrapper import21 on Debian so to switch to the correct user.
If you have some customization in this area, that probably won't be handled.
Obviously.
On 5/25/24 11:49 AM, Marc SCHAEFER wrote:
This. Sorry, I mixed From: with Subject: and the content:
Date: Sat, 25 May 2024 13:37:29 -0000 From: postorius@lists2.alphanet.ch To: schaefer@XXX Subject: [example.com] Please Confirm Your E-mail Address Hello from example.com! You're receiving this e-mail because user Schaefer-XXX has given your e-mail +address to register an account on example.com. To confirm this is correct, go to [ ... ] Thank you for using example.com! example.comI guess it's the same SITE_ID setting in Django's DB:
Yes, that's what it is.
-- 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 2024-05-25 08:38:
The host name displayed in the web UI is based on the SITE_ID setting in Django's settings. This is a system configuration not associated with any lists. it references an entry in the django_sites table in the database.
Specifically, the mailmanweb DB, table django_site.
In this case, I found the GUI to be easier:
https://$your_domain/admin/sites/site/
rb
participants (5)
-
Marc SCHAEFER -
Mark Sapiro -
Odhiambo Washington -
Ron / BCLUG -
schaefer＠alphanet.ch