- Mailman-users - lists.mailman3.org

MM3.3 ignores
by Axel Rau Nov. 8, 2022

Nov. 8, 2022

Hi all, mm 3.3.5 started to complain: - - - File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 142, in load self.push(filename, user_config.read()) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 148, in push self._post_process() File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 160, in _post_process self.ensure_directories_exist() File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 253, in ensure_directories_exist makedirs(directory) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/utilities/filesystem.py", line 69, in makedirs os.makedirs(path, mode) File "/usr/local/py_venv/mailman_33/lib/python3.9/os.py", line 225, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: '//var/templates‘ - - - part from mailman.cfg: - - - [paths.dev] var_dir: $cfg_file/../.. [paths.here] var_dir: $cwd/var [paths.fhs] bin_dir: /usr/local/bin var_dir: /var/lib/mailman queue_dir: /var/spool/mailman log_dir: /var/log/mailman lock_dir: /var/spool/lock/mailman etc_dir: /usr/local/etc ext_dir: /usr/local/etc/mailman.d pid_file: /var/run/mailman/master.pid [paths.home] var_dir: /usr/local/mailman3 - - - var subdirectory: - - - (mailman_33) [root@lists5 /usr/local/py_venv/mailman_33]# ls -l /usr/local/mailman3/var/ total 62 drwxr-xr-x 3 mailman mailman 3 18 Jan. 2022 archives drwxr-xr-x 2 mailman mailman 2 18 Jan. 2022 cache drwxr-xr-x 2 mailman mailman 2 18 Jan. 2022 data drwxrwx--- 2 mailman mailman 4 2 Feb. 2022 etc drwxr-xr-x 6 mailman mailman 6 19 Jan. 2022 lists drwxr-xr-x 2 mailman mailman 2 5 Nov. 17:48 locks drwxr-xr-x 2 mailman mailman 7 18 Jan. 2022 logs drwxr-xr-x 155 mailman mailman 155 24 Okt. 09:09 messages drwxr-xr-x 3 root mailman 3 14 Juni 17:57 old_templates drwxr-xr-x 14 mailman mailman 14 18 Jan. 2022 queue drwxr-xr-x 3 mailman mailman 3 18 Jan. 2022 templates # ls -ld /usr/local/mailman3 drwxr-xr-x 11 mailman mailman 24 24 März 2022 /usr/local/mailman3 - - - I’m confused with the layout (and I dont like var stuff not in var). I have no layout set. Why does it not see /usr/local/mailman3/var/templates ? Any help apprecaiated Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

5 5

Imported archives MM2 to MM3
by Mark Dale Nov. 4, 2022

Nov. 4, 2022

Hi I've just migrated a list from MM 2.1.39 to MM 3.3 (Debian). Following the guide at: https://docs.mailman3.org/en/latest/migration.html Importing the config went fine and all is well with that. The import of the archive appeared to go well (notes below) as did the rebuilding of the index. However, the archives show up empty on the list's webpage. I don't know what I should be looking for to fix this, so any pointers would be great. Thanks. //////////////////////////////////////// Migrate the list archives ========================= # python3 /usr/share/mailman3-web/manage.py hyperkitty_import -l LISTNAME@DOMAIN ./LISTNAME.mbox Importing from mbox file ./LISTNAME.mbox to LISTNAME@DOMAIN Computing thread structure Synchronizing properties with Mailman 33 emails left to refresh, checked 0 Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list leden(a)vereniging.tropischebossen.nl'. //////////////////////////////////////// Rebuild the index: ======================== # python3 /usr/share/mailman3-web/manage.py update_index_one_list LISTNAME@DOMAIN Indexing 646 emails

1 1

Re: No DBA password when installing Mailman3 with remote database server
by Markus Ludwig Grandpré Nov. 4, 2022

Nov. 4, 2022

