- Mailman-users - lists.mailman3.org

MTA authentication and smtpd_sender_login_maps
by Jan Eden Nov. 25, 2022

Nov. 25, 2022

Hi, I installed Mailman3 successfully and would like to change the default smtp settings to an authenticated connection (smtp_user, smtp_pass). But my Postfix configuration restricts sending messages via the smtpd_sender_login_maps directive (which points to a hashed file I created years ago) and correctly refuses connections for messages with the test mailing list's From header. I obviously do not want to add an entry to the map file for each mailing list created by someone on the server. Is there a way to programmatically create a sender login map with Mailman? Thanks, Jan

2 2

Hyperkitty no longer archiving
by Hirayama, Pat Nov. 23, 2022

Nov. 23, 2022

Greetings, A couple of months ago, I needed to move the Mailman3 server I inherited from one AWS account to another AWS account. This necessitated a change in the IP address of instance hosting the docker containers that comprise my mailman3 server. I thought I had updated the IP address wherever it needed to be, but I suppose I've missed something, because hyperkitty has not been archiving any messages. (Most of my lists don't archive, so it took a while before someone noticed). When I look at /opt/mailman/var/archives/hyperkitty/spool, I see messages dating back over the past couple of months waiting to be archived. So, they don't appear to be lost (and things are being mailed out normally). The thing is, the IP addresses of the docker containers haven't changed with respect to docker networking. docker networking ------------------------ docker host 172.31.0.1 mailman-core 172.31.0.3 mailman-nginx 172.31.0.5 mailman-postfix 172.31.0.4 mailman-django-uwsgi 172.31.0.2 settings_local.py: MAILMAN_ARCHIVER_FROM = ('172.18.8.14', '172.31.0.1', '172.31.0.2', '172.31.0.3', '172.31.0.4', '172.31.0.5', '127.0.0.1', '::1') During troubleshooting, I added 172.18.8.14 (new IP of the webserver), but that didn't seem to help. It seems like I added one of the docker addresses that was missing .... but again, that doesn't seem to have fixed the issue. mailmansuite.log is full of: ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured ERROR 2022-11-22 00:25:40,399 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured Any suggestions as to where I might look for a solution, or what setting I need to change? Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

4 12

Upgrading a Ubuntu Mailman 3 Installation
by Allan Hansen Nov. 21, 2022

Nov. 21, 2022

