July 2024 - Mailman-users - lists.mailman3.org

deployment recommendation(?)
by noc＠iem.at July 18, 2024

July 18, 2024

(sorry, if this comes in double; i sent the same mail yesterday, but it seems it didn't make it (i did check the archives); so i'm re-sending via the webinterface) hi, it's summer here in europe, and students have left the campus. so - like every summer - I ponder on the idea of migrating our old mailman2 instance that has served us for the last twenty years to a new and shiny mailman3. and - like always - i'm a bit unsure about the best way to proceed to find the optimum deployment strategy for a long-running (decades) medium-sized (our largest list has ~1800 members) installation. one of our primary objectives is receiving *security updates*. we also would like to stay on top of development (that is: use the latest and greatest *stable* mailman3 release). in my heart i am a Debian person, so my mailman2 installation just used the Debian packages. the new deployment machine, will be Debian based as well. now https://docs.mailman3.org/en/latest/install/install.html lists three options: # Debian packages this is what I would normally pick, but: my past experience with mailman3 in Debian was... rather suboptimal. (my current Debian box running mailman3 is frozen at Debian/buster ("old-old-stable") because of mailman3). i see that the packages in current Debian/stable ("bookworm"), are lagging slightly (3.3.8, rather than 3.3.9), though that's to be expected from a distro with stable releases. otoh, Debian/unstable still ships 3.3.8, which is a bit disappointing. in any case, the really nice thing about (Debian-official) Debian packages is that they are typically - stable - guarantee an upgrade path between releases # Docker packages this is of course the simplest from a deployment perspective, but then i'm a bit worried about the security perspective. in my perception, docker deployments tend to get installed and then forgotten, and while the host OS keeps getting updates, the docker images are just left as is. so they tend to get stale. i would like to know how this is handled # virtualenv this is the deployment method recommended in the docs. however, it doesn't say why this method is any better than the others. also, the website says that it was last updated in 2019, so: is this recommendation still relevant? personally i do not have much experience with deployment of long-running software in virtualenv, and i'm esp worried a bit when it comes to switching python releases (which will happen multiple times in the next few years) i use virtualenv all the time for my pet projects, but there it doesn't matter much, if the venv breaks: i just delete it and start from scratch. but those are not long-running services. so: what are the drawbacks, limitations, advantages and benefits of the various deployment methods? i'd really like to make the switch this year! gmfasdr IOhannes

4 3

Setting PYTHONPATH in the virtual environment installation
by Keith Christian July 15, 2024

July 15, 2024

Before switching from a "git clone" installation to the virtual environment install, "/home/mailman3/mailman/src/mailman" was recommended as the PYTHONPATH setting. Here are some paths that exist in the Mailman3 virtual environment on the server in question: /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/__init__.py /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/__pycache__ /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/docs /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/mailarchive.py What is the proper setting for PYTHONPATH in this case? Thanks. ----------- Keith

2 1

mailman findmember runs very slow
by Wong, Wesley July 14, 2024

July 14, 2024

Hi, I am noticing a performance issue with Mailman 3 when using the "mailman findmember" CLI command to search for email address or name. On average, it takes about 15 - 20 seconds to run a query which is very slow IMHO. When searching through web administrator interface for Users, it takes only 1 -2 seconds. Is there a reason for such a discrepancy between the two interfaces? Is there any tuning to the CLI that could help with the performance issue? Here is the setup information regarding the VM hosting the Mailman 3 server: Memory: 16G CPU Cores: 6 Mailman CORE version: 3.3.9 Python version: 3.11.5 Database: MariaDB 10.6.15 OS: SLES 15 SP5 Thanks. wesley * * * Wesley Wong Senior Systems Engineer (ACIS) (310) 206-2571 wesley.wong(a)anderson.ucla.edu<mailto:wesley.wong@anderson.ucla.edu> UCLA Anderson School of Management | Transformative Leaders

2 3

repeated headers in mails from mailinglists
by Tobias Diekershoff July 14, 2024

July 14, 2024

Dear all, we have recently migrated from Mailman2 to Mailman3 and now discovered that all mails going through Mailman3 have the headers Archived-At and List-Archive repeated identically in the mail header ~100 times each. We are running Mailman3 on Debian Bookworm from the Debian repositories (mailman3 3.3.8-2~deb12u2) with postfix (3.7.11-0+deb12u1) and hyperkitty (1.2.1-1). Can somebody of you help me to get rid of the repeated header? Thanks in advance for you help! Best, Tobias -- Tobias Diekershoff >>> System Hacker Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 | fsfe.org/support OpenPGP-Key ID ... 0x25FE376FF17694A1 Fingerprint ...... 23EE F484 FDF8 291C BA09 A406 25FE 376F F176 94A1 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pgp-keys Name: OpenPGP_0x25FE376FF17694A1.asc

3 2