Dear Mr. Turnbull, dear blackout69, thank you very much for your answers. Below this text you will find a brief documentation how I finally managed to install mailman3 and mailman3web packages under Debian 11 with a remote PostGreSQL server v10.22. Maybe there is a more elegant way to install both packages correctly, but AFAIK any solution will be only a workaround for the main problem, that the DBA's password is usually unknown during the whole installation process if you use a remote database server that is run by another staff team. Best regards, Markus ------------ 8< ------------ Mailman3 installation ===================== 1. Installation mailman3 2. Installation mailman3web 3. Integration in boot sequence 1. Installation mailman3 ------------------------ Once the remote database server has been set up with databases mailman3 and mailman3web and with a database user mailman3 that has access to both databases, create database mailman3; create database mailman3web; create user mailman3 with encrypted password 'streng_geheim'; grant all privileges on database mailman3 to mailman3; grant all privileges on database mailman3web to mailman3; the package mailman3 can be installed: # apt install mailman3 To avoid the DBA password prompt that ususally cannot be answered if the database server is run by another team, the installation tool dbconfig-common should be omitted: * Configure database for mailman3 with dbconfig-common? No The mailman3 package will be installed without errors. The configuration of the database connection can be done in file /etc/mailman3/mailman.cfg: ... class: mailman.database.postgresql.PostgreSQLDatabase ... url: postgres://mailman3:<secret>@<host>:<port>/mailman3 At this point the required tables have not yet been created in the database. Therefore, the mailman3 package should be configured again: # dpkg-reconfigure mailman3 Because the database mailman3 already exists on the database server, it does not need to be recreated using dbconfig-common: * Reinstall database for mailman3? No * Add the HyperKitty configuration to mailman.cfg? No Also moving the HyperKitty configuration to /etc/mailman3/mailman.cfg is not necessary at this time. After dpkg-reconfigure has finished, all necessary tables do now exist in the database mailman3: mailman3=> \dt List of relations Schema | Name | Type | Owner --------+--------------------+-------+---------- public | _request | table | mailman3 public | acceptablealias | table | mailman3 public | address | table | mailman3 public | alembic_version | table | mailman3 ... An initial start of the service mailman3 shows no errors: # systemctl start mailman3 # systemctl status mailman3 ● mailman3.service - mailman3 server. Loaded: loaded (/lib/system/system/mailman3.service; enabled; vendor default: enabled) Active: active (running) since Thu 2022-11-03 10:10:29 CET; 11min ago. ... 2. Installing mailman3-web -------------------------- Once the mailman3 package is installed, package mailman3-web can be installed: # apt install mailman3-web This time you should not do the installation process without the help of the installation tool dbconfig-common: * Configure database for mailman3 with dbconfig-common? Yes * Database type to be used by mailman3-web: pgsql * Host name of the PostgreSQL database server for mailman3-web: new host * Host running the PostgreSQL server for mailman3-web: <remote host> * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> Even if the DBA password prompt cannot be answered: Create configuration file /etc/dbconfig-common/mailman3-web.conf with new version Password for user postgres: ?????? the dbconfig-common tool should be used again: * Next step for database installation: retry * Configure database for mailman3-web with dbconfig-common? Yes * Connection method for PostgreSQL database of mailman3-web: TCP/IP * Host name of the PostgreSQL database server for mailman3-web: <remote host> * Port number for the PostgreSQL service: 5432 * Method for authenticating the PostgreSQL administrator: password * Method for authenticating PostgreSQL user: password * PostgreSQL database name for mailman3-web: mailman3web * PostgreSQL username for mailman3-web: mailman3 * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> * Name of the database's administrative user: postgres * Password of your database's administrative user: sldjkfhskldfjhyxlökcjy The prompt for the DBA password cannot be answered correctly again, therefore "ignore" should now be the best choice for the further course of the installation process: * Next step for database installation: ignore * Password of your database's administrative user: sldjkfhskldfjhyxlkcylö An error does occur now because the database user mailman3 can not be created: ... Password for user postgres: unable to connect to postgresql server. error encountered creating user: psql: error: fe_sendauth: no password supplied ... But this error doesn't matter, because the database user mailman3 does already exist and the installation process of the package mailman3web will nevertheless be finished completely. A look into file /etc/mailman3/mailman-web.py shows that dbconfig-common has entered the database connection to the database server correctly, too: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman3web', 'USER': 'mailman3', 'PASSWORD': '<secret>', 'HOST': '<remote host>', 'PORT': '', <--- missing? 'OPTIONS': { }, } } Also all required tables have been created in the database mailman3web during the installation process: mailman3web=> \dt List of relations Schema | Name | Type | Owner --------+-----------------------------------+-------+---------- public | account_emailaddress | table | mailman3 public | account_emailconfirmation | table | mailman3 public | auth_group | table | mailman3 public | auth_group_permissions | table | mailman3 public | auth_permission | table | mailman3 ... The initial start of the service mailman3-web shows no errors: # systemctl start mailman3-web # systemctl status mailman3-web ● mailman3-web.service - Mailman3-web uWSGI service. Loaded: loaded (/lib/system/system/mailman3-web.service; enabled; vendor default: enabled). Active: active (running) since Thu 2022-11-03 10:42:30 CET; 11min ago ... 3. Intergration in boot sequence -------------------------------- Finally, the two services mailman3 and mailman3-web can be included in the boot sequence: # systemctl enable mailman3 Synchronize the state of mailman3.service with the SysV service script with /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3 # systemctl enable mailman3-web Synchronize the status of mailman3-web.service with the SysV service script using /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3-web ------------ >8 ------------ On 01.11.22 08:10, Stephen J. Turnbull wrote: > blackout69 writes: > > > For mailman3 > > sudo dpkg-reconfigure mailman3 > > > > For mailman3-web > > sudo dpkg-reconfigure mailman3-web > > I guess those will work too as long as the users and databases have > been created. But they'll still fail at the first step without that > (and they might fail anyway if checking for the existence of those > users and databases involves logging in to the database as the admin > user). > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