Dear Mailman 3 wizards, Several years ago I tried upgrading to Mailman 3 (I did install Mailman 2), but quickly ran into a thicket too complex for me to get out of. Two others - way more experienced than me at system-level manipulations - tried as well but did not succeed. Brian Carpenter of EMWD installed the system seemingly effortlessly, and seemingly overnight. We had a good relationship, and I was a beta site for his new product, SAAS. Brian also did the system MM3 upgrades as they appeared and would check that all was well a couple of times a year. Unfortunately, and I respect that, the current management at EMWD "don't provide working hands service for foreign Mailman 3 installations." I do not dare touch it, based on my earlier attempts with the installation. With Brian's passing I'm thus faced with a system that has no capable system support (I manage the lists, not the core). I have 50+ lists with 10000+ subscription total, and a lot of people depend on this tool. (It's a non-profit organization). So, I'm interesting in hiring someone for part-time, occasional work (a few times a year). Update MM3 as new versions are made available. Diagnose and fix the system if anything goes awry. I will pay you, as I did Brian, out of my own pocket, for your time. Yours, Allan Hansen

2 1

Migrating to mailman-web and Ubuntu 22.04
by Andrew Hodgson Nov. 16, 2022

Nov. 16, 2022

Hi. For various reasons I want to migrate to a larger host running Ubuntu 22.04. I have set up the various packages ok and as part of the migration I want to use mailman-web instead of mailman-suite which is an older setup. I have instructions for Mailman-web for setting up Uwsgi but I would prefer to keep Gunicorn working as per the instructions here: DOC/Mailman 3 installation experience - Mailman Wiki (list.org)<https://wiki.list.org/DOC/Mailman%203%20installation%20experience> Has anyone done this before? Thanks. Andrew.

3 5

New Mailman Core Release
by Mark Sapiro Nov. 15, 2022

Nov. 15, 2022

We are pleased to announce the release of Mailman core 3.3.7. It is published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ The change log is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… - please note the `BREAKING CHANGE` documented there and due to our now using SQLAlchemy >-1.4. Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies (aiosmtpd) not supporting 3.10 yet. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Do not display any lists on index the page (/postorius/lists/) by default (when you create the list it defaults to Hide) - Debian package install
by daniel.botting＠codethink.co.uk Nov. 11, 2022

Nov. 11, 2022

Hi all, I am currently in the process of moving from mailman 2.1 to mailman 3, the basic functions are completed (mailing list and archiving). On our current mailman 2.1 install it advises there are no publicly advertised lists, when I visit mailman3-list.domain/postorius/lists/ I see all the lists that have been created, I require them not to be displayed. I know when you create a list you can on the 'Advertise this list' line select 'Hide this list in list index', but I would like it to default to this in case somebody forgets to select it. I am not a Python expert, though from the description at the top of the below file and the contents further down it looks like you are defining in base.py and then in default.py you are using what was defined, a class of 'Private' which should cause the lists not to be advertised, but they are? File: /usr/ib/python3/dist-packages/mailman/styles/base.py class Private: """Settings for private mailing lists.""" def apply(self, mailing_list): mlist = mailing_list mlist.advertised = False <-------------- mlist.archive_policy = ArchivePolicy.private mlist.subscription_policy = SubscriptionPolicy.confirm_then_moderate File: /usr/lib/python3/dist-packages/mailman/styles/default.py class PrivateDefaultStyle( Identity, BasicOperation, Bounces, Private, Discussion, Moderation): """Style for mailing-lists with private archives.""" name = 'private-default' description = _('Discussion mailing list style with private archives.') def apply(self, mailing_list): """See `IStyle`.""" Identity.apply(self, mailing_list) BasicOperation.apply(self, mailing_list) Bounces.apply(self, mailing_list) Private.apply(self, mailing_list) Discussion.apply(self, mailing_list) Moderation.apply(self, mailing_list) I added the below to /etc/mailman3/mailman.cfg: [styles] # The default style to apply if nothing else was requested. The value is the # name of an existing style. If no such style exists, no style will be # applied. default: private-default I took 'private-default' from /usr/lib/python3/dist-packages/mailman/styles/default.py, this means now when a new list is created the List style is 'Discussion mail list style with private archives so it is not displayed when you are logged out at /hyperkitty. Many thanks Daniel

1 0

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

Nov. 8, 2022

Am 08.11.2022 um 09:14 schrieb Axel Rau <Axel.Rau(a)chaos1.de>: > Am 08.11.2022 um 08:11 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: > > > What is /var/templates now? I.e., is it a symlink to /usr/local/mailman3/var/templates? what does `ls -l /var/templates` (no slash at the end) show? > It does not exist. No directory, no link. Maybe I remember it wrong. Axel PS: Can I send posts with attachments to this list? My last posting didn’t make it. --- PGP-Key: CDE74120 ☀ computing @ chaos claudius --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

2 1

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

after last upgrade I've got a CSRF failed verification
by Guillermo Hernandez (Oldno7) Oct. 31, 2022

Oct. 31, 2022

I did upgrade one of my mailman3 server after Abhilasj announcement: "I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 1 <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> 2. Postorius 1.3.7 2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5]" I did it via pip and all seems to be working, but when I try to discard or accept any message via postorius it shows a Forbidden 403 error CSRF verification failed. In my settings.py I have commented out these variables: # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' I've been messing with them whith no results. It's like it lacked some value in some template... Can someone, please, point me in the right direction? Thanks in advance -- ___________________________________________ 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.

2 7

Re: Problems after Upgrade
by Mark Sapiro Oct. 31, 2022

Oct. 31, 2022

On 10/30/22 17:37, Jeff Steele wrote: > Thanks Mark, > > I was able to fix this problem easily by modifying: > > mailman3/lib/python3.8/site-packages/compressor/management/commands/compress.py > > to change the line: > > Command.requires_system_checks = None > > to > > Command.requires_system_checks = [] > > Now, bin/mailman-web compress runs but outputs: > > CommandError: Compressor is disabled. Set the COMPRESS_ENABLED setting or use --force to override. > > which I guess is fine. If you want to do off line compression which is a good thing, you need to set ``` COMPRESS_ENABLED = True ``` in your Django settings. I recently added this and also a note about CSRF_TRUSTED_ORIGINS to https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Problems after Upgrade
by Jeff Oct. 31, 2022

Oct. 31, 2022

Hello, I tried to upgrade to the latest mailman3 version using the following command: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web mailmanclient There didn’t appear to be any problems with this step and I’ve since run it again a few times and only see that the requirements have been satisfied. When first running the command: mailman-web migrate I received several errors dealing with search_text in the package compressor (at least that’s as best as I remember, I wasn’t taking notes). I fixed these manually by changing it to search_str. Eventually "mailman-web migrate” started working and has subsequently worked. When I run the command: mailman-web compress I get the following error: traceback (most recent call last): File "bin/mailman-web", line 8, in <module> sys.exit(main()) File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 279, in fetch_command klass = load_command_class(app_name, subcommand) File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 49, in load_command_class return module.Command() File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/base.py", line 274, in __init__ raise TypeError("requires_system_checks must be a list or tuple.") TypeError: requires_system_checks must be a list or tuple. I have not been able to fix this and would appreciate any assistance. When I run the command: bin/mailman-web collectstatic It asks me yes or no continue and when I enter “yes” it displays the following which I assume means it worked: 372 static files copied to '/usr/local/mailman3/web/static', 38 unmodified Starting mailman3 seems to work by the status message shows the following: systemctl status -l mailman3 ... Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 259, in send_warnings_and_remove Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: self._send_warnings() Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 310, in _send_warnings Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: member.address, Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/member.py", line 121, in address Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return (self._user.preferred_address Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: AttributeError: 'NoneType' object has no attribute 'preferred_address' lines 13-35/35 (END) I have been receiving admin requests to approve messages. But, I can’t approve them because of the following issue: Starting mailman-web seems to work as expected with no errors. However, when I try to login to the web interface, I get a HTML page with the following error: init__() got an unexpected keyword argument 'providing_args' Request Method: GET Request URL: http://lists.crestwood-dc.org/accounts/login/?next=/mailman3/lists/crestwoo… Django Version: 4.1.2 Exception Type: TypeError Exception Value: __init__() got an unexpected keyword argument 'providing_args' Exception Location: /usr/local/mailman3/lib64/python3.8/site-packages/compressor/signals.py, line 4, in <module> Raised during: allauth.account.views.LoginView Python Executable: /usr/local/mailman3/bin/uwsgi Python Version: 3.8.13 As a result, I cannot login and approve posts. I would greatly appreciate any assistance with these issue. Thanks much!

2 2

Mailman3-core rest failure
by Jacob Sievert Oct. 30, 2022

Oct. 30, 2022

Hello, since our last update from python 3.6 to python 3.9 our mailman server returns the following errors if we try to access the list via postorius. [29/Oct/2022:13:25:25 +0200] "GET /3.1/lists/XXX.XXX.XX/archivers HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.4" I tried to set the logging to a more verbose state but couldn't get a better message yet. If somebody knows what went wrong, that would be great. regards Jacob

2 3

Adding users
by horvath.arpad.szfvar＠gmail.com Oct. 30, 2022

Oct. 30, 2022

Hi, I've tried to add new members to the mailing list, but I failed even if I tried 3 ways: - manage.py shell - invitation letter - sending a letter to subscribe. I try to solve it with the Python shell now. Based on this site: https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode… I tried this one from Debian bash command line, but there is an error message, as you can see at the end. # pwd /usr/share/mailman3-web # ./manage.py shell In [1]: from mailman.interfaces.usermanager import IUserManager In [2]: from zope.component import getUtility In [3]: user_manager = getUtility(IUserManager) --------------------------------------------------------------------------- ComponentLookupError Traceback (most recent call last) <ipython-input-3-9500ce4250f0> in <module> ----> 1 user_manager = getUtility(IUserManager) /usr/lib/python3/dist-packages/zope/component/_api.py in getUtility(interface, name, context) 167 if utility is not None: 168 return utility --> 169 raise ComponentLookupError(interface, name) 170 171 def queryUtility(interface, name='', default=None, context=None): ComponentLookupError: (<InterfaceClass mailman.interfaces.usermanager.IUserManager>, '') What do I wrong. Should I stop all my mailman processes first? Thanks, Arpad

2 4

restriction on attrs?
by Stephen J. Turnbull Oct. 27, 2022

Oct. 27, 2022

Hi, I'm working with a frozen requirements.txt for a full Mailman 3 install (BigCorp QA stuff), and trying to decide whether it's worth fighting BigCorp QA to update it to the recent releases. The previous test install pulled in attrs 22.1.0, but now mailman-3.3.6 restricts attrs<21.3. I can't find any documentation for this change, which Mark made in a change d0595dec76 that's documented to be about lmtp and smtp. What's going on with this change? Steve

3 3

New Mailman Releases
by Abhilash Raj Oct. 27, 2022

Oct. 27, 2022

Hi, I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 [1] 2. Postorius 1.3.7 [2] 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of changelogs are available below: [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 -- Something weird is going on with the page missing the bullets. [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies not support 3.10 yet (aiosmtpd). Thanks to all the contributors for making this release possible and apologies on my end for delayed releases. If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/ -- thanks, Abhilash Raj (maxking)

2 4

Sanity check of upgrade procedure
by David Newman Oct. 27, 2022

Oct. 27, 2022

The other day Abhilash posted here that updated releases are available. I rarely upgrade my Mailman3 server running in a venv on Debian 11. But when I have there was previously an issue with mistune, requiring commands like this (run as mailman in a venv): pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi pip install wheel mailman pymysql mysqlclient pip install mistune==2.0.0rc1 mailman-web migrate mailman-web compress mailman-web collectstatic mailman-web compilemessages For these new releases, is that mistune step still needed? Thanks! dn

2 4

Internal Server Error: Reattach this thread
by hasimoto＠designet.co.jp Oct. 27, 2022

Oct. 27, 2022

Hi, In the archive, clicking "Reconnect this thread" causes an internal server error. I received the following email, but I don't know how to solve it, please help me. -- -- -- -- Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest -- -- -- -- Internal Server Error: /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest AttributeError at /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest 'function' object has no attribute 'lower' Request Method: GET Request URL: http://mailman.example.com/archives/list/testml@list1.example.com/thread/LQ… Django Version: 3.0.14 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.10.6 Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python310.zip', '/usr/lib/python3.10', '/usr/lib/python3.10/lib-dynload', '/opt/mailman/venv/lib/python3.10/site-packages'] Server time: 水, 19 10月 2022 01:07:28 +0000 Installed Applications: ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 134, in inner return func(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 413, in reattach_suggest default_search_query = stripped_subject( File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", line 155, in stripped_subject if subject.lower().startswith(mlist.subject_prefix.lower()): Exception Type: AttributeError at /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest Exception Value: 'function' object has no attribute 'lower' Request information: USER: admin GET: q = '' POST: No POST data FILES: No FILES data COOKIES: csrftoken = 'cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK' sessionid = 'upuj3rv0wkxafklk633lx2jppwgrco1t' META: CSRF_COOKIE = 'cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate' HTTP_ACCEPT_LANGUAGE = 'ja,en-US;q=0.7,en;q=0.3' HTTP_CONNECTION = 'close' HTTP_COOKIE = 'csrftoken=cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK; sessionid=upuj3rv0wkxafklk633lx2jppwgrco1t' HTTP_HOST = 'mailman.example.com' HTTP_REFERER = 'http://mailman.example.com/archives/list/testml@list1.example.com/thread/LQ…' HTTP_USER_AGENT = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0' HTTP_X_FORWARDED_FOR = '192.168.30.94' HTTP_X_REQUESTED_WITH = 'XMLHttpRequest' PATH_INFO = '/archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest' QUERY_STRING = 'q=' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'GET' REQUEST_URI = '/archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest?q=' SCRIPT_NAME = '' SERVER_NAME = 'ubuntu22' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' uwsgi.core = 0 uwsgi.node = b'ubuntu22' uwsgi.version = b'2.0.20' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f4ac0d23570> wsgi.multiprocess = True wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'http' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'http' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'admin1(a)example.org'),)" ALLOWED_HOSTS = ['127.0.0.1', 'mailman.example.com'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = PosixPath('/opt/mailman/web') CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'} COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter', 'compressor.filters.cssmin.rCSSMinFilter'], 'js': ['compressor.filters.jsmin.rJSMinFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f4ac443e050> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_MANIFEST_STORAGE = 'compressor.storage.OfflineManifestFileStorage' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))" COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/opt/mailman/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_URL = '/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailmanweb', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '5432', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'OPTIONS': {}, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_CHARSET = 'utf-8' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'admin1(a)example.org' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_CHARSET = 'utf-8' FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = 420 FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': 'fulltext_index'}} HYPERKITTY_ENABLE_GRAVATAR = True IGNORABLE_404_URLS = [] INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('uz', 'Uzbek'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_HTTPONLY = False LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LANGUAGE_COOKIE_SAMESITE = None LANGUAGE_COOKIE_SECURE = False LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.WatchedFileHandler', 'filename': '/opt/mailman/web/logs/mailmanweb.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'ERROR', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'ERROR', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'DEBUG', 'propagate': True}, 'postorius': {'handlers': ['console', 'file'], 'level': 'INFO'}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'http://mailman.example.com/mailman3/' PREPEND_WWW = False Q_CLUSTER = {'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default'} ROOT_URLCONF = 'mailman_web.urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_REFERRER_POLICY = None SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'admin1(a)example.org' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [{'id': 'yahoo', 'name': 'Yahoo', 'openid_url': 'http://me.yahoo.com'}]}, 'google': {'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}}, 'facebook': {'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': ['email', 'name', 'first_name', 'last_name', 'locale', 'timezone'], 'VERSION': 'v2.4'}} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/opt/mailman/web/static' STATIC_URL = '/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = False USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'mailman_web.wsgi.application' X_FRAME_OPTIONS = 'DENY' YEAR_MONTH_FORMAT = 'F Y' -- -- -- -- Thank you.

5 11

"Unsubscribe all" button
by Philippe B Oct. 21, 2022

Oct. 21, 2022

Would it be possible to add a confirmation screen after you click on it? Like: WARNING! Clicking "Confirm" will empty the list of all its existing members, regardless of what was entered on the previous screen. That operation cannot be reversed. Are you absolutely sure that you want no one to be on your list anymore? The reason is that we've had a lot of list owners who populate the "Emails to Unsubscribe" box on the "Mass Removal" page with a subset of the list's subscribers and proceed to click "Unsubscribe all" with the expectation that "all" means all the users explicitly listed in the box. Which means that the site admins have to restore the entire list of subscribers every time... If adding a confirmation screen isn't straightforward, maybe the wording on the buttons could be modified: * Unsubscribe users -> Unsubscribe users listed above * Unsubscribe all -> Empty list of all its existing members (irreversible)!!! In the meantime, this was problematic enough for us that my colleague Dan had to resort to hiding the "Unsubscribe all" button from the web page(s), which isn't ideal.

3 3

HyperKitty failure: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400)
by Armin Schöffmann Oct. 21, 2022

Oct. 21, 2022

Hello list, using mailman3 as of current gitlab master with db-backend postgresql 14.5, I get the following error whenever a message is handed over to hyperkitty for archiving: Oct 19 11:43:00 2022 (2164807) HyperKitty failure on https://listserv.foo.bar/archives/api/mailman/archive: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400) Oct 19 11:43:00 2022 (2164807) Could not archive the message with id <kcEE.5Fsdt1DFSK2fk5foEoTfkw.gCYcK5/j2AE@root> Oct 19 11:43:00 2022 (2164807) archiving failed, re-queuing (mailing-list test-list.foo.bar, message <kcEE.5Fsdt1DFSK2fk5foEoTfkw.gCYcK5/j2AE@root>) Oct 19 11:43:00 2022 (2164807) Exception in the HyperKitty archiver: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} Oct 19 11:43:00 2022 (2164807) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} I already re-created the db, but this doesn't solve the issue. Sounds like db-definitions for model "Thread" are incomplete, but I can't identify the underlying db-objects. Thanks for any input, Armin. -- Aegaeon technologies GmbH phone: +49.941.8107344 fax: +49.941.8107356 Legal disclaimer: http://aegaeon.de/disclaimer/email_all_int.txt

4 7

How to enable VERP?
by Andy Smith Oct. 19, 2022

Oct. 19, 2022

Hi, I'm a little confused as to how to enable VERP. mailman3 Debian package, version 3.3.3-1, using Exim 4 MTA. In /etc/mailman3/mailman.cfg I added: [mailman] … verp_delivery_interval: 1 verp_probes: yes and restarted mailman3.service. The list's "Alter Messages / Personalize" setting is "Individual" (but I tried "Full" as well and saw no difference in VERP behaviour). I can see the MTA is doing an individual delivery for each recipient, and the list's custom footer tells the recipient which address they are subscribed under, so I know that part is working. With VERP enabled I was expecting the Return-Path header in the delivered list mail to include a cookie to identify the individual subscriber, but instead it is "listname-bounces(a)example.com" like always. In mailman.cfg my MTA-related settings are: [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.exim4 And the Exim configuration itself has ther macros, router and transport files from the "Exim" section of here: https://docs.mailman3.org/en/latest/config-core.html#configuring-mta edited only for correct paths. That's been working for months for delivering list email in and out, but I'm just now trying to enable VERP and it's not happening. Is there something I'm missing? Thanks, Andy

2 2

cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)
by Paul Ssekamatte Oct. 19, 2022

Oct. 19, 2022

i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. my setup uses an alias domain i.e the mail server is different from the lists server. I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. Even when I change the port number, I still get the same error Kindly assist. here is my mailman.cfg config [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here site_owner: postmaster(a)mail.example.com [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:#passwd@localhost/mailman [archiver.prototype] enable: yes # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] /etc/mailman3/settings.py file is as follows from mailman_web.settings.base import * from mailman_web.settings.mailman import * ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailmanweb', 'USER': 'mailman', # TODO: Replace this with the password. 'PASSWORD': 'passwd', 'HOST': 'localhost', 'PORT': '5432', } } STATIC_ROOT = '/opt/mailman/web/static' LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' ALLOWED_HOSTS = [ 'localhost', 'lists.example.com', 'mail.example.com', # Archiving API from Mailman, keep it. ] SITE_ID = 1 SECRET_KEY = 'key MAILMAN_ARCHIVER_KEY = 'key DEFAULT_FROM_EMAIL = 'postmaster(a)example.com' SERVER_EMAIL = 'postmaster(a)example.com' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), }, } /etc/postfix/main.cf is as follows smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no compatibility_level = 2 smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydomain = example.com myhostname = lists.example.com mydestination = $myhostname, localhost.$mydomain, localhost relayhost = mail.example.com myorigin = $mydomain mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 mynetworks_style = subnet mailbox_size_limit = 4096000000 #message_size_limit = 2048000000 recipient_delimiter = + inet_interfaces = all #inet_protocols = all inet_protocols = ipv4 unknown_local_recipient_reject_code = 550 owner_request_special = no virtual_mailbox_domains = example.com virtual_mailbox_base = /var/vmail virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap postfix domains as follows: lists.example.com example.com postfix lmtp as follows: testlist(a)lists.example.com lmtp:[mail.example.com]:8024 testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 postfix vmap as follows: testlist(a)example.com nmutest(a)lists.example.com testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com

2 2

Mailman 3 Hyperkitty indexes not being built
by tom＠gather.coop Oct. 19, 2022

Oct. 19, 2022

My config looks like this: HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), ... I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years. What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again. Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-n… Thank you!

2 1

URL-lines in templates get folded
by Frank Steinberg Oct. 18, 2022

Oct. 18, 2022

Hi, I’ve added links to some templates to give owners and moderators shortcuts to the postorius UI for moderation tasks, e.g., I’ve added https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> Unfortunately those lines seem to exceed a certain limit and get folded, so that they appear as, e.g. https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> messages (or similar) and are not directly useful. Do you have any suggestion for this situation?

2 4

Is there a way to see all the list's held messages
by bob B Oct. 16, 2022

Oct. 16, 2022

I run mailman but do not admin the lists. Is there a way for me to see all the held messages for all the lists?

3 4

Updating installed pkgs in MM3 venv
by Odhiambo Washington Oct. 15, 2022

Oct. 15, 2022

What is the recommended way for updating installed the installed pkgs in MM3 venv - to ensure that nothing breaks? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 1

Upgrading packages
by Eggert Ehmke Oct. 13, 2022

Oct. 13, 2022

Hello Mark & all, I have the venv installation on my Debian 11 system running. I followed your suggestion to upgrade all packages. When upgrading hyperkitty by this command: pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. All packages were upgraded fine. I applied the patch to venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py to change the mistune import line. When I run now mailman-web migrate I get: *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* *To fix them run 'python manage.py makemigrations --merge'* However, when I run the suggested command as: $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- merge No conflicts detected to merge. Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my production system. Would be nice to shed some light on this. Eggert

2 5

Debian 11 mailman3 installation question
by William Oliver Oct. 13, 2022

Oct. 13, 2022

I have had an installation of mailman3 running for a year or so with no problems. This was a manual installation. I ended up having to change machines, so I decided to install using the debian 11 package. It seems to have gone well except.... when I restart mailman3 service, I get the following fail and error message: oot@emergenis:/etc/nginx/sites-enabled# systemctl restart mailman3 Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xe" for details. root@emergenis:/etc/nginx/sites-enabled# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-10-11 15:09:45 EDT; 8s ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 1056 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) CPU: 9.193s Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 109, in start Oct 11 15:09:43 emergenis.com mailman3[1056]: call_name(config.mta.incoming).regenerate() Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 133, in regenerate Oct 11 15:09:43 emergenis.com mailman3[1056]: raise RuntimeError(NL.join(errors)) Oct 11 15:09:43 emergenis.com mailman3[1056]: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not permitted Oct 11 15:09:43 emergenis.com mailman3[1056]: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation not permitted Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 11 15:09:45 emergenis.com systemd[1]: Failed to start Mailman3 server. Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Consumed 9.193s CPU time. Heres the ls for /var/lib/mailman3/data: root@emergenis:/var/lib/mailman3/data# ls -l total 8 -rw-rw---- 1 list list 315 Oct 11 15:09 postfix_domains -rw-rw---- 1 list list 318 Oct 11 15:09 postfix_lmtp The web interface comes up and seems to "work" but of course complains that mailman3 isn't actually running. I assume there's some posfix config I haven't done right, but I am clueless as to what it is. Thanks in advance for any pointers. billo

2 6

Default setting for Delivery status
by Mark Dale Oct. 12, 2022

Oct. 12, 2022

Hi, Where and how do I set the default setting of "Delivery status" to be "Enabled". I'm not seeing any clues in mailman3-web/settings.py At the moment, a new subscriber is neither "Enabled" or "Disabled". Thanks, Mark

3 3

Performance issues with Mailman 3
by Wong, Wesley Oct. 8, 2022

Oct. 8, 2022

Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists. I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS: VM config: ESX 6.7 (CPU: Intel(R) Xeon(R) Gold 6242) 4 CPU 8 GB SLES 15 SP3 Python 3.9.10 MariaDB 10.5.17 Mailman 3.3.5 Thanks. wesley Wesley Wong Senior Systems Engineer Anderson Computing & Information Services | ACIS 310-206-2571 [ucla-logo---new_smaller] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

2 2

Mailman2 CLI commands for Mailman3
by Dave Hall Oct. 5, 2022

Oct. 5, 2022

Hello. Sorry if this is an old topic. I'm in the process of migrating from 2.1 to 3.2. In my use case one of the advantages of Mailman 2.1 vs services like Google Groups has been the ability to manage lists from the command line. Things like using sync_members to update the list for a committee when the membership of the committee is updated one a year, or like using find_members and remove_members to remove a user from all mailing lists when they leave the organization. Even the ability to script mailing list creation. So far I haven't found these commands in Mailman3. I hope there is a plan to add these soon. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 2

Django site - how to create programmatically - new install
by daniel.botting＠codethink.co.uk Oct. 3, 2022

Oct. 3, 2022

Hi all, I've mainly setup mailman3 to replace our mailman 2.1 install using Ansible, a point I could do with some assistance on is setting the fqdn used programmatically. I've been doing alot of reading before creating this thread. To create a domain I currently navigate to: https://serverfqdn.com/postorius/domains/ and click 'Add Domain'. I believe this is setting the name of the Django site, please accept my apologies if I'm wrong and the SITE_ID=1 is then used, I am only planning to use one domain only. I'm using Postgres and when I check the contents of the Django_mailman3_maildomain table as below afterwards: mailman3web=# TABLE django_mailman3_maildomain; id | mail_domain | site_id ----+--------------------------------------+--------- 1 | mailman3-test2.guest.codethink.co.uk | 1 Many thanks Daniel

2 2

Upgrade Mailmam Core from
by sascha.rissel＠gmail.com Oct. 3, 2022

Oct. 3, 2022

Hello, I have newly set up Mailman 3 on Ubuntu 20.04. Sending and receiving mails between list members does work, but I am currently experiencing two issues: 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. 2) Archiving is activated within list settings, but there isn't any archive created. I found this thread, where the first of these issues is also described: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. I am running Mailman 3.2.2 on Python 3 .8.10. So I need to either upgrade Mailman Core or downgrade Python. I already did > apt-get upgrade > apt-get update Unfortunately this didn't upgrade Mailman Core's version. Which steps do I have to undertake to upgrade Mailman Core? Regards, Sascha.

5 13

All addresses in a bounced list posting seem to be considered as bouncing
by Andy Smith Oct. 1, 2022

Oct. 1, 2022

Hi, I noticed this happened (bounce.log): Jul 09 12:46:51 2022 (71506) Member xxxxx(a)xxxxx.force9.co.uk already scored a bounce on list users.mailman.bitfolk.com today. Jul 09 12:46:51 2022 (71506) Bounce message for a non subscriber: Email users-leave(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Jul 09 12:46:51 2022 (71506) Member andy(a)bitfolk.com on list users.mailman.bitfolk.com, bounce score = 1. Jul 09 12:46:51 2022 (71506) Bounce message for a non subscriber: Email users(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com What happened here is that a reply to one of my posts was rejected by subscriber xxxxx(a)xxxxx.force9.co.uk at smtp time (Exim mainlog): 2022-07-09 12:46:13 1oA9qc-007qOx-0T ** xxxxx(a)xxxxx.force9.co.uk R=dnslookup T=remote_smtp H=mx.avasin.plus.net [212.159.8.200] X=TLS1.2:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=yes DN="businessCategory=Private Organization,jurisdictionOfIncorporationCountryName=GB,serialNumber=03279013,C=GB,L=Sheffield,O=Plusnet plc,CN=mx.avasin.plus.net": SMTP error from remote mail server after end of data: 552 Spam Message Rejected The message contained my email address (andy(a)bitfolk.com) in quoted text, since it was a reply to a message of mine, and also contained addresses from the list's footer, which accounts for the log messages about users-leave(a)mailman.bitfolk.com and users(a)mailman.bitfolk.com. I'm concerned that Mailman seems to have scored my address as bouncing even though it isn't, merely because it appears inside a message that was rejected. Is that expected? Is there any way to avoid it? I see that Mailman has a bunch of heuristics to parse bounce messages. In this case though, there shouldn't have been a bounce message received to users-bounces@, as this was an SMTP-time rejection. Mailman seems to have parsed addresses out of the actual mail it was sending, rather than only scoring the subscriber address it was trying to send a list posting to. Cheers, Andy

3 11

Help addressing some issues with mailman 3 docker images
by Clark Boylan Oct. 1, 2022

Oct. 1, 2022

Hello, Some of us at opendev.org are looking to migrate to mailman 3 for our list servers. We've got about 98% of things sorted out using maxking's docker images (thank you for publishing those along with excellent documentation). There are however a small number of things that we've run into that we'd like to address before we take this to production. * Mailman 3 relies on lynx to convert html email to txt email. Lynx isn't currently installed in the docker images, but I've pushed a PR to add it to the images. https://github.com/maxking/docker-mailman/pull/552 * There are some user and group inconsistencies between the images. Not a deal breaker, but would be good to understand if these are intentional or if they can be changed without massively impacting people. https://github.com/maxking/docker-mailman/issues/550 * Issues with ALLOWED_HOSTS settings making assumptions about the environment and its inputs. We've worked around these by bind mounting in our own settings.py with these problems addressed, but it would be good to address them in case anyone else has run into this too. Details in these github issues: https://github.com/maxking/docker-mailman/issues/548 https://github.com/maxking/docker-mailman/issues/549 Ideally we'd avoid forking the images downstream and modifying them ourselves, but it seems the docker image repo is not getting a ton of attention recently. Totally understand that this may not be the biggest priority. We're happy to help address these by writing fixes and sending pull requests, but guidance would be appreciated before we head too far down that road. Once again thank you for the great documentation and images. They have already gotten us most of the way to production and the issues we've found are relatively minor. Clark

2 1

serving /static-content within /mailman3-web-Folder - change in recent mm release
by Stefan Bauer Sept. 30, 2022

Sept. 30, 2022

Hi Folks, during our migration to latest MM we noticed, that nowadays, the static content is not served from within mailmans base directory, but from outside. old MM3: domain.tld/mailman3/static/django-mailman3/js/main.js new MM3: domain.tld/static/django-mailman3/js/main.js Is there a chance to change it to the old behavior? We are running an additional nginx-proxy in front of mailman-server and dont want to forward /static, but only /mailman3. Thank you.

2 2

2 postfix instances and 1 mailman instance possible?
by charlie derr Sept. 29, 2022

Sept. 29, 2022

Greetings, We will be (temporarily) splitting our single postfix instance and running two separate instances on our email server. Can we configure mailman to listen to one of them and send to the other? If so, please do direct us towards how we would go about configuring mailman to do this. versions: mailman: 2.1.15-30.el7_9.2 postfix: 2.10.1-9.el7 (both via rh/centos repo(s)) thanks so very much for any assistance/direction you're able to provide, ~c -- Charlie Derr Director of Instructional Technology Bard College at Simon's Rock https://simons-rock.edu Encryption key: http://hope.simons-rock.edu/~cderr/ 413-528-7344 Pronouns: he/him/his

2 1

Re: Start thread with list-address instead of own
by Stefan Bauer Sept. 29, 2022

Sept. 29, 2022

Sorry found it. I was just too stupid. It is the anonymous list flag. sorry for the noise. Stefan

1 0

Start thread with list-address instead of own
by Stefan Bauer Sept. 29, 2022

Sept. 29, 2022

HI folks, latest mm3, when starting a new thread via mm3-webinterface -> Archives -> select List -> Start a new thread. It creates the thread with _my own_ personal address. How can i set the "sender" address as the list-address? IIRC with an older mm version, it had a different behavior. Any help is greatly appreciated. thank you. Stefan

1 0

what process creates webui tables (mailmanweb db)?
by tflatley＠gmail.com Sept. 27, 2022

Sept. 27, 2022

hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate - this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file python3 manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? Thanks

2 5

Footer from templates not working - DB issue?
by chris＠mehl.one Sept. 27, 2022

Sept. 27, 2022

Hi, I am running Mailman3 on Debian 11 with Apache and MariaDB. Single installation. When I edit a footer from the WebUI templates, it doesn't show in the messages. Could it be an issue with the related DB? If so - what do I need to change? Many thanks in advance for any leads! Chris

4 5

collectstatic msg
by tflatley＠gmail.com Sept. 27, 2022

Sept. 27, 2022

Hello, in a venv install , after the database migration is complete i run the followign collectstatic compress compilemessages for a package install, i run the following ython3 manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman3/web/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: no CommandError: Collecting static files cancelled. on venv i did not get this msg - venv output 406 static files copied to /opt/mailman/web/static is it safe to overwrite these files? also before i run this do i need the mailman services down? thaniks

2 1