Hiding the "subscribe without creating an account"
by Ben Sturmfels July 14, 2024

July 14, 2024

Hi Folks, My Mailman3 installation is receiving a trickle of fake registrations, for which it then attempts to send a "Your confirmation is needed to join..." email, which typically bounce. I suspect these are coming from the "subscribe without creating an account" form on the list summary page. I notice that lists.mailman3.org doesn't show this form at all - you have to create an account to subscribe: https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ compared to mine with: https://lists.softwarefreedom.com.au/postorius/lists/free-software-melb.lis… Is there a configuration option that does this, or was it a custom change made in the templates? Was the change made to reduce fake registrations? Did it work? Regards, Ben -- Ben Sturmfels Sturm Software Engineering www.sturm.com.au +61 3 9024 2467

3 3

500 error on one list
by Seth Seeger July 13, 2024

July 13, 2024

Hello, One of my lists is return a 500 error when I try to visit the list's home page: HTTP Error 500: {"title": "500 Internal Server Error"} mailmanweb.log says: ERROR 2024-07-13 15:22:30,073 1668 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3.8/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/postorius/views/list.py", line 275, in get 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 File "/usr/lib/python3.8/_collections_abc.py", line 666, in __contains__ self[key] File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/connection.py", line 127, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2024-07-13 15:22:30,079 1668 django.request Internal Server Error: /postorius/lists/XXXX/ ERROR 2024-07-13 15:22:30,079 1668 django.request Internal Server Error: /postorius/lists/XXXX/ mailman.log says: [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX HTTP/1.1" 200 466 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/roster/owner HTTP/1.1" 200 2401 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXX@XXXX/config HTTP/1.1" 200 14262 "-" "GNU Mailman REST client v3.3.2" 2024-07-13 15:23:44 [FALCON] [ERROR] GET /3.1/lists/XXXX/archivers => Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/falcon/app.py", line 361, in __call__ responder(req, resp, **params) File "/usr/lib/python3.8/site-packages/mailman/rest/lists.py", line 405, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3.8/site-packages/zope/component/_api.py", line 152, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3.8/site-packages/zope/interface/registry.py", line 354, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 619, in __init__ exists = store.query(ListArchiver).filter( File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3467, in one_or_none raise orm_exc.MultipleResultsFound( sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/archivers HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.2" Did this one list get corrupted somehow? I'm running GNU Mailman 3.3.4 (Tom Sawyer) in Docker containers on Debian Stretch. Emails to that list are not getting processed. I'm not out of disk space. Anything I should check? Thank you, Seth

2 1

Pkl files with ".last" extension
by Keith Christian July 12, 2024

July 12, 2024

In the MM2 to MM3 migration project I'm involved with, I see files with names like config.pkl.last along with config.pkl. Is there a special reason for the ".last" extension and if so, what is it? Thanks, -------- Keith

2 2

bulk deletion of messages from Hyperkitty
by Danil Smirnov July 12, 2024

July 12, 2024

Hi, community! After importing from Mailman 2, thousands of badly compiled messages from the past appeared with empty content on the same date (date of import). Is there a safe way to delete them all? If we delete them from the database - hyperkitty_email table - do we need to do some clean-up of hyperkitty_thread table as well? Any advice? BR, Danil Smirnov

4 5

Hyperkitty stuck files
by zoltan＠circle-interactive.co.uk July 11, 2024

July 11, 2024

Hi, I have a mailman3 setup in venv with python 3.11.2 mailman 3.3.9 mailman-hyperkitty 1.2.1 I feel I have read a lot about issues with stucked files in spool directory still I am not able to proceed with debugging in my case. Ideas would be welcome and appreciated. Thanks This is the error in archiver.log Jul 09 10:56:12 2024 (47531) HyperKitty archiver processing queued filebase: 1720522497.980487+a88492922feca24ced15594a5ec16556195 6f3ad Jul 09 10:56:12 2024 (47531) hyperkitty archiver: sending message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/archive: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> (500) Jul 09 10:56:12 2024 (47531) Could not archive the message with id <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) archiving failed, re-queuing (mailing-list act.lists.contextualscience.org, message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com>) Jul 09 10:56:12 2024 (47531) Exception in the HyperKitty archiver: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Jul 09 10:56:12 2024 (47531) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html>

3 8

Postfix SMTP REJECT non-subscribers
by Matthew Blissett July 11, 2024

July 11, 2024

Hi, With Mailman 2, I have configuration and scripts to reject non-members from posting to lists _during the SMTP connection_. This is better than bouncing (no backscatter), better than discarding messages (the user finds out) and better than moderation (spammy messages aren't forwarded to external email systems). The configuration and scripts are described here: https://code.launchpad.net/~jimpop/mailman/check_subscriber Is anything like this built-in to Mailman 3? I cannot find it in Gitlab. Thanks, Matt

3 3