3 2

Moderate first postings of new members
by c.buhtz＠posteo.jp Nov. 3, 2022

Nov. 3, 2022

Hi, I'm looking for a feature but not sure if I missed it or if it isn't really there. By default, I accept all messages of list members without moderating them. What I want is that I would like to moderate the messages of new subscribed members until I set them to auto-accept all messages. I want to see what a new member is posting before it is send/accepted to the list. Is this possible? Kind Christian

3 3

Mailman upgrade results in page not found error
by Andrew Hodgson Nov. 3, 2022

Nov. 3, 2022

Hi. Just doing the Mailman suite upgrade on my small installation I use for test purposes. Steps include: Run backup script Stop services Mv venv venv-old python3 -m venv --system-site-packages --symlinks venv source venv/bin/activate pip install -U pip pip install mailman mailman-hyperkitty hyperkitty postorius whoosh deactivate ./bin/Django-admin collectstatic ./bin/Django-admin migrate At this step I got an error regarding the import of URLs, a quick Google suggested this was because the new venv has upgraded to Django 4.0. I downloaded the urls.py from the mailman-web Git repo (I should migrate to this at some point I know) and replaced my version with this one. This allowed the migrate to run correctly. Once services were up everything worked as expected except for the web page. If you go to https://lists.hodgsonfamily.org you get a Postorius page not found error, however if you click on the Mailman logo you get to the correct place. I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of having https://lists.hodgsonfamily.org going to the correct place? Urls.py: # -*- coding: utf-8 -*- # Copyright (C) 1998-2016 by the Free Software Foundation, Inc. # # This file is part of Postorius. # # Postorius is free software: you can redistribute it and/or modify it under # the terms of the GNU General Public License as published by the Free # Software Foundation, either version 3 of the License, or (at your option) # any later version. # # Postorius is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for # more details. # # You should have received a copy of the GNU General Public License along with # Postorius. If not, see http://www.gnu.org/licenses/. from django.conf.urls import include from django.contrib import admin from django.urls import path, reverse_lazy from django.views.generic import RedirectView urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('admin/', admin.site.urls), ] Thanks. Andrew.

3 3

How to add new lists?
by fstltna＠yahoo.com Nov. 3, 2022

Nov. 3, 2022

I have been able to get the web interface up and the default "mailman@" address is there and appears in the list of lists, but when I add a list from the command line with a command like "mailman create foo(a)ourlists.gameplayer.club" it does not return a error and using "mailman lists" lists it as existing. However there is no new entries in the /etc/aliases file and the new list doesn't appear in the web interface... Any ideas?

2 1

Adding list via web form
by fstltna＠yahoo.com Nov. 3, 2022

Nov. 3, 2022

Trying to add a list using the web form but I get this: "Error: You are not authorized to create new mailing lists". Do I need to log in somewhere? I thought I was logged in as admin but maybe not?

2 1

Start a new thread and Reply buttons don't work on web interface
by mcashdollar＠anl.gov Nov. 1, 2022

Nov. 1, 2022

Hi, I'm planning on upgrading some of our mailing lists from Mailman 2 to Mailman 3. I setup a test server to try Mailman 3. I notice that when I go to "Archives" in the web interface and choose "Start a new thread" or "Reply" to post a message on my test list, it says successful, but the message never shows up. Looking at the logs, I don't see any errors. I can see the HTTP POST in the log and it seems like everything works: [pid: 70249|app: 0|req: 41/93] 127.0.0.1 () {46 vars in 1223 bytes} [Tue Nov 1 21:03:25 2022] POST /archives/list/discuss(a)lists.chicagohpc.org/message/ATXUU5VT NBT6TIF72T7WNNHDIJNOROIF/reply => generated 949 bytes in 104 msecs (HTTP/1.0 200) 8 headers in 258 bytes (1 switches on core 1) I'm using nginx as the http server. location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /static/ { alias /opt/mailman/web/static/; autoindex off; } Does anyone have an idea of why posting messages from the web interface never shows up? I turned on all the debug logs but can't find an error. Thanks

2 1

No DBA password when installing Mailman3 with remote database server
by Markus Ludwig Grandpré Nov. 1, 2022

Nov. 1, 2022

Dear Mailman3 list, I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system with a remote Postgres database server. During the installation process dpkg is asking for the DBA password that our DBA team would not provide to me. So what can I do? Best regards, Markus -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

4 5

about the last upgrade, one more thing about urls.py
by Guillermo Hernandez (Oldno7) Oct. 31, 2022

Oct. 31, 2022

I forgot to mention that I found one error in the last upgrade procedure in the migrate part. It is about the urls.py file. It's about the import from django.conf.urls the "url", that now is inexistent. After searching around, I've edited urls.py like below. That saved me from modifying more things in that file. ### from django.conf import settings ### mod. 30/10/22 ###from django.conf.urls import include, url from django.conf.urls import include from django.urls import re_path as url ##### -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

1 0