- Mailman-users - lists.mailman3.org

CPU usage when idle
by roughnecks May 29, 2025

May 29, 2025

Hello, if you look at this graph you'll notice how my VPS "reacted" after mailman3 install. It's a Debian stable host, and I installed packages via apt. I mean, isn't this a bit too much for a software that is idle, because no lists are currently in use? RED is my VPS, the other colors are other machines. Thanks -- roughnecks ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/jpeg Name: raw (1).jpg

4 7

Unable to update templates
by Mark May 29, 2025

May 29, 2025

Hi, I'm unable to update the custom welcome template (list:user:notice:welcome) after it's initial creation. When the custom welcome template is created (in Postorius), and a user then subscribed by the list-owner (using mass subscribe), the welcome message is received as expected. However when I update the template, the databases are updated correctly but the Welcome message is still sent with the old template content. mailman.templates mailmanweb.postorius_emailtemplate Additionally, if I delete the template and create a new one the old content still gets sent. I cannot find where this content is written or is being cached. Any clues on tracking this bugbear down gratefully received. Regards, Mark $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://******:******@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ -- Installed with venv. ===================== Query to DB - mailman ===================== SELECT URI FROM TEMPLATE WHERE NAME = 'list:user:notice:welcome' AND context = 'testlist.example.com'; ====================== Result (all directories and file owned by 'mailman' with '765' permissions) ====================== file:///templates/list/testlist.example.com/list:user:notice:welcome ====================== Content of above Welcome file ====================== This is the second test Welcome message. ====================== Text of the welcome message actually received. (It's the content of the first custom template.) ====================== This is the first test message to Welcome new members.

2 7

Re: MM broken after proxy migration (Nginx -> Caddy)
by Andreas Kemper May 28, 2025

May 28, 2025

