- Mailman-users - lists.mailman3.org

Link to account
by Lars Bjørndal 14 Apr '23

14 Apr '23

Hi, list! On one of my sites, I want to have all Mailman3 links to go under /mailman3. Even though, the Login link goes to a URL like: https://list.punktskriftutvalget.no/accounts/login/ How can I ensure it goes to https://list.punktskriftutvalget.no/mailman3/accounts/login/ Thanks, Lars

2 6

REST API http://.../3.1/users/../preferred_address returns 404 for GET and POST
by Eric Vyncke 13 Apr '23

13 Apr '23

Postorius 1.3.6 does not work anymore when displaying the details of a list that I own (https://lists.XXX.org/mailman3/postorius/lists/rapcs-pilotes.listsXXXorg/) . It worked before but there was several upgrades in between (Ubuntu, apt packages, MySQL, Python). It displays the usual header/footer of the page but with "Something went wrong" above a red box with "HTTP Error 404:". /var/log/mailman3/mailman.log last entries are below (note the 404 result codes in the REST API): Apr ... 127.0.0.1 - - "GET /3.1/users/d5...94 HTTP/1.1" 200 418 Apr ... 127.0.0.1 - - "GET /3.1/users/d5...94/preferred_address HTTP/1.1" 404 0 Apr ... 127.0.0.1 - - "GET /3.1/addresses/eric(a)XXX.org HTTP/1.1" 200 379 Apr ... 127.0.0.1 - - "POST /3.1/users/d5...94/preferred_address HTTP/1.1" 404 0 /var/log/mailman3/web/mailman-web.log of course has an exception about this 404 result code. Using the MM3 shell, the preferred_address can be displayed and even modified. There are also good values in the MySQL database. Other API endpoints for users work fine (preferences, addresses, ...) Postorius system information is: Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, Mar 13 2023, 10:26:41) [GCC 9.4.0] Running Ubuntu 20.04.4 LTS and Python 3.8 Thanks in advance for any hint to solve this issue (I have held messages that I would love to accept)

2 6

Transaction failed: Duplicate header 'DKIM-Signature'
by Mohsen Masoudfar 13 Apr '23

13 Apr '23

I am observing the following error message in the logs for one specific list: = = = relay=email-smtp.us-east-1.amazonaws.com[35.168.84.210]:587, delay=0.27, delays=0.05/0.04/0.12/0.06, dsn=5.0.0, status=bounced (host email-smtp.us-east-1.amazonaws.com[35.168.84.210] said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) = = = As I mentioned, this happens for one single list only and this list has not been able to send any email for a week now. After checking mailman-users, I came across the following setting, which seems kind of related to my issue: = = = To distribute messages with valid DKIM signatures, I set remove_dkim_headers: yes in /etc/mailman3/mailman.cf = = = Here are my questions: 1 - I have around 100 lists and this happens for this one list only, so, I am not sure, if the issue might be solved with this change. 2 - Because this happens for this one list only, I would rather change it for this one list only, is there any option available changing it for one list only and not for the whole server? Thanks M

2 3

RemoteUserBackend for Mailman3?
by Markus Ludwig Grandpré 12 Apr '23

12 Apr '23

Dear MM§-users, is there a good documentation and example how I can learn to enable django.contrib.auth.backends.RemoteUserBackend for Mailman3? I've already found a detailed documentation (see [1]), but I do not manage to implement this AuthN mechanism for Mailman3. Can you help me? Btw. how can I disable and remove the Fedora button from Maliman3's login page? Best, Markus [1] <https://docs.djangoproject.com/en/4.1/howto/auth-remote-user/> -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

4 6

List notices in French, but subject in English
by Mark Dale 12 Apr '23

12 Apr '23

Hi, I have a list set with it's preferred language set as French and the body of the standard notification emails (eg. Welcome message) is correctly sent in French, however the subject of the emails is in English. Can the list be configured so the subject is also in French, or is this an issue with gettext .mo files somewhere? This is on Debian package Mailman 3.3.3 Thanks, Mark

2 2

An archive/read-only list on a full setup?
by Andreas Schamanek 11 Apr '23

11 Apr '23

I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly. After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc. What's the proper way to set up a hyperkitty-only list? -- -- Andreas :-)

2 2

Change base mailman URL path
by chad.hays86＠gmail.com 08 Apr '23

08 Apr '23

Hi, I recently completed the a Mailman3 install using these[1] instructions. I'm able to access the web interface, the Django admin app, etc off the root domain URL. For example: https://mydomain.org/mailman3, https://mydomain.org/admin, https://mydomain.org/archives What's the most straightforward way to put all of these URL paths behind a different context? For example: https://mydomain.org/lists/mailman3, https://mydomain.org/lists/admin, https://mydomain.org/lists/archives I'm running Apache2 as my web server and am using mod_proxy to proxy requests to uwsgi. [1] https://docs.mailman3.org/en/latest/install/virtualenv.html

2 2

Debian Package Install - Ownership and Permissions
by Dave Hall 07 Apr '23

07 Apr '23

Hello, I know that installing from Debian packages is not the preferred method - unfortunately that's what I'm stuck with at the moment. I have an installation that is sort of working, but there seems to be a lot of issues relating to ownership and permissions that I'll have to manage by hand, so I am asking for some guidance. I'm seeing an interplay between 'list' (the existing Mailman2 user), www-data (the Apache user) and root. Given that it seems like almost everything that's part of mailman3-web/django/hyperkitty is running in uwsgi, should I maybe change /etc/mailman3/uwsgi.ini to use 'list' as the uid/gid rather than www-data and then also change any user/group permission to 'list' as well? Thanks -Dave -- Dave Hall Binghamton University

4 9

Problem with starting core - problem getting a lock on something
by Jens Günther 06 Apr '23

06 Apr '23

Unfortunately our mailman-core-container doesn't start anymore correctly. We updated lately to v0.4.5 and it ran smoothly for the last 4 weeks. This morning the RAM crashed and I then had to restore some things since the RAID was affected. Anyway, the container doesn't get up anymore although we didn't change anything in the setup. Does anybody know what the error means and how we could fix that? "Could not acquire the lock" normally means that some permissions aren't right ... right? Actually I don't know where to start. What I already did: remove the container completely and rebuild it. Thank you in advance! Jens. Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 125, in acquire_lock_1 lock.lock(timedelta(seconds=0.1)) File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 386, in lock raise TimeOutError('Could not acquire the lock') flufl.lock._lockfile.TimeOutError: Could not acquire the lock During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 237, in details lockfile, hostname, pid, random_ignored = filename.split( ValueError: not enough values to unpack (expected 4, got 1) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/bin/master", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3.10/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3.10/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 580, in main lock = acquire_lock(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 151, in acquire_lock lock = acquire_lock_1(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 131, in acquire_lock_1 hostname, pid, tempfile = lock.details File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 241, in details raise NotLockedError('Details are unavailable') from error flufl.lock._lockfile.NotLockedError: Details are unavailable

1 1

Hyperkitty shows "<" as <
by Andreas Schamanek 05 Apr '23

05 Apr '23

Hi fellow Hyperkitties, I migrated from Mailman 2 to 3 and imported my 1st list via `manage.py hyperkitty_import` to Hyperkitty 1.3.4 (the Debian package), but that might not even be relevant to my problem: All "<" and ">" in old and new messages are shown as "<" and ">" in message views _however_ they are shown correctly in overview abstracts e.g. at //server/mm3/hyperkitty/list/testlist@server/latest Is this a bug in Hyperkitty? Or is our server doing something funky? -- -- Andreas :-)

2 4