Hi Stephen, thanks for the comprehensive explanations and sorry for initially not answering to the list (I expected this to be the default behaviour). Afterall it turned out that my mailman.db was somehow broken, even though I couldn't find any fishy / strange things in Postorius. Since anyhow just a few lists are hosted on the server and subscriptions for most of them being managed fron another program, I decided to remove MM3 completely and start with a fresh configuration. BR Andreas Am 28.05.2025 um 18:16 schrieb Stephen J. Turnbull: > Hi Andreas > > Andreas Kemper writes: > > > thanks for the quick response. > > Please reply to list (personal mail doesn't get read any faster) or to > all (I don't mind getting the duplicate). The odds are quite good > that somebody else will be able to reply before I do (I live in Japan, > normally I wouldn't be up now ;-). > > > Agree there, even though I haven't found any "settings.py" file in > > my Debian 12 installation yet. > > Normally the override settings.py is in /etc/mailman3/settings.py. If > you have no overrides, I don't know where Debian would put it. There > are actually several in the distribution where the highest levels are > normally in site-packages/mailman_web/settings/*.py (*not* named > "settings.py", I think they are "base.py" and "mailman.py"). Come to > think of it, I'm not sure whether Debian would put mailman and > mailman_web in site-packages or somewhere else. :-( (I'm a Debian > user since 1997, but my mission-critical applications are installed > from source.) > > > Hmm, executing > > > > sudo -u list mailman stop followed by > > sudo -u list mailman start > > > > first deletes and afterwards recreates the lock files, > > That is the expected behavior if Mailman is running normally. Are you > sure there's actually a recurring problem? Or did Mailman just crash > once, and the problem was the stale master lockfile? > > > where both of them are dated in the future, > > Also expected. I forget exactly what expiration of the lock file > triggers, but there's some regularly scheduled cleanup that happens > then. > > > plus mailman.log has a duplicate line in the end, > > It's a duplicate because the default is for there to be two processes > serving the REST API. This is configurable. See more comments at the > end. > > > even though I couldn't seen any mailman-related process (ps auxw | > > grep mailman) after stopping it. > > If the process is named by the full path to the executable, then you > will see "mailman", but if I recall correctly on Debian the Mailman > processes run under the users "list" for Mailman core, and "www-data" > for the web UIs. The various components run under different names: > master, nntp, lmtp, command, rest, etc. I forget what process names > you would see for the Django processes. > > > In doubt I will simply redirect the specific paths, mainly > > /accounts/fedora, > > That makes sense as the earlier you reject a connection the less > resources are used by your server, and the less information can leak > to an attacker. > > > small addition to my previous post. "ps auxw" shows in total three > > process for MM's rest component, i. e. > > > python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 > > > To serve ports 8000 and 8001, I would have expected two processes, > > but to see three of them surprises me somewhat. > > It's not uncommon for moderators to go AWOL, or for somebody to spam > the server with either posts or subscription activity, and end up with > hundreds or thousands of entries in the pending requests table. > Serving those queries can take a long timemany seconds or even time > out. Mailman core deals with it in the least complex, most robust way > imaginable: it runs more REST API server processes. (3 total by > default. One is the "master" that handles requests from the Django > apps and communication with Mailman core and starts new workers when > old ones exit or crash. Two are "workers" that actually handle a > certain number of requests then exit.) By default Mailman is > configured to use up to four when really busy, but normally there are > only two. > > Django runs only one -- it deals with concurrent requests in a > different way. > > Steve >

1 0

Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py
by Christian Schneider May 28, 2025

May 28, 2025

Dear mailman community, with the help of you I was able to set up a new mailman3 environment (a big THANK YOU!!! :-)): OS: Ubuntu 24.04-LTS mailman: GNU Mailman 3.3.10 (Tom Sawyer) Python: 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] Method: Python Virtual Environment Installation My configuration files are placed in the following directory: /etc/mailman3 - gunicorn.py - mailman.cfg - settings.py The environment is up and running: A list for testing is set up and mails are transfered (and archived) using the test-list - successfully... :-) Looking at the thread overview of the list (in Hyperkitty archives) I realized that the shown date format is unusual (for Germany), like: Do Mai 22, 3:57 nachm. (meaning: Thu May 22, 3:57 p.m.) I would prefer a format like: 22-05-2025 15:57:24 So I tried to reconfigure this setting in settings.py according to this URL: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the format did not change. (After changing settings.py I initiated a restart of mailman3 and mailmanweb) I also set USE_L10N to False as suggested in Django-Docs: https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO… My /etc/mailman3/settings.py is parsed - as far as I can say because changing USE_I18N to false (in /etc/mailman3/settings.py) switches date to English as this is my locales-setting on Ubuntu... Nevertheless the format stays the same (in this case: Thu May 22, 3:57 p.m.) How can I adjust the date format (in the discussion boxes) at the thread overview page (url: https://my-domain.de/archives/list/test-list@lists.my-domain.de/)? Any hint is appreciated! Thank you very much and kind regards Christian

3 6

Place holders
by Mark May 28, 2025

May 28, 2025

Hi, The place holders listed as available on the "Add new template" page are: $hyperkitty_url $listname $list_id: $display_name $short_listname: $domain $info $request_email $owner_email $site_email $language The only one that seems to sort of work on my template is $list_id - which displays as "testlist". (I was expecting to see "testlist(a)example.com"). The others just get displayed as a variable. Eg. $owner_email Have I missed a setting somewhere? Regards, Mark GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]

2 1

list's RSS feed has wrong URLs (base path instead of subdomain)
by Simone May 28, 2025

May 28, 2025

Hello, very new to mailman :) I have set this up and it's working well so far, but today I noticed that links in list's RSS feed point to https://mydomain.tld, while mailman is running on https://lists.mydomain.tld. I wouldn't know how to fix this.. any hints? Thanks

3 2

MM broken after proxy migration (Nginx -> Caddy)
by Andreas Kemper May 27, 2025

May 27, 2025

Hi, I've been running MM 3 for quite some time, with a couple of lists including members managed via the REST-API from an external program. After some issues with LetsEncrypt certificates, I migrated the HTTPs proxy from previous Nginx now to Caddy with the following Caddyfile: https://listen.dlc-aachen.de { header Strict-Transport-Security max-age=31536000; # Disable access to archive and registration redir /hyperkitty* https://listen.dlc-aachen.de redir /accounts/signup* https://listen.dlc-aachen.de reverse_proxy localhost:8000 { header_up X-Forwarded-Proto {scheme} header_up X-Forwarded-Host {host} } handle_path /static/* { file_server { root /var/lib/mailman3/web/static } } } Following this change, list continued operation as usual, but after a few days it seemed to be attacked via it's GUI, according to the attached Django error message. Since then mailman doesn't send out anymore mails and I have a persistent master.lck file. Furthermore, during mailman start smtp.log always shows a "Connection lost during _handle_client()". I guess the connection loss is related to the master.lck file, hence how can I get rid of it / "reset" mailman? In addion, should I include further directives in my Caddyfile in order to protect mailman from coming attacks? Thx a lot Andreas

2 1

Django: An error occurred while processing your request.
by Florian Sukup May 27, 2025

May 27, 2025

Hi, I running Debian bookworm and have installed mailman3-full (+ postfix). I am new to mailman3 (using mailman2 now) and about exploring how to migrate. I had 3 sites or domains: example.com and two real ones. When I received emails from postorius, then it came from example.com which is nonsense as I worked with the real lists. So I deleted example.com. When I call https://.../mailman3/admin or any of the lists, the result is: Server error An error occurred while processing your request. How can I get out of it? This is only a test environment, so no heart attack. Thank you for any help. Florian.

3 3

Masking email addresses in the archives
by Odhiambo Washington May 26, 2025

May 26, 2025

I must have missed this if it was ever discussed, but is it possible to mask the list members' email addresses in the archives? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 4

Moderation -- implicit destination behavior
by Steve Bachinsky May 24, 2025

May 24, 2025

Hi. We have noticed some posts being held for moderation (even though user has permission to post to list) and Mailman reports: moderation_reasons: ['Message has implicit destination’] The lists are configured for “require_explicit_destination”. However, the email address of the list is clearly in the CC: header of the email (no alias or subdomain). Is there some other reason why Mailman would hold an email for moderation with the reason of “implicit destination”? This moderation is not consistent for same list and poster. The emails come from a large domain with multiple load-balancing email servers. I suspect that it may be something with one or more of the servers being misconfigured, but unable to see anything obvious from the headers and confused why Mailman states the reason to be implicit destination when that does not seem to be the cause. Thanks, Steve

4 4