- Mailman-users - lists.mailman3.org

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

An issue with the postfix_domains directory creation and the mailman start command.
by Keith Christian July 10, 2024

July 10, 2024

From Mark's reply of Jul 5, 2024, 3:18 PM: RE: The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. 1 [mailman3@somehost ~]$ ./venv/bin/mailman start 2 Starting Mailman's master runner 3 Generating MTA alias maps 4 [mailman3@somehost ~]$ sudo ls -l /opt/mailman3/mm/var/data/postfix_domains 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': No such file or directory 6 [mailman3@somehost ~]$ ls -dl /opt/mailman3/mm/var/data/ 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 /opt/mailman3/mm/var/data/ What should I do about lines 4-7? Thought it might be a permissions issue but it's owned by the correct user. Not sure that i missed any steps, suggestions appreciated.

4 8

Dropdown problem in postorius due to bootstrap
by Greg Newby July 9, 2024

July 9, 2024

(My first post) As has been observed, the Ubuntu 24.04 LTS packaging for native Mailman3 can be challenging. I've been solving all kinds of issues, and I'm writing here about something I've so far been unable to solve. The problem: *In Postorius, dropdown menus are not working*. I.e., as a list admin you can click on a menu option like "Users" or "Mass operations," and nothing happens. As a regular user, the top-right icon to manage settings and logout does not do anything. The same behavior occurs regardless of which browser I use. The dropdown in HyperKitty works, and HyperKitty uses a different code base. In the browser developer console (Firefox & others), the error is: “Uncaught TypeError: n.createPopper is not a function.” I've dug deeply into this. The relevant <script> is bootstrap.min.js. Postorius (via django) is using version 5.3.1 via package libjs-bootstrap5: ** This is what django is using: /usr/share/bootstrap-html/js/bootstrap.bundle.min.js -- version 5.3.1, linked to: /usr/share/javascript/bootstrap5/js/bootstrap.bundle.min.js /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js Here is detail of the error from the Firefox developer console: Uncaught TypeError: n.createPopper is not a function _createPopper dropdown.js:241 show dropdown.js:139 toggle dropdown.js:121 <anonymous> dropdown.js:446 i event-handler.js:118 R event-handler.js:184 on event-handler.js:216 <anonymous> dropdown.js:444 <anonymous> bootstrap.bundle.min.js:6 <anonymous> bootstrap.bundle.min.js:6 By temporarily replacing /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js I have tried moving back to 4.6.1 (from libjs-bootstrap4). I have also retrieved the latest 5.3.1 from the CDN, which is slightly different but doesn't change the error: https://cdn.jsdelivr.net/npm/bootstrap@5.3.1/dist/js/bootstrap.bundle.min.js Here's the JavaScript section from the bottom of a sample page from my Postorius site (view-source: https://lists.ogf.org/mailman3/postorius/lists/gfsg.lists.ogf.org/held_mess… ): <script src="/mailman3/static/postorius/libs/jquery/jquery-3.6.0.min.js"></script> <script src="/mailman3/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js"></script> <script src="/mailman3/static/django-mailman3/js/main.js"></script> <script src="/mailman3/static/postorius/js/script.js" defer></script> <script> // Add the .js-enabled class to the body so we can style the elements // depending on whether Javascript is enabled. $(document).ready(function(){ $("body").addClass("js-enabled"); $(".gravatar").addClass("rounded-circle"); }); </script> I would appreciate suggestions about how to solve this problem. Thanks to everyone who is doing a great job building and supporting Mailman3. I've been using Mailman2 for a long time, and have dozens of lists on multiple servers. ~ Greg Newby

2 1

hyperkitty_import performance boosting potential
by dlb-ml＠anl.gov July 9, 2024

July 9, 2024

Our organization is moving to MM3 from MM2, and I'm at the point where I am testing importing our archives. However, many of the lists that we want to transfer over have pretty large mbox files, so it takes a significant amount of time for it to process them. I can throw all of the resources I need at it in order to make it faster, but I'm not sure if the import application is single-threaded only. Is there a way to enable a multi-threaded option? Can I safely run multiple commands at the same time using something like /usr/bin/parallel? Thanks

2 2

E-mail every minute: "Cron <www-data@sharky5> ..."
by Robert Heller July 8, 2024

July 8, 2024

What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear). I am getting an e-mail *every* minute that looks like: From www-data(a)deepsoft.com Sat Jul 6 17:38:03 2024 Return-Path: <www-data(a)deepsoft.com> X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on sharky5.deepsoft.com X-Spam-Level: X-Spam-Status: No, score=-850.0 required=5.0 tests�YES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NO_RELAYS,URIBL_BLOCKED, USER_IN_WELCOMELIST autolearn=ham autolearn_force=no version=4.0.0 X-Original-To: www-data Delivered-To: www-data(a)deepsoft.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d�epsoft.com; s�epsoft.com; t20301883; bh=qGrVTBfV1NiqgxCIzSaXwoKZ0lKxKvaK56k31yXU2Sk=; h=From:To:Subject:Date:From; b=jTml1ZF+qGkmS2tcz5kgZHjOyPxeaWIQiX1mzAF3ZfZWb0ziVLxutkcej5mGapUOq PpH6ExYM1TEipMTYQ/JRY/74vz2dEpebDrZqjyY3KakxLWiyFFEb5glmQYZGvz9wr2 e5ljD0Shku4fbRoaxO7XMQCn/fmx3+D8tI/ZPbMQReceived: by sharky5.deepsoft.com (Postfix, from userid 33) id 5257D4C1296; Sat, 6 Jul 2024 17:38:03 -0400 (EDT) From: root(a)deepsoft.com (Cron Daemon) To: www-data(a)deepsoft.com Subject: Cron <www-data@sharky5> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/var/www> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=www-data> Message-Id: <20240706213803.5257D4C1296(a)sharky5.deepsoft.com> Date: Sat, 6 Jul 2024 17:38:03 -0400 (EDT) X-Scanned-By: MIMEDefang 3.3 on 108.161.129.198 Status: R /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. And I get this output from sudo mailman-web check --no-color : System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. System check identified 14 issues (0 silenced). Again, the docs are not helpful (at least not to me). -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

5 11

Mailman 3 install questions: HAYSTACK_CONNECTIONS
by heller＠deepsoft.com July 7, 2024

July 7, 2024

I am using the debian 12 repo versions of mailman3, django, posterious, hyperkitty, and xapian: sharky5% dpkg-query -l python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} mailman3\* | grep '^ii' ii mailman3 3.3.8-2~deb12u2 all Mailing list management system ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list management system documentation ii mailman3-web 0+20200530-2.1 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django 3:3.2.19-1+deb12u1 all High-level Python web development framework ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.9-1 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-postorius 1.3.8-3 all Web user interface to access GNU Mailman3 ii python3-xapian 1.4.22-1 amd64 Xapian search engine interface for Python3 Before adding the HAYSTACK_CONNECTIONS options, I have this: sharky5% sudo mailman-web haystack_info --no-color --skip-checks Number of handled 1 index(es). - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at 0x7fd0de1b0470> When I add this to /etc/mailman3/maymail_web.py (adapted from the section titled: "Setting up Fulltext search (xapian)" on https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian HAYSTACK_CONNECTIONS = { 'default': { 'PATH': "/var/lib/mailman3/web/fulltext_index", 'ENGINE': 'xapian_backend.XapianEngine' }, } I get: File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'xapian_backend' So, do I use Xapian or not? Is something missing somewhere? Is this a documentation bug or something else? -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

2 1

Subject Munging
by Sam Darwin July 6, 2024

July 6, 2024

Hi, We have a user who is proposing that reply messages from a mailing list should be in the following format: Re: [MM3-users] Ubuntu 24.04 upgrade notes and not [MM3-users] Re: Ubuntu 24.04 upgrade notes Their reason... is that mailman2, and other lists, used to do it that way. I myself am agnostic about the difference, and probably prefer to keep things the way mailman3 recommends. The questions are: 1. What could be explained to the user to convince them the new method is preferable. 2. Can this be customized with a Setting? (Not that we will end up modifying it. Just curious). Thanks.

3 3

Mailman 3, postfix domains, and postgresql cannot authenticate user
by Keith Christian July 5, 2024

July 5, 2024

--------------------------------------------------------------------------- First issue:Postfix v3.5.8 on RHEL 8. The below is from journalctl -xe: --------------------------------------------------------------------------- Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or directory I manually created the var_dir: /opt/mailman3/mm/var directory specified in the mailman.cfg file. How do I find out how to populate the postfix_domains.db files, and the postfix_lmtp.db file? --------------------------------------------------------------------------- Second issue: Postgresql authentication. PostgreSQL v10.23. --------------------------------------------------------------------------- I have this in the active mailman3.cfg file, where xxxxxxxxxx is the same complex password in the mailman3 config file: url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 Same password when I created the mailman3 and mailman3web users: create role mailman3 with encrypted password 'xxxxxxxxxx '; create role mailman3web with encrypted password 'xxxxxxxxxx '; psycopg2.OperationalError: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: Ident authentication failed for user "mailman3" --------------------------------------------------------------------------- Contents of the "live" mailman.cfg file, from "mailman info" --------------------------------------------------------------------------- (venv) [mailman3@someserver ~]$ cat -n /opt/mailman3/var/etc/mailman.cfg 1 # /opt/mailman3/mailman.cfg 2 [paths.here] 3 var_dir: /opt/mailman3/mm/var 4 5 [mailman] 6 layout: here 7 # This address is the "site owner" address. Certain messages which must be 8 # delivered to a human, but which can't be delivered to a list owner (e.g. a 9 # bounce from a list owner), will be sent to this address. It should point to 10 # a human. 11 site_owner: user(a)example.com 12 13 [database] 14 class: mailman.database.postgresql.PostgreSQLDatabase 15 ##### url: postgresql://mailman:MYPASSWORD@localhost/mailman 16 # ---------------------------------------------------------------------------------- 17 # Changed: Fri Jun 28 11:56:02 EDT 2024 18 url: postgresql://mailman3:xxxxxxxx@localhost/mailman3/mailman3 19 # Changed: Fri Jun 28 11:56:02 EDT 2024 20 # ---------------------------------------------------------------------------------- 21 22 [archiver.prototype] 23 enable: yes 24 25 # For the HyperKitty archiver. 26 [archiver.hyperkitty] 27 class: mailman_hyperkitty.Archiver 28 enable: yes 29 configuration: /opt/mailman3/mailman-hyperkitty.cfg 30 31 [shell] 32 history_file: $var_dir/history.py 33 34 [mta] 35 incoming: mailman.mta.postfix.LMTP 36 outgoing: mailman.mta.deliver.deliver 37 lmtp_host: 127.0.0.1 38 lmtp_port: 8024 39 smtp_host: localhost 40 smtp_port: 25 41 configuration: python:mailman.config.postfix 42 verp_confirmations: yes 43 verp_personalized_deliveries: yes 44 verp_delivery_interval: 1 Suggestions appreciated for how to fix the postfix_domains files, and the postgres authentication isssue. ------------- Keith

3 5

Ubuntu 24.04 upgrade notes
by Andrew Hodgson July 3, 2024

July 3, 2024

Hi. Just thought I would write up my installation experiences on Ubuntu 24.04 following this guide as much as possible: Virtualenv Installation - Mailman Suite 3.3 documentation (mailman3.org)<https://docs.mailman3.org/en/latest/install/virtualenv.html> Ubuntu packages: I'm trying not to install dev packages on the server if possible and managed to get away with the following packages: python3-psycopg2 sassc lynx python3-venv python3-certbot-nginx postgresql exim4-daemon-light Creating the venv: python3 -m venv --system-site-packages --symlinks venv This creates the venv referencing the system packages as well which is useful as some of the dependencies for Mailman are met by the Certbot and python3-psycopg2 packages. Using Pip I installed the following packages: pip install mailman mailman-hyperkitty mailman-web Postgres: I ran into an issue with the database after running `mailman-web migrate`. This was because a newer version of Django pulled in from the above command needed some tables creating in the public schema, and from Postgres 15 (Ubuntu ships with Postgres 16) that isn't allowed by default. I solved this by making the Mailman role owner of the mailman database. I am aware of discussions around whether its best to do this or give explicit perms on the databases to allow all on the public schema, but I decided to go with this option. My Postgres commands are now: sudo -u postgres psql create database mailman; create user mailman with encrypted password '[...]'; ALTER DATABASE mailman OWNER TO mailman; Django: I ran into an issue with a newer Django installation not allowing any form submission, was getting a 403 returned due to CSRF protection failure. I resolved this by adding this line to my local Settings.py: CSRF_TRUSTED_ORIGINS=['https://lists.domain.com'] I moved back to using Gunicorn for the backend server, the instructions on this were spot on. I've had this error before but the mailman-web compilemessages command failed because of missing msgfmt. I think I can pull this in from Ubuntu packages but may need to update installation docs with this extra package requirement. Search: I continued to use Woosh as I'm running a very low traffic site and that is what comes with Mailman-Web as part of package requirements. Thanks for the good support as always guys. Andrew.

1 0

Mailman Ubuntu 24.04 install notes
by Andrew Hodgson July 1, 2024

July 1, 2024

Hi. Just thought I would write up my installation experiences on Ubuntu 24.04 following this guide as much as possible: Virtualenv Installation - Mailman Suite 3.3 documentation (mailman3.org)<https://docs.mailman3.org/en/latest/install/virtualenv.html> Ubuntu packages: I'm trying not to install dev packages on the server if possible and managed to get away with the following packages: python3-psycopg2 sassc lynx python3-venv python3-certbot-nginx postgresql exim4-daemon-light Creating the venv: python3 -m venv --system-site-packages --symlinks venv This creates the venv referencing the system packages as well which is useful as some of the dependencies for Mailman are met by the Certbot and python3-psycopg2 packages. Using Pip I installed the following packages: pip install mailman mailman-hyperkitty mailman-web Postgres: I ran into an issue with the database after running `mailman-web migrate`. This was because a newer version of Django pulled in from the above command needed some tables creating in the public schema, and from Postgres 15 (Ubuntu ships with Postgres 16) that isn't allowed by default. I solved this by making the Mailman role owner of the mailman database. I am aware of discussions around whether its best to do this or give explicit perms on the databases to allow all on the public schema, but I decided to go with this option. My Postgres commands are now: sudo -u postgres psql create database mailman; create user mailman with encrypted password '[...]'; ALTER DATABASE mailman OWNER TO mailman; Django: I ran into an issue with a newer Django installation not allowing any form submission, was getting a 403 returned due to CSRF protection failure. I resolved this by adding this line to my local Settings.py: CSRF_TRUSTED_ORIGINS=['https://lists.domain.com'] I moved back to using Gunicorn for the backend server, the instructions on this were spot on. I've had this error before but the mailman-web compilemessages command failed because of missing msgfmt. I think I can pull this in from Ubuntu packages but may need to update installation docs with this extra package requirement. Search: I continued to use Woosh as I'm running a very low traffic site and that is what comes with Mailman-Web as part of package requirements. Thanks for the good support as always guys. Andrew.

1 0

Held messages showing a reason not in English on the Postorious
by Alan KT So (ITSC) June 27, 2024

June 27, 2024

We just notice a held message from a user's list showing the held reason in Ukrainian, but the interface is in US English and the list's preferred language is English (USA). We could not repeat the issue. What can be the reason behind? [cid:image001.png@01DAC7B9.AF2B0400] ___________________________________________ 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.

3 2

A poll: "Delete this thread"
by Sam Darwin June 26, 2024

June 26, 2024

Hi, If you have a locally installed mailman3 instance, could you try (as an administrator) to visit a thread in Hyperkitty and click "Delete this thread"? Does the thread get deleted, and you return to "Recently active discussions" and everything is fine? Even just a few replies would indicate a pattern. That it's usually ok, for example. I get a spinning wheel, and "Thread matching query does not exist." HyperKitty==1.3.9, PostgreSQL, Ubuntu 22.04, memcached, gunicorn.

5 7

Problem with digests not being sent daily
by Mark June 24, 2024

June 24, 2024

Hi, I have a problem with digests not being sent daily (periodically). Mailman 3.3.9 installed in virtualenv Enable Digests = YES Send Digest Periodically = YES Digest size threshold = 0 Cron is set and is running. An error report (below) is generated and emailed. The last line in the error report says "FileNotFoundError: [Errno 2] No such file or directory ...". Setting the list's folder to 777 didn't help. Any clues on where to start looking for a solution would be greatly appreciated. Thanks, Mark /////////////////////////////////////// CRON IS SET: /////////////////////////////////////// su mailman (venv) mailman:/$ crontab -e ... 5 6 * * * /opt/mailman/venv/bin/mailman digests --periodic ... /////////////////////////////////////// CRON RUNS: /////////////////////////////////////// # tail -100 /var/log/cron.log ... 2024-06-21T06:05:01.815948+00:00 deu CRON[3105464]: (mailman) CMD (/opt/mailman/venv/bin/mailman digests --periodic) ... /////////////////////////////////////// ERROR REPORT EMAILED BY CRON: /////////////////////////////////////// Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/commands/cli_digests.py", line 126, in digests maybe_send_digest_now(mlist, force=True) File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/app/digests.py", line 106, in maybe_send_digest_now os.rename(mailbox_path, mailbox_dest) FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/mm/var/lists/LISTNAME.LISTDOMAIN/digest.mmdf' -> '/opt/mailman/mm/var/lists/LISTNAME.LISTDOMAIN/digest.252.14.mmdf' ////////////////////////////////////////////////////////////////////////////////

3 14

unique key violation because of case sensitivity of email address
by Jörg Schulz June 16, 2024

June 16, 2024

After updating to the most recent version of mailman-web, the migrations script issued an error: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Traceback (most recent call last): mailman-web | File "/usr/lib/python3.12/site-packages/django/db/backends/utils.py", line 89, in _execute mailman-web | return self.cursor.execute(sql, params) mailman-web | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mailman-web | psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "account_emailaddress_user_id_email_987c8728_uniq" mailman-web | DETAIL: Key (user_id, email)=(27, John.Doe(a)mynicedomain.de) already exists. mailman-web |(...) Digging into the db, I found the duplicate to result from a duplicate entry using john.doe(a)mynicedomain.de Obviously, the process that originally created the entry, took case sensitivity literally which doesn't seem to be the case any longer for the migration script. I fixed this by removing one of the duplicates hoping no further errors will come up.... What would have been the better approach?

2 1

running a script for the mailman-shell (to discard held messages) gives errors about a package argument for relative import
by stephan.edel＠gmx.net June 16, 2024

June 16, 2024

Our organization has been been communicating through about a dozen mailing lists, running on mailman, with ~200 subscribers, for 15-odd years. After Debian 10 LTS ran out, I had to upgrade our organisations Debian server, forcing me into mailman3. I haven't managed, yet, to get the web interface running, so I need to do the most urgent tasks in the shell for now. I have found out that, for example, to discard all held messages from the list "motor", I need to > sudo -u list mailman shell -l motor.our-server.de and in the shell, >>> from mailman.app.moderator import handle_message >>> rdb = IListRequest(m) >>> for req in rdb.held_requests: ... if req.request_type == RequestType.held_message: ... handle_message(m, req.id, Action.discard) > commit() Now, obviously, I put these exact lines in a script, so I don't have to type it out every single time, and try to run it using > sudo -u list mailman shell -l testlist.our-server.de -r ./mm_discard_held.py but that invariably gives me ------------------------ Traceback (most recent call last): File "/usr/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'mailman')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/commands/cli_withlist.py", line 294, in shell r = call_name(dotted_name, m, *run_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/__init__.py", line 121, in import_module raise TypeError(msg.format(name)) TypeError: the 'package' argument is required to perform a relative import for './mm_discard_held' ------------- I've tried a PYTHONPATH=/root/bin , where mm_discard_held.py lives, as suggested. I've tried moving it to the path where the mailman binary lives, as suggested. I always get the same result. What else can I do? Thank you.

2 1

mailman3 on Rocky 9 is not starting after an OS update and reboot
by dgoldsmith＠sans.org June 12, 2024

June 12, 2024

We are running mailman 3.x in a venv setup using Postgresql. The mailman service hangs during startup and eventually fails with a timeout: # systemctl status mailman3 × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) Active: failed (Result: timeout) since Wed 2024-06-12 13:35:23 UTC; 11s ago Process: 1205 ExecStart=/opt/mailman/venv/bin/mailman start (code=killed, signal=TERM) CPU: 1.019s Jun 12 13:33:53 <hostname> systemd[1]: Starting GNU Mailing List Manager... Jun 12 13:35:23 <hostname>systemd[1]: mailman3.service: start operation timed out. Terminating. Jun 12 13:35:23 <hostname> systemd[1]: mailman3.service: Failed with result 'timeout'. Jun 12 13:35:23 <hostname> systemd[1]: Failed to start GNU Mailing List Manager. Jun 12 13:35:23 <hostname> systemd[1]: mailman3.service: Consumed 1.019s CPU time. Searching I found some similar reports where it seemed to be an issue with a stale .lck lock file. But on our system: - /var/lib/mailman is empty - /opt/mailman/mm/var/locks is empty The last entries in /opt/mailman/mm/var/logs/mailman.log is: 2024-06-12 09:23:44 -0400] [2101411] [INFO] Handling signal: term Jun 12 13:23:44 2024 (2101395) Master watcher caught SIGTERM. Exiting. [2024-06-12 13:23:44 +0000] [2101451] [INFO] Worker exiting (pid: 2101451) Jun 12 09:23:44 2024 (2101412) retry runner caught SIGTERM. Stopping. [2024-06-12 13:23:44 +0000] [2101450] [INFO] Worker exiting (pid: 2101450) Jun 12 09:23:44 2024 (2101408) nntp runner caught SIGTERM. Stopping. [2024-06-12 09:23:48 -0400] [2101411] [INFO] Shutting down: Master Jun 12 13:23:50 2024 (2101395) Master stopped Any help would be appreciated. Postgres appears to be up., Postfix is up, nginx is up. The web UI gives me the error: Something went wrong Mailman REST API not available. Please start Mailman core. Running "mailman version" hangs for a long time and then returns: $ mailman version GNU Mailman 3.3.9 (Tom Sawyer) Running "mailman status" hangs for a long time and then returns: $ mailman status GNU Mailman is not running What other logs can be checked for more detail? What possible services or file/dir permissions may have had something changed by the OS updates? Thanks, David Goldsmith

3 2

Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)
by Mark Sapiro June 11, 2024

June 11, 2024

On 6/6/24 11:22 AM, Marcus Bautze wrote: > Hi, > > Sorry, that was a wrong information in my mail . I already changed the base url to your suggestion as I wrote the mail (and forgot to change it in the mail) but i‘m getting the same error :-( I have some questions. At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "Thank you, archiver is now starting. Now there's another problem:". Does this mean messages are being archived in HyperKitty or are they accumulating in (I think the Debian path is) /var/lib/mailman/archives/hyperkitty/spool/? At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py and this are the same Keys." To be clear, in mailman-web.py the key is quoted and in mailman-hyperkitty.cfg it is not. E.g., in mailman-hyperkitty.cfg api_key: Some_key and in mailman-web.py MAILMAN_ARCHIVER_KEY = 'Some_key' What are your versions for mailman-hyperkitty and HyperKitty? HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 and if I recall corectly, at least one Debian package was shipped with this incompatibility -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues
by Keith Christian June 10, 2024

June 10, 2024

Hello, mailman list: Trying to add the mailman3.service unit so that mailman3 will start on system boots/reboots. Seeing different behavior with the mailman3.service unit commands vs. with the "/opt/mailman3/venv/bin/mailman" command line. Everyone on this list is more experienced than I with reading systemd error messages and Python code, so your ideas are appreciated. I am using letters and numbers to navigate the six screenshots in this email, I hope this is helpful, without being too much info. Running the following OS and Python versions. Mailman was installed with "pip install wheel mailman psycopg2-binary" per the virtual environment instructions: (venv) [keithchristian@localhost ~]$ cat /etc/redhat-release AlmaLinux release 9.4 (Seafoam Ocelot) (venv) [keithchristian@localhost ~]$ python3 -V Python 3.9.18 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- To begin: here is the current mailman3.service unit file, taken from the "Starting Mailman automatically" portion of: https://docs.mailman3.org/en/latest/install/virtualenv.html, with all /opt/mailman/ paths set to /opt/mailman3/ for my sandbox system. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- A 1 [mailman3@localhost ~]$ cat /etc/systemd/system/mailman3.service A 2 [Unit] A 3 Description=GNU Mailing List Manager A 4 After=syslog.target network.target postgresql.service A 5 A 6 [Service] A 7 Type=forking A 8 PIDFile=/opt/mailman3/mm/var/master.pid A 9 User=mailman3 A 10 Group=mailman3 A 11 ExecStart=/opt/mailman3/venv/bin/mailman start A 12 ExecReload=/opt/mailman3/venv/bin/mailman restart A 13 ExecStop=/opt/mailman3/venv/bin/mailman stop A 14 A 15 [Install] A 16 WantedBy=multi-user.target ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Below in line B-6, systemd thinks mailman isn't running, but with the "/opt/mailman3/venv/bin/mailman" commands, line B-2 says it is. I could be misinterpreting the systemd output, however. Python not happy about some directories. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- B 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman status B 2 GNU Mailman is running (master pid: 10004) B 3 [mailman3@localhost ~]$ systemctl status mailman3.service B 4 mailman3.service - GNU Mailing List Manager B 5 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) B 6 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 7min ago B 7 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) B 8 CPU: 762ms B 9 B 10 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist B 11 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) B 12 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs B 13 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) B 14 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs B 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) B 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' B 17 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE B 18 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. B 19 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Below, we stop mailman with the command line and check status with systemd. C-1, C-2, show stopped. I'd think systemctl status should show stopped but it doesn't. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- C 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman stop C 2 Shutting down Mailman's master runner C 3 [mailman3@localhost ~]$ systemctl status mailman3.service C 4 mailman3.service - GNU Mailing List Manager C 5 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) C 6 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 8min ago C 7 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) C 8 CPU: 762ms C 9 C 10 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist C 11 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) C 12 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs C 13 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) C 14 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs C 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) C 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' C 17 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE C 18 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. C 19 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Below, we start mailman, the "/opt/mailman3/venv/bin/mailman" command line works, D-1 through D-5. Line D-6, the systemd status command (erroneously) shows otherwise. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- D 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman start D 2 Starting Mailman's master runner D 3 Generating MTA alias maps D 4 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman status D 5 GNU Mailman is running (master pid: 10457) D 6 [mailman3@localhost ~]$ systemctl status mailman3.service D 7 mailman3.service - GNU Mailing List Manager D 8 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) D 9 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 10min ago D 10 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) D 11 CPU: 762ms D 12 D 13 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist D 14 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) D 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs D 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) D 17 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs D 18 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) D 19 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' D 20 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE D 21 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. D 22 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------------- E 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman status E 2 GNU Mailman is running (master pid: 10457) E 3 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman stop E 4 Shutting down Mailman's master runner E 5 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman start E 6 Starting Mailman's master runner E 7 Generating MTA alias maps E 8 [mailman3@localhost ~]$ systemctl status mailman3.service E 9 mailman3.service - GNU Mailing List Manager E 10 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) E 11 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 2h 21min ago E 12 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) E 13 CPU: 762ms E 14 E 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist E 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) E 17 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs E 18 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) E 19 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs E 20 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) E 21 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' E 22 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE E 23 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 24 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 25 [mailman3@localhost ~]$ systemctl stop mailman3.service E 26 ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ==== E 27 Authentication is required to stop 'mailman3.service'. E 28 Multiple identities can be used for authentication: E 29 1. keith christian (keithchristian) E 30 2. mailman3 E 31 Choose identity to authenticate as (1-2): 2 E 32 Password: E 33 ==== AUTHENTICATION COMPLETE ==== E 34 [mailman3@localhost ~]$ systemctl status mailman3.service E 35 mailman3.service - GNU Mailing List Manager E 36 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) E 37 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 2h 21min ago E 38 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) E 39 CPU: 762ms E 40 E 41 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist E 42 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) E 43 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs E 44 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) E 45 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs E 46 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) E 47 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' E 48 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE E 49 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 50 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 51 [mailman3@localhost ~]$ systemctl start mailman3.service E 52 ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ==== E 53 Authentication is required to start 'mailman3.service'. E 54 Multiple identities can be used for authentication: E 55 1. keith christian (keithchristian) E 56 2. mailman3 E 57 Choose identity to authenticate as (1-2): 2 E 58 Password: E 59 ==== AUTHENTICATION COMPLETE ==== E 60 Job for mailman3.service failed because the control process exited with error code. E 61 See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details. E 62 [mailman3@localhost ~]$ journalctl -xeu mailman3.service|tail -20 E 63 Defined-By: systemd E 64 Support: https://wiki.almalinux.org/Help-and-Support E 65 E 66 An ExecStart= process belonging to unit mailman3.service has exited. E 67 E 68 The process' exit code is 'exited' and its exit status is 1. E 69 Jun 08 11:58:52 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 70 Subject: Unit failed E 71 Defined-By: systemd E 72 Support: https://wiki.almalinux.org/Help-and-Support E 73 E 74 The unit mailman3.service has entered the 'failed' state with result 'exit-code'. E 75 Jun 08 11:58:52 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 76 Subject: A start job for unit mailman3.service has failed E 77 Defined-By: systemd E 78 Support: https://wiki.almalinux.org/Help-and-Support E 79 E 80 A start job for unit mailman3.service has finished with a failure. E 81 E 82 The job identifier is 9400 and the job result is failed. E 83 E 84 [mailman3@localhost ~]$ journalctl -xeu mailman3.service|grep -a "Jun 08 11:5[0-9]:[0-9][0-9]" E 85 Jun 08 11:58:51 localhost.localdomain systemd[1]: Starting GNU Mailing List Manager... E 86 Jun 08 11:58:52 localhost.localdomain mailman[11160]: Traceback (most recent call last): E 87 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/bin/mailman", line 33, in <module> E 88 Jun 08 11:58:52 localhost.localdomain mailman[11160]: sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) E 89 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1157, in __call__ E 90 Jun 08 11:58:52 localhost.localdomain mailman[11160]: return self.main(*args, **kwargs) E 91 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1077, in main E 92 Jun 08 11:58:52 localhost.localdomain mailman[11160]: with self.make_context(prog_name, args, **extra) as ctx: E 93 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 943, in make_context E 94 Jun 08 11:58:52 localhost.localdomain mailman[11160]: self.parse_args(ctx, args) E 95 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1644, in parse_args E 96 Jun 08 11:58:52 localhost.localdomain mailman[11160]: rest = super().parse_args(ctx, args) E 97 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1408, in parse_args E 98 Jun 08 11:58:52 localhost.localdomain mailman[11160]: value, args = param.handle_parse_result(ctx, opts, args) E 99 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2400, in handle_parse_result E 100 Jun 08 11:58:52 localhost.localdomain mailman[11160]: value = self.process_value(ctx, value) E 101 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2362, in process_value E 102 Jun 08 11:58:52 localhost.localdomain mailman[11160]: value = self.callback(ctx, self, value) E 103 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/bin/mailman.py", line 95, in initialize_config E 104 Jun 08 11:58:52 localhost.localdomain mailman[11160]: initialize(value) E 105 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 228, in initialize E 106 Jun 08 11:58:52 localhost.localdomain mailman[11160]: initialize_1(config_path) E 107 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 122, in initialize_1 E 108 Jun 08 11:58:52 localhost.localdomain mailman[11160]: mailman.config.config.load(config_path) E 109 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 141, in load E 110 Jun 08 11:58:52 localhost.localdomain mailman[11160]: self._post_process() E 111 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 163, in _post_process E 112 Jun 08 11:58:52 localhost.localdomain mailman[11160]: self.ensure_directories_exist() E 113 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist E 114 Jun 08 11:58:52 localhost.localdomain mailman[11160]: makedirs(directory) E 115 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs E 116 Jun 08 11:58:52 localhost.localdomain mailman[11160]: os.makedirs(path, mode) E 117 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs E 118 Jun 08 11:58:52 localhost.localdomain mailman[11160]: mkdir(name, mode) E 119 Jun 08 11:58:52 localhost.localdomain mailman[11160]: PermissionError: [Errno 13] Permission denied: '//var/templates' E 120 Jun 08 11:58:52 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE E 121 Jun 08 11:58:52 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 122 Jun 08 11:58:52 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 123 [mailman3@localhost ~]$ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- For the PermissionError: [Errno 13] Permission denied: '//var/templates' in Line E-119 above, every /var/tamplates directory except the last one has write permissions for mailman3, I doubt that the "/home/keithchristian/var/templates directory" had been tried. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- F 1 1716996947 drwxr-xr-x. 2 mailman3 mailman3 6 May 29 09:35 /opt/mailman3/var/templates F 2 1716999414 drwxr-xr-x. 2 mailman3 mailman3 6 May 29 10:16 /opt/mailman3/mailman_install_documentation_edits/var/templates F 3 1717774226 drwxr-xr-x. 2 mailman3 mailman3 6 Jun 7 09:30 /opt/mailman3/venv/var/templates F 4 1717779523 drwxr-xr-x. 2 keithchristian keithchristian 6 Jun 7 10:58 /home/keithchristian/var/templates ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- END OF MAILMAN INSTALL ISSUES SCREENSHOTS -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

5 6

Email to list owner on list creation only sent when using mailman create --notify command
by Perry Kollmorgen June 10, 2024

June 10, 2024

Hi, This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. Is there an option to include a notify option when using mailmanclient or the API direct perhaps ? Or even maybe a way to trigger a notification manually at some point once the list is completely setup including both short and long descriptions ? Thank you. Regards, Perry

2 2

Digests not working correctly
by Joel Lord June 8, 2024

June 8, 2024

So I seem to have problems with both periodic AND size-triggered digests. Size first, this is simpler. Just got one sent out, clearly triggered by a new email getting added to the queued up messages, but the setting for the list is the default 30KB and the digest came out at 23.2 KB. Is it measuring the accumulated queue as size on disk including metadata and filesystem block sizes or something, rather than the size of what the emailed digest will be? Periodic is much more complicated, even to explain. I have the cron job running nightly at 11:00 PM and it certainly seems to be working, except for one really odd thing. The list also definitely has periodic digests enabled in the web UI. This is a very bursty list, so it will go mad with traffic for a few weeks and then will go mostly idle for a month or so. The first digest of a burst is definitely size-triggered, but pretty reliably it has the last few messages from the previous burst in there. So the one I got today had three messages from today and one message from May 4th. But that May 4th message should have gone out at 11:00 PM on May 4th with the daily digest and then gotten flushed from the pending digest queue, right? -- Joel Lord

3 14

Using the API to create nonmembers with a different moderation action than the list default
by Perry Kollmorgen June 8, 2024

June 8, 2024

Hi, My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. When using the mailmanclient python bindings I have worked out I can add nonmembers with something like: mailing_list.add_role('nonmember', 'nonmember(a)yourdomain.com', display_name='Non Member') However I can't see anything in the mailmanclient docs which suggest it is possible to configure a member_moderation_action or moderation_action field for that member. I assume I'll need to fall back to using the REST API directly, and most likely something along these lines: 1/ Obtain the member ID for an email address of someone who already been added as a nonmember. 2/ Patch an endpoint which looks something like: /members/{member_id} I'm not able to use the mailman binary (e.g mailman shell) on the mailman-core host itself as I would like to query an existing database of people and reach out to a mailman endpoint from the database host rather than opening that host up to further network access. I figured it might be a good stage in which to ask for a little help and pointers before I continue, perhaps there is something I have missed for a better way to approach this. Thanks. Regards, Perry

3 4

Trying to save a new style
by Perry Kollmorgen June 7, 2024

June 7, 2024

Dear Mailman-users list, I have embarked on project to stand up a Mailman3 instance for general staff email announcements and a small number of adhoc lists. I have a fair amount up and working using Docker and Postfix, with generally emails to/from lists working well, as well as the web interface. One of the reasons I've used Mailman3 is the API and mailman shell options which I'm slowly trying to wrap my head around, but having some progress. I have a question for the moment on something which has stumped me, and whilst I may have more questions as I continue on this implementation, I am hopeful someone can point out where I am going wrong on this. Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> >>> >>> from zope.interface import implementer >>> from mailman.interfaces.styles import IStyle >>> @implementer(IStyle) ... class TestStyle: ... name = 'AB-Announce-Style' ... description = 'AB Announce mailing list style.' ... def apply(self, mailing_list): ... mailing_list.admin_immed_notify = true ... mailing_list.admin_notify_mchanges = true ... mailing_list.advertised = false ... mailing_list.allow_list_posts = false ... mailing_list.anonymous_list = false ... mailing_list.archive_policy = "private" ... mailing_list.archive_rendering_mode = "markdown" ... mailing_list.collapse_alternatives = false ... mailing_list.convert_html_to_plaintext = false ... mailing_list.default_member_action = "defer" ... mailing_list.default_nonmember_action = "hold" ... mailing_list.digest_send_periodic = false ... mailing_list.digests_enabled = false ... mailing_list.emergency = false ... mailing_list.include_rfc2369_headers = true ... mailing_list.max_message_size = 40000 ... mailing_list.max_num_recipients = 30 ... mailing_list.member_roster_visibility = "moderators" ... mailing_list.send_goodbye_message = true ... mailing_list.send_welcome_message = true ... mailing_list.subscription_policy = "moderate" ... mailing_list.unsubscription_policy = "moderate" ... >>> manager.register(TestStyle()) >>> >>> commit() >>> >>> for style in manager.styles: ... print(style.name) ... AB-Announce-Style legacy-announce legacy-default private-default So at this point the style has been registered, however it doesn't look to save this permanently. When I quit the shell and log back in, it only shows the original 3 styles. Nor can I see the style from the web interface. Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> Is there a way to save this style permanently ? Thank you for any assistance you can provide. Regards, PerryK

3 2

Mailman3 memory footprint
by Marc SCHAEFER June 6, 2024

June 6, 2024

Hello, It seems the mailman & mailman-web memory footprint are somewhat big. It looks a lot of instances are started. I have seen this: https://gitlab.com/mailman/mailman/-/issues/1050 and added this to the end of /etc/mailman3/mailman-web.py: Q_CLUSTER = { 'workers': 2, 'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5, } However, it does not seem to really reduce the memory footprint. Any other suggestions? Thank you.

2 1

Mailman3 doesn't send Mails to users (Debian12 with Plesk)
by marcus＠mbautze.de June 6, 2024

June 6, 2024

Hello, i already send this question to the plesk-forum but it seems that nobody there can help me :-( After updating from Debian 10 to 11 to 12, I now have mailman3 running on my server I then converted all lists from Mailman2 to Mailman3 following the instructions from mailman. I can access it via the web interface, manage everything etc. When I register on the web interface, I also receive the corresponding mails from Mailman (forgotten password...) Mails are also arriving, at least mails that are not allowed go into the mails to be approved. The problem, however, is that it does not send out any mails, nor do they appear in the archive. When I look in the Mailman-Log I find: May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost [Errno 111] Connection refused May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: [Errno 111] Connection refused The configuration of Mailman.cfg looks like this: incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 In Mailman manuals I find hints that the transport routes have to be added to the Postfix-config. Doesn't Debian/Plesk do this automatically? Does anyone else have an idea what I need to change to get my mails out? I did the conversion from mailman2 to mailman3 with root because it didn't work with "sudo -u list "m, but the files stored in the file system all belong to list, so that shouldn't be the problem.

9 25

Sending to mangled 'From' addresses.
by hansen June 5, 2024

June 5, 2024

All, Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. For example, say the mail client captures my address as “Allan Hansen via <listname>” <listaddress> then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: “Allan Hansen via <listname>” and, to make it worse, the actual email address, <listaddress>, is often hidden. The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., "Allan Hansen via <listname>" In other words, filtering is done on the name part of the recipient, not the address part. Should I get onto the other list to request this as an enhancement? Yours, Allan

3 3

Sign and encrypt e-mail responses
by Markus Grandpré June 4, 2024

June 4, 2024

Dear List, is it possible to sign and encrypt all e-mail responses from the Mailman3 server with a digital certificate? Best regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

3 3

Recently active discussions - Hyperkitty
by Sam Darwin June 4, 2024

June 4, 2024

Hi, Sometimes not sure if it's preferable to open a gitlab issue, or chat on the mailing list. I have run a large archive import into mailman3/hyperkitty. After that's done, waited a day, for scheduled cron jobs to complete. In "All Threads", all the email archives are present. The import worked. In "RECENTLY ACTIVE DISCUSSIONS" on the main page, it says: RECENTLY ACTIVE DISCUSSIONS No discussions this month (yet). Nothing there. That means if I direct users to visit the site, the page, it appears empty. That's too bad. :-) It should display recent emails. What would affect this feature during an archive import? Is it a problem with the import script itself, or with a scheduled cron job, or something else? Would you expect "Recently active discussions" be empty when very recent archives do exist? Thanks, Sam

3 7

import21 detailed usage instructions in 2024
by Keith Christian June 3, 2024

June 3, 2024

1 Soon, I will be executing the first test imports from Mailman2.1 to Mailman3.9. 2 Planning to copy over the entire production Mailman2.1 to a new directory structure on the Mailman 3.9 machine. 3 Expecting that all .mbox and .pkl files will be present and no special work has to be done to bring them over will a "full" mailman2.1 copy. 4 Can the import21 program find the mailman2.1 .mbox and .pkl files on its own and process them? 5 Other than the mailman2.1 instance being shut down, any other prep that needs to be done? 6 Any special command line parameters to be aware of for import21? 7 Is there a list of troubleshooting steps for commonly encountered migration issues? Thanks. ------------------ Keith

2 1

import21 caused a few mails to be sent out
by Marc SCHAEFER June 2, 2024

June 2, 2024

Hello, After importing a (big > 3000 subscribers) list with import21, I noticed the following: 36 mails went out from LIST-NAME-bounces to subscribers, but they apparently all bounced. Could those be subscribers that Mailman2 saw bouncing and added the appropriate flag, and Mailman3 sent a probe after the import21? I checked for one of the e-mail address and: Mailman2: - that e-mail has the [X] R flag for "noncourriel" (no delivery) Mailman3: - that e-mail is Delivery mode Regular, Bounces to 0 NB: in MM2 and MM3, all users are in Hold for moderation, that's normal. In addition, there are a few mails in /var/lib/mailman/messages for example that same user: one file, showing a bounce from a remote server. So my questions: 1) is this behaviour to "probe" already disabled addresses normal, and not "port over" the "don't deliver"? 2) why are those messages held in messages/ ? 3) should I then, before running import21, clean the MM2 installation of all those users with [X] R flag? If yes, is there a simple command? Thank you for pointers or help. PS: there was no trafic on that imported mailing-list yet, it's a test.

2 1

Mailman sending email from user@example.com
by dgoldsmith＠sans.org May 30, 2024

May 30, 2024

I have defined an additional SITE in django and the SITE_ID value in /etc/mailman3/settings.py is set to reference that site's ID value. Messages for a list being distributed that are generating certain bounce errors are resulting in email from Mailman 3.x being sent to the list owners from the address user(a)example.com. Is there something else to update in the settings files, Django or the database to make it use the list owner email address tied to the domain of the site? Thanks, David Goldsmith

1 1

Have postgresql in the mailman.cfg file but sqlite shows in the mailman info command
by Keith Christian May 29, 2024

May 29, 2024

(venv) [mailman3@localhost-live ~]$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.9.18 (main, Jan 24 2024, 00:00:00) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] config file: /opt/mailman3/mailman.cfg db url: sqlite:////opt/mailman3/var/data/mailman.db <<<---------------------------------------- devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Class and url were commented out in the mailman.cfg file, did not recognize postgresql but generated a trace (venv) [mailman3@localhost-live ~]$ grep postgresql /opt/mailman3/mailman.cfg # class: mailman.database.postgresql.PostgreSQLDatabase # url: postgresql://mailman:MYPASSWORD@localhost/mailman Uncommented class and url: class: mailman.database.postgresql.PostgreSQLDatabase <<<---------------------------------------- url: postgresql://mailman:MYPASSWORD@localhost/mailman <<<---------------------------------------- Now I get a stack trace from "mailman info" (venv) [mailman3@localhost-live ~]$ mailman info Traceback (most recent call last): File "/opt/mailman3/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1077, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 943, in make_context self.parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1644, in parse_args rest = super().parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1408, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2400, in handle_parse_result value = self.process_value(ctx, value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2362, in process_value value = self.callback(ctx, self, value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 228, in initialize initialize_1(config_path) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 122, in initialize_1 mailman.config.config.load(config_path) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 145, in load self.push(filename, user_config.read()) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 150, in push self._config.push(config_name, config_string) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 582, in push confs = self._getExtendedConfs(conf_name, conf_data) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 615, in _getExtendedConfs _parser_read_file(parser, StringIO(conf_data), conf_filename) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 49, in _parser_read_file parser.read_file(f, source) File "/usr/lib64/python3.9/configparser.py", line 718, in read_file self._read(f, source) File "/usr/lib64/python3.9/configparser.py", line 1085, in _read raise MissingSectionHeaderError(fpname, lineno, line) configparser.MissingSectionHeaderError: File contains no section headers. file: '/opt/mailman3/mailman.cfg', line: 14 <<<---------------------------------------- 'class: mailman.database.postgresql.PostgreSQLDatabase\n' Here is the complete mailman.cfg file: 1 # /etc/mailman3/mailman.cfg 2 # [paths.here] 3 # var_dir: /opt/mailman/mm/var 4 # 5 # [mailman] 6 # layout: here 7 # # This address is the "site owner" address. Certain messages which must be 8 # # delivered to a human, but which can't be delivered to a list owner (e.g. a 9 # # bounce from a list owner), will be sent to this address. It should point to 10 # # a human. 11 # site_owner: user(a)example.com 12 # 13 # [database] 14 # class: mailman.database.postgresql.PostgreSQLDatabase 15 # url: postgresql://mailman:MYPASSWORD@localhost/mailman 16 # 17 # [archiver.prototype] 18 # enable: yes 19 # 20 # # For the HyperKitty archiver. 21 # [archiver.hyperkitty] 22 # class: mailman_hyperkitty.Archiver 23 # enable: yes 24 # configuration: /etc/mailman3/mailman-hyperkitty.cfg 25 # 26 # [shell] 27 # history_file: $var_dir/history.py 28 # 29 # [mta] 30 # verp_confirmations: yes 31 # verp_personalized_deliveries: yes 32 # verp_delivery_interval: 1 33 # Ideas? Thanks.

3 2

Django administration - User permissions
by advorkin＠cs.princeton.edu May 29, 2024

May 29, 2024

Hello, I'm trying to setup users with different permissions. For example: I created a group support with an ability to hyperkitty/mailing list/Can add/change/delete/view mailing list. Unfortunately, the user still does not have an ability to create mailing lists as the option does not exist. It does work when the user is set as "Superuser status". I've also tried giving every possible "available user permissions", but it didn't make a difference. Am I missing something? Thank you!

2 4

Installing Mailman3 under a Python Virtual environment running on RHEL9
by Andy Macheta May 29, 2024

May 29, 2024

Hi, So tried, without much success, to get Postorius working on my Mailman3 server and every internet trick& tip I tried did not work so decided to take a new approach as recommended at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Used this reference: https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ would also work with Red Hat. Fell at the first hurdle with no packages available called "python3-dev" or "python3-venv" Is there anyone that has managed to install a running version of Mailman3 that has a working GUI whether it is on bare metal or Python virtual environment and if so, could they kindly let me know how they did it?? The closest I've come is a running command line version of Mailman3 which is fine for me of course but not for anyone else as they like access via web browser. Thanks in advance, Andy Macheta

4 13

Circumstances in which a subscriber is added to Pending Confirmation list
by David Owen May 28, 2024

May 28, 2024

Hi I wondered if anybody would be able to assist me in my understanding of the Pending Confirmation list, please. In our Mailman mailing list, our Member Policy settings for both Subscription Policy and Un-subscription Policy are set to Open. Therefore we don't require subscribers to confirm their subscription after they submit a request to join our mailing list. Despite this, a number of subscribers seem to be arriving in the Pending Confirmation (Subscriptions pending user confirmation) list. Others correctly arrive in the Members list, as we would expect. All subscription requests are made by the subscriber sending an email to our "join" email address with the subject "subscribe". I've looked at the settings carefully and can't seem to see any that may cause the above behaviour at any time (although I may have missed something of course). Therefore, does anybody know the circumstances in which subscribers to an open mailing list may somehow arrive in the Pending Confirmation list? If I could understand the cause(s) I could then consider ways to manage it or prevent it from happening. Our Mailman installation is hosted centrally in a large organisation so we while we can alter our mailing list's settings in Postorious, we can't alter the source code or similar, so we don't have great room for manoeuvre. Our Postorius version is 1.3.6. Thanks and regards David

1 0

FYI: "RuntimeError: command failure: /usr/sbin/postmap /opt/mailman/mm/var/data/postfix_lmtp, 1, Operation not permitted"
by Nils May 27, 2024

May 27, 2024

After mailman was running so well I was wondering if I really need the restart option in the service configuration. When I commented it out, I got this error a few weeks later: > # systemctl status mailman3 > × mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; > vendor preset: enabled) > Active: failed (Result: exit-code) since Tue 2024-05-14 00:34:37 > CEST; 1 week 6 days ago > Process: 1159 ExecStart=/opt/mailman/venv/bin/mailman start > (code=exited, status=1/FAILURE) > CPU: 6.933s > > May 14 00:34:36 SERVER.TLD mailman[1159]: return > f(get_current_context(), *args, **kwargs) > May 14 00:34:36 SERVER.TLD mailman[1159]: File > "/opt/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_control.py", > line 109, in start > May 14 00:34:36 SERVER.TLD mailman[1159]: > call_name(config.mta.incoming).regenerate() > May 14 00:34:36 SERVER.TLD mailman[1159]: File > "/opt/mailman/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", > line 136, in regenerate > May 14 00:34:36 SERVER.TLD mailman[1159]: raise > RuntimeError(NL.join(errors)) > May 14 00:34:36 SERVER.TLD mailman[1159]: RuntimeError: command > failure: /usr/sbin/postmap /opt/mailman/mm/var/data/postfix_lmtp, 1, > Operation not permitted > May 14 00:34:36 SERVER.TLD systemd[1]: mailman3.service: Control > process exited, code=exited, status=1/FAILURE > May 14 00:34:37 SERVER.TLD systemd[1]: mailman3.service: Failed with > result 'exit-code'. > May 14 00:34:37 SERVER.TLD systemd[1]: Failed to start GNU Mailing > List Manager. > May 14 00:34:37 SERVER.TLD systemd[1]: mailman3.service: Consumed > 6.933s CPU time. I can only guess that the error might be some case of very bad timing, because there shouldn't be any problem with the mentioned call. > # su mailman > (venv) mailman@SERVER:/$ /usr/sbin/postmap > /opt/mailman/mm/var/data/postfix_lmtp Usually works fine. I re-enabled the lines in the server configuration: > Restart=on-failure > RestartSec=15

1 0

Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)
by schaefer＠alphanet.ch May 25, 2024

May 25, 2024

Hello, I already have some success in auto-migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm), using a new container (not upgrading the existing installation, which is obsolete e.g. 32 bit x86). I am doing this using custom scripts. The idea being to be able to import most of the existing configuration and archives, let the list administrators test the new system, and progressively advertise this to users. Then, the old container will be disabled. The basic stuff works (From: domain is OK, HTTP transport works, mail go out, etc) I however bumped into the following problem: How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer? Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR. Thank you for any input.

5 5

Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?
by Keith Christian May 25, 2024

May 25, 2024

Greetings, Mailman3 List ! mailman3 was installed into the below virtual environment: (venv) [mailman3@localhost-live ~]$ pip install wheel mailman psycopg2-binary Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or any other supporting programs be installed into this virtual environment ? PostgreSQL and Postfix have been successfully installed outside of the mailman3 virtual environment and start properly, I assume this is correct. Thanks in advance. ---- Keith

4 3

Congrats & MM3 Development Plans Request - Take 2
by David Wilson May 23, 2024

May 23, 2024

Liang Liu; Congratulations on securing your Summer of Code project with MM3. As someone who is quite interested in the Mailman3 development plans, I tried to follow the link you provided but with no success. It timed out. Is that still a valid or the best link? Can you also please point me to the best source or site to get a general understanding of short and long term *MM3 development plans*, including various upcoming GSOC projects, including yours. Thank you very much in advance. Best regards. Dave Wilson ------------------------------------------------------------------------ ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: qL0JVbh9Fk99UcFT.png Replaced multipart/alternative part with first alternative.

3 2

[GSoC] Self-introduction Liu
by Liang Liu May 21, 2024

May 21, 2024

Hello everyone, I’m Liang Liu, a GSoC student this year. I will be responsible for using the publish-subscribe model to improve communication efficiency between the core and clients. The detail of this function is shown in the link below. https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202024#Support_for_RE… I am excited to learn from all of you and share my experiences. Please feel free to reach out to me for any collaboration or discussion—I am keen to contribute and learn as much as I can. Hope we have a productive summer.

1 0

List Configuration Attribute Descriptions
by steve.bachinsky＠tena-sda.org May 20, 2024

May 20, 2024

Where does one obtain a complete and concise description for all of the list configuration attributes? From the documentation, it is shown that the REST "config" interface will provide all of the attribute values associated with a particular list. But how does one find a concise description for all of these attributes? For example, I see that there is a list attribute for "default_nonmember_action" and there are two documentation pages for this attribute, but I can't find a concise description of the attribute and the permitted values. Thanks, Steve

2 1

Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it
by Keith Christian May 20, 2024

May 20, 2024

The path to the mailman3.py file is: /home/mailman3/mailman/src/mailman/bin/mailman.py I created a mailman3 user, then, set the ownership on all directories and files in /home/mailman3 and below to mailman3:mailman3. When trying to run the "mailman info" command to verify that that mailman3 can start, I get this error: File "/home/mailman3/mailman/src/mailman/bin/mailman.py", line 22 in <module> from mailman.command.cli_help import help as help command Not sure what is going on here, help greatly appreciated.

3 4

When QQ email sends emails to the Mailman service set up by oneself, members of the list who use QQ email cannot receive the emails, and it shows that the emails are rejected.
by rqchen＠cnic.cn May 11, 2024

May 11, 2024

When QQ email sends emails to the Mailman service set up by oneself, members of the list who use QQ email cannot receive the emails, and it shows that the emails are rejected.

2 3

cnic-20240510
by 陈汝祈 May 10, 2024

May 10, 2024

cnic-20240510

1 0

Change Dmark settings via command line
by bob B May 8, 2024

May 8, 2024

I need to set all the DMARC settings on are lists to "replace from with list address". Is there an easy want to do this via cli? I could do it by viewing the web interface but we have a lot of lists.

4 9

Deleting A List
by Odhiambo Washington May 4, 2024

May 4, 2024

I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. I can see from Django Admin UI that the archives are still intact. I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke Is there a way to move the archives from the old list to the new list? -- 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]

2 6

Welcome message template errors
by Mark May 1, 2024

May 1, 2024

Hi All I'm getting errors when a custom "Welcome message" template is in place [list:user:notice:welcome]. Case: Subscribing a new user via the admin "Mass subscribe". Although the new user is successfully subscribed, a welcome message is not sent and the following error message displays on the webpage. === HTTP Error 400: HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read timeout=5) === And the site-owner receives an email with ... ==== Internal Server Error: /mailman3/lists/ DoesNotExist at /mailman3/lists/ Site matching query does not exist. Request Method: GET Request URL: http://<REDACTED-PUBLIC-IPv4-ADDRESS>/mailman3/lists/ Django Version: 4.2.11 Python Executable: /opt/mailman/venv/bin/python3 Python Version: 3.11.2 ... etc ... === Regarding the second line in the email - my thinking is that it should be looking in "/opt/mailman/mm/var/lists" and not "/mailman3/lists/". If that's right, where would I look to change that directive? If not, any other clues would be greatly appreciated. The error doesn't occur if the is no custom "Welcome message" template - ie. the user is sent the default welcome message. $ 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 REST root url: http://localhost:8001/3.1/

2 29

Re: [MM3-users off list] Re: Welcome message template errors
by Mark April 29, 2024

April 29, 2024

>> So, I'm thinking (in broad brush strokes) that if I'm stuck with this >> "http glitch" I could write a script to: >> >> 1. extract the text of the custom message from the database, >> 2. write that message text to a file >> 3. update the templates.uri entries to replace the >> http://localhost... with file:///path/to/file >> 4. cron the script to run every few minutes. >> >> It screams of utter clunk I know... > but it would work. > > Note that this may not be as big an issue as it seems. It doesn't > affect all templates, for example list:member:digest:footer, > list:member:digest:header, list:member:digest:masthead, > list:member:regular:footer, list:member:regular:header and > list:member:generic:footer are only used by the `out` runner when > sending messages, so these aren't affected. Right. Affected are all the "list:user:notice:***" (eg. goodbye, hold, reject,...) > > I'm still trying to determine what the issue is. To this end can you > tell me what Python version your Mailman uses and what is the output > from `pip freeze` with your venv active? $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] $ pip freeze aiosmtpd==1.4.4.post2 alembic==1.13.1 arrow==1.3.0 asgiref==3.7.2 atpublic==4.0 attrs==23.2.0 authheaders==0.16.2 authres==1.2.0 blessed==1.20.0 certifi==2023.11.17 cffi==1.16.0 charset-normalizer==3.3.2 click==8.1.7 cmarkgfm==2024.1.14 cryptography==42.0.1 defusedxml==0.7.1 Django==4.2.11 django-allauth==0.60.1 django-appconf==1.0.6 django-compressor==4.4 django-extensions==3.2.3 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.12 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 dkimpy==1.1.5 dnspython==2.5.0 docutils==0.20.1 falcon==3.1.3 filelock==3.13.1 flufl.bounce==4.0 flufl.i18n==5.0.2 flufl.lock==8.0.2 greenlet==3.0.3 gunicorn==21.2.0 HyperKitty==1.3.9 idna==3.6 lazr.config==3.0 lazr.delegates==2.1.0 mailman==3.3.9 mailman-hyperkitty==1.2.1 mailman-web==0.0.9 mailmanclient==3.3.5 Mako==1.3.0 MarkupSafe==2.1.4 mistune==3.0.2 networkx==3.2.1 nh3==0.2.15 oauthlib==3.2.2 packaging==23.2 passlib==1.7.4 postorius==1.3.10 psutil==5.9.8 psycopg2-binary==2.9.9 publicsuffix2==2.20191221 pycparser==2.21 Pygments==2.17.2 PyJWT==2.8.0 python-dateutil==2.8.2 python3-openid==3.2.0 pytz==2023.3.post1 rcssmin==1.1.1 readme-renderer==42.0 redis==3.5.3 requests==2.31.0 requests-oauthlib==1.3.1 rjsmin==1.2.1 robot-detection==0.4 six==1.16.0 SQLAlchemy==2.0.25 sqlparse==0.4.4 types-python-dateutil==2.8.19.20240106 typing_extensions==4.9.0 urllib3==2.1.0 wcwidth==0.2.13 Whoosh==2.7.4 xapian @ file:///opt/mailman/xapian-1.4.24-cp311-cp311-linux_aarch64.whl xapian-haystack==3.1.0 zope.component==6.0 zope.configuration==5.0 zope.event==5.0 zope.hookable==6.0 zope.i18nmessageid==6.1.0 zope.interface==6.1 zope.schema==7.0.1

1 0

Mailman with Python 3.12
by Andrew Hodgson April 26, 2024

April 26, 2024

Hi. What's the latest on Mailman with Python 3.12? Looking at Ubuntu 24.04 upgrade plans and realised it comes with Python 3.12. Ubuntu are shipping Mailman packages from Debian so not sure if they have made any changes to make Python 3.12 work. I don't use those packages myself. Andrew.

3 3

mailman3-web and the django middleware problem
by Thomas Stein April 26, 2024

April 26, 2024

Howdy! I'm trying to migrate an aged mailman3 installation from ubuntu 20.04 to ubuntu 22.04. Fresh install of mailman3-web gives me: Creating config file /etc/dbconfig-common/mailman3-web.conf with new version creating database mailman3web.db: success. verifying database mailman3web.db exists: success. Creating config file /etc/mailman3/mailman-web.py with new version /usr/lib/python3/dist-packages/django_q/conf.py:174: UserWarning: Retry and timeout are misconfigured. Set retry larger than t imeout,failure to do so will cause the tasks to be retriggered before completion.See https://django-q2.readthedocs.io/en/maste r/configure.html#retry for details. warn( Traceback (most recent call last): File "/usr/bin/django-admin", line 33, in <module> sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', 'django-admin')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 416, in execute django.setup() File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 124, in populate app_config.ready() File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line 15, in ready raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE dpkg: error processing package mailman3-web (--configure): installed mailman3-web package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: mailman3-web needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) I've already seen this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… ...but that does not get me anywhere. Could someone please push me in the right direction? cheers! t.

4 12

Slow performance when listing members on Postorius
by Alan So April 24, 2024

April 24, 2024

We are about to upgrade to Mailman core 3.3.9 and Postorius 1.3.10. We notice that for setup with large number of members, the performance is much slower when listing members on web (Postorius). Further troubleshooting show that there are quite a number of API calls which do not appear in Mailman core 3.3.5 and Postorius 1.3.6 when we list members. [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/33a6266d0a04472c8d5d6c78869a964c/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/7a18b7cb90a34ac98881a3f01b5488d1/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/61c6c3e2aaf443babd3bd191519b0424/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/8dd681165b8c436fac6793cae1ed2c27/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" Further tests showing that each database query using "_member_id" in table member can take as much as 0.3 to 0.5 seconds for some large installations. The default 25 members per page mean that it will take at least 7.5 to 12.5 seconds. Changing to 200 members per page will take even longer time. We wonder whether "_member_id" should be indexed just like most other id in the database mailman_core in order to solve the issue. Or are there any other workarounds? +----------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | _member_id | char(32) | YES | | NULL | | | role | int(11) | YES | MUL | NULL | | | list_id | varchar(255) | YES | MUL | NULL | | | moderation_action | int(11) | YES | | NULL | | | address_id | int(11) | YES | MUL | NULL | | | preferences_id | int(11) | YES | MUL | NULL | | | user_id | int(11) | YES | MUL | NULL | | | bounce_score | int(11) | YES | | NULL | | | last_bounce_received | datetime | YES | | NULL | | | last_warning_sent | datetime | YES | | NULL | | | total_warnings_sent | int(11) | YES | | NULL | | +----------------------+--------------+------+-----+---------+----------------+

1 1

Change config to create a new list with all archives off
by Tibor Molnar April 21, 2024

April 21, 2024

Can archiving be changed anywhere in mailman3 configs, so then all new lists created do not archive by default?

5 8

Mailman 3 hosting query
by Bill Robertson April 18, 2024

April 18, 2024

Hi I'm investigating the possibility of transferring a fairly small mailing list I own from Google Groups to MM3 via a hosting service. I'd appreciate any pointers regarding what I should be looking out for with companies that offer this service It also seems very hard to find out which hosting companies are worth considering (In particular, reliability and support are important) Any help much is much appreciated Thanks

4 5

Is there a way to find out when a user subscribed to a list
by Mohsen Masoudfar April 17, 2024

April 17, 2024

Hi, We need to find out when a specific user joined a list. Is there a way to get this information? Thanks!

3 2

Mailman-web stop responding.
by Paul Rubin April 17, 2024

April 17, 2024

I was trying to administrate a list and discovered that mailman-web was unresponsive. I have tried stopping and restarting it. The error logs update for the startup, but not when anything connects to localhost:8000. The last entry in uwsgi.log was two hours ago and nothing has been added since. I tried both lynx http://localhost:8000 and telnet to http://localhost 8000 and GET request instantly closes the port and logs nothing. As far as I can tell both mailman and postgres are working fine. This is what logs on startup. ==> uwsgi-error.log <== *** Starting uWSGI 2.0.22 (64bit) on [Sun Apr 14 10:45:51 2024] *** compiled with version: 13.2.1 20230912 [revision b96e66fd4ef3e36983969fb8cdd1956f551a074b] on 05 October 2023 13:37:28 os: Linux-6.5.4-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 20 05:07:04 UTC 2023 (fdd7e9e) nodename: mail.rubinsoftware.com machine: x86_64 clock source: unix detected number of CPU cores: 4 current working directory: / detected binary path: /opt/mailman/venv/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! your processes number limit is 15246 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8000 fd 8 Python version: 3.11.5 (main, Aug 31 2023, 07:57:41) [GCC] PEP 405 virtualenv detected: /opt/mailman/venv/ Set PythonHome to /opt/mailman/venv/ Python main interpreter initialized at 0x7f2c3d709d58 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 250128 bytes (244 KB) for 4 cores *** Operational MODE: preforking+threaded *** added /etc/mailman3/ to pythonpath. WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x7f2c3d709d58 pid: 16064 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 16064) spawned uWSGI worker 1 (pid: 16065, cores: 2) spawned uWSGI worker 2 (pid: 16067, cores: 2) [uwsgi-daemons] spawning "/opt/mailman/venv/bin/mailman-web qcluster" (uid: 72 gid: 67) 14:45:52 [Q] INFO Q Cluster white-green-ten-mobile starting. 14:45:52 [Q] INFO Process-1:1 ready for work at 16072 14:45:52 [Q] INFO Process-1:2 ready for work at 16073 14:45:52 [Q] INFO Process-1:3 monitoring at 16074 14:45:52 [Q] INFO Process-1 guarding cluster white-green-ten-mobile 14:45:52 [Q] INFO Process-1:4 pushing tasks at 16075 14:45:52 [Q] INFO Q Cluster white-green-ten-mobile running. What should I do to diagnose further?

4 5

ModuleNotFoundError: No module named 'xapian_backend'
by Ron / BCLUG April 17, 2024

April 17, 2024

I had a working mailman3, tore it down, switched to PostgreSQL (from MySQL), and now everything is working, except: mailman-web update_index and mailman-web update_index_one_list They fail with: ModuleNotFoundError: No module named 'xapian_backend' I rebuilt and re-installed xapian: (venv) mailman@mail:~$ echo $XAPIAN_VERSION 1.4.25 (venv) mailman@mail:~$ pip list | grep -i xapian xapian 1.4.25 Any ideas? Thanks! rb

2 1

mailman3 digest sending questions and also adding docker to the mix
by bob B April 17, 2024

April 17, 2024

So I have been down the digest rabbit hole. So to confirm my assumptions/findings: Digest size threshold---- means when the total size of held messages hits this setting, a digest is sent Digest Volume Frequency. ---- specifies when the digest volume number gets incremented for digest messages, IT DOES NOT send out digests based on the setting, daily, weekly ... So what does the GUI setting "Send Digest Periodically yes no" do? how periodically does it send digests, if this is set to yes? If I want to send a digest out for a list every day, or every week, how do I set that, especially in the docker environment? Is this something that can be configured in the GUI and configured by each of my list admins? I found that ”'mailman digests --periodic' via cron” should be set in googling, but does that mean I have to do a cron job for any list that wants a scheduled digest sent? My use case is, that I have a list admin who set a size threshold, but regardless of that, they also want their list digest sent out daily, they thought it was the "Digest Volume Frequency" setting but that is not correct. However in their testing they are not getting daily digest, they are getting digests only when the threshold is reached, BUT they have "Send Digest Periodically" set to "yes" and "Enable Digests" is set to "yes"

7 17

hyperkitty.lib.utils Failed to update the fulltext index
by Ben Harris April 13, 2024

April 13, 2024

hello there, i migrated to a new host last night and i've been getting this error from a cronjob mail every minute. anyone have any ideas what would cause this? ERROR 2019-04-17 14:26:33,056 27205 hyperkitty.lib.utils Failed to update the fulltext index: ord() expected a character, but string of length 0 found Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/hyperkitty/lib/utils.py", line 186, in run_with_lock fn(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/hyperkitty/search_indexes.py", line 87, in update_index update_cmd.update_backend("hyperkitty", "default") File "/usr/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 276, in update_backend last_max_pk=max_pk) File "/usr/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update backend.update(index, current_qs, commit=commit) File "/usr/lib/python2.7/dist-packages/haystack/backends/whoosh_backend.py", line 178, in update self.setup() File "/usr/lib/python2.7/dist-packages/haystack/backends/whoosh_backend.py", line 126, in setup self.index = self.storage.open_index(schema=self.schema) File "/usr/lib/python2.7/dist-packages/whoosh/filedb/filestore.py", line 176, in open_index return indexclass(self, schema=schema, indexname=indexname) File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 421, in __init__ TOC.read(self.storage, self.indexname, schema=self._schema) File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 632, in read check_size("int", _INT_SIZE) File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 626, in check_size sz = stream.read_varint() File "/usr/lib/python2.7/dist-packages/whoosh/filedb/structfile.py", line 191, in read_varint return read_varint(self.read) File "/usr/lib/python2.7/dist-packages/whoosh/util/varints.py", line 102, in read_varint b = ord(readfn(1)) thanks, ben

5 8

Error -- postorius Un-handled exception
by Mark April 12, 2024

April 12, 2024

Hi All, I've just installed MM3 on a fresh Debian 12 using the Virtualenv method. (venv)...$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Postorius Version 1.3.10 After creating a couple of lists, the lists are shown in the table on the "Mailing lists" webpage as they should, but clicking on any of the listnames returns an error page: Something went wrong HTTP Error 500: {"title": "500 Internal Server Error"} And the Mailman log is a mystery to me, and no error is reported in the Nginx log ... # tail -f /opt/mailman/web/logs/mailmanweb.log ERROR 2024-01-24 05:41:46,327 51799 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/views/generic/base.py", line 103, in view return self.dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/postorius/views/generic.py", line 76, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/views/generic/base.py", line 142, in dispatch return handler(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/postorius/views/list.py", line 359, in get and 'hyperkitty' in archivers # noqa: W504 ^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen _collections_abc>", line 780, in __contains__ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server Error: /postorius/lists/testing.example.com/ ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server Error: /postorius/lists/testing.example.com/ Could anyone steer me in the right direction for fixing this? Thanks, Mark

6 20

Sibling lists in Mailman3
by Markus Grandpre April 10, 2024

April 10, 2024

Dear list, after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or something similar) in Mailman3. How are sibling lists treated in Mailman3? Thank you in advance for your answers. Best Markus -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

4 5

Requesting help with a turnkey mailman installation
by biobee7＠gmail.com April 7, 2024

April 7, 2024

Hello Everyone! If you can install mailman turnkey on my server - email me biobee7(a)gmail.com

2 1

Warning on EL8: django-mailman 1.3.12 prefers Django 4.2 which requires Maria DB>10.4
by Jered Floyd April 4, 2024

April 4, 2024

A heads-up for anyone else on RHEL 8, because the error is mystifying. django-mailman 1.3.12 bumps the preferred django version from 4.1 to 4.2. Django 4.2 requires MariaDB 10.4 or later. RHEL 8 has full lifecycle support for MariaDB 10.3. For some reason I haven't yet been able to identify, this causes pyMySQL integrations to fail with the mysterious error: django.core.exceptions.ImproperlyConfigured: mysqlclient 1.4.3 or newer is required; you have 1.4.6. (Yes, Database.version_info contains "(1, 4, 2, 'final', 0)" while Database.version contains "1.4.6" and I am totally stumped where that 1.4.2 is coming from as it appears... nowhere.) Bypassing that error check gives the more informative: django.db.utils.NotSupportedError: MariaDB 10.4 or later is required (found 10.3.39). Doing a pip install with django\<4.2 works. This is not ideal since 4.1 is past LTS, so I would recommend that Mailman systems be migrated to RHEL 9. --Jered

1 1

Question: What happens if I delete a user from all lists and that user is sole owner of some list?
by David Partain April 3, 2024

April 3, 2024

Hi, One of the great things about our new installation compared with our old is the ability to manage users via https://our.wee.domain/postorius/users I might have been able to manage them using the command line on the old installation, but there is no 'mailman delmembers' on that box. Since I now have this Mighty Power, I want to use it to clean up. There are many users who should no longer be on the system, so I want to run something along the lines of: mailman delmembers --member some(a)email.address --fromall \ --no-goodbye-msg --no-admin-notify or, if I'm feeling brave, something like this. mailman delmembers --file somefile --fromall \ --no-goodbye-msg --no-admin-notify My question is: If one of these users is the sole owner of a list, what will happen? Will the user be deleted and that list now owner-less? Will mailman refuse to delete that user until I add a new owner? Thanks in advance for your feedback. Cheers, David

3 4

Help with mailman2 to mailman3 archive migration
by francisco.lopezayuso＠sib.swiss April 2, 2024

April 2, 2024

Hello all, I'm having some issues with a migration I'm performing right now from our old mailman2 server to a mailman3 one. The mailing lists imports work fine, but the archives seems to work sometimes: This means that some lists archives appear but others are missing when browsing the archives in the web UI. This happens despite the command line telling me that the import went fine. Here are the steps I run for the archives: # Copy the archives into the my new server # Cleaning old archives, where $LIST is my mailing list name $ /opt/mailman3/venv/lib/python3.11/site-packages/hyperkitty/contrib/check_hk_import /opt/mailman3/archives/private/"$LIST".mbox/"$LIST".mbox $ /opt/mailman3/venv/lib/python3.11/site-packages/hyperkitty/contrib/cleanarch3 /opt/mailman3/archives/private/"$LIST".mbox/"$LIST ".mbox # Importing the archives $ mailman-web hyperkitty_import -l "$LIST(a)my.domain.com" /opt/mailman3/archives/private/"$LIST".mbox/"$LIST".mbox # Indexing the new archive $ mailman-web update_index_one_list "$LIST(a)my.domain.com" Here is also an example log of an archive I'm migrating that does not appear in the UI, for reference (list and domain were renamed for privacy): $ mailman-web hyperkitty_import -l my_list(a)domain.com --since=1900-01-01 /opt/mailman3/archives/private/my_list.mbox/my_list.mbox Importing from mbox file /opt/mailman3/archives/private/my_list.mbox/my_list.mbox to my_list(a)domain.com Computing thread structure Synchronizing properties with Mailman Adding admin as owner of MailingList: my_list.lists.domain.com 2070 emails left to refresh, checked 1000 2070 emails left to refresh, checked 2000 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 my_list(a)domain.com'. $ mailman-web update_index_one_list my_list(a)domain.com Indexing 22 emails Any help would be greatly appreciated, I'm very lost here... Cheers,

2 1

Mailman stops processing....... where to start looking for root cause?
by bob B April 2, 2024

April 2, 2024

Today was the 2nd time mailman stopped sending out mail, it receives mail but sends nothing out. To resolve the issue I restarted the mailman services and then all the incoming/queued mail was sent out... last time this happened was 21 days ago.... Before that, it has been rock solid for years. We are running in a docker environment with no recent changes. On the host in /var/log/maillog, I see the mail coming in and going to mailman in docker. for docker, the mailman logs are in /opt/mailman/core/var/logs in /opt/mailman/core/var/logs/smtp.log ---------- I see the messages coming in /opt/mailman/core/var/logs/debug.log ------------ is empty /opt/mailman/core/var/logs/mailman.log -------------- I do not see anything that looks like it had an issue So where can I look to try to determine a cause? If it happens again, what and where can I cook to troubleshoot before restarting the service? Thanks

4 4

Seeking help completing a useful installation
by Hugh Esco March 30, 2024

March 30, 2024

I have more fully documented where I am at with this attempt to build a working installation of mm3 at this link: https://gitlab.com/mailman/django-mailman3/-/issues/73 My questions include: - the template for /etc/mailman3/mailman.cfg, defines vardir, but no DATA_DIR. See test failure #1 (closed) <http:///mailman/django-mailman3/-/issues/1>, above. Where does that want to be? Any issue with putting the mm3.db next to the mm3_web.db at /opt/mailman/mm/var/data? - there are two possible virtualenv's in my build: (a) /opt/mailman/venv/ and (b) /opt/mailman/.pyenv/. I say more about these below. Which do I want to use in this instance? I'm guessing the latter where the mailman3 libraries are published, but have doubts. The link above urges a dependency on python ^3.11, but bookworm provides only python 3.8, so I used pyenv to satisfy the requirement. It wanted to deploy to its own path, though perhaps there is some switch which would consolidate everything under /opt/mailman/venv/. I do not work with python enough to know. - attempts to run bin/mailman-web startapp mm3web fail to add any new processes to the process list. bin/mailman-web start fails with errors. What change of state to the server should I expect from running this command? How do I test for success? If startapp is the correct invocation, what argument does it want on a working installation? - having run the command in the previous point, I see nothing in the browser except for the apache starter page at the root path '/'. None of the paths defined in the apache2 configuration seem to offer any joy. I assume that uwsgi wants to proxy the requests to a running mailman-web service somehow, but that no such service is found. I see one hopeful line in the log at: /opt/mailman/mm/var/logs/mailman.log "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" - I assume that once I get apache2 wired to a running application through the uwsgi proxy, that I can proceed to create an admin user, use it to explore the web gui, and begin to consider how to migrate my legacy mm2.1 lists into the new installation. Any further help crossing the finish line would be appreciated. Thanks, -- Hugh

2 2

Disabling the footer on a mailing list: Is this how?
by David Partain March 28, 2024

March 28, 2024

Hi, I regularly get requests from users to disable footers since they use email clients that simply show an attached text file. Yes, I know that's broken. I never got this working with my old broken installation. Since we're now running a shiny new version of mailman3, I thought I'd give it a go again. From what I've read, I thought the following would do the trick: # sudo -u mailman -s /usr/bin/bash $ source /local/mailman/venv/bin/activate $ cd ~/var/templates/ $ mkdir -p lists/test-list.our.domain/en/ $ cp /dev/null "lists/test-list.our.wee.domain/en/list:member:regular:footer" However, sending mail to test-list(a)our.wee.domain<mailto:test-list@our.wee.domain> still includes the footer. What am I missing? Do I need to restart something? Did I misunderstand what I've read? With kind regards, David

2 2

See list of subscribers
by Tom Yates March 27, 2024

March 27, 2024

I'm sure I'm just doing something stupid, but I can't work out what. I have a list, as admin under "Settings" -> "List Identity" -> "Members List Visibility" I have it set to "Only Mailinglist Members". But a random subscriber, who's signed up and authenticated, when she visits the list page she sees her subscription, but no option to list the other subscribers. Is she looking in the wrong place? Do I need to open up more settings? Am I just being an idiot? Thanks for any light anyone can shed. -- Tom Yates - https://www.teaparty.net

2 2

Hyperkitty on Debian 12
by Markus Grandpre March 27, 2024

March 27, 2024

Dear list members, when following the instructions to migrate list archives from Mailman21 to Mailman3 (see [1]), I face the following problem: # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 /var/mailman21/testlist.mbox python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such file or directory and have no clue, where to find the right <manage.py> file. The command dpkg returns: # dpkg -l | grep hyperkitty ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives In </etc/mailman3/mailman-web.py> I find: INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', ... Can you please help me? Thank you in advance? Best, Markus [1] <https://docs.mailman3.org/en/latest/migration.html> -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

5 7

Topics - Tags
by Mark March 27, 2024

March 27, 2024

Hi, I'm reading the docs on "Message tagging" (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) as saying shell access is needed to: (a) enable topics, and (b) write the keywords. In Mailman 2 there is an Admin web UI for "Topics". Is there such a web UI that can be enabled in Mailman 3 so that the list owners can create topics (tags) in their lists? Thanks.

3 5

Deleting messages from HyperKitty archive
by Mark March 25, 2024

March 25, 2024

Hi, I'm running Mailman 3.3.9 with HyperKitty version 1.3.8 (venv installed as per the docs). As superuser (listmaster) I can "Delete message/thread" and "Delete archive". These options aren't there for the list owners. The docs (link below) say that in the newer HyperKitty version 1.3.9, list owners can delete messages/threads Is there a patch I can implement on HyperKitty version 1.3.8 (so list owners can delete messages), or is it possible to update HyperKitty to version 1.3.9 without bringing everything crashing down? *** https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html 1.3.9 (2024-02-27) List owners can now delete messages and threads and reattach threads. (Fixes #261) *** Thanks, Mark

2 4

Issue converting table charset to utf8mb4 on mysql
by Helio Loureiro March 24, 2024

March 24, 2024

3 3

How to fix lists with characters errors?
by Helio Loureiro March 24, 2024

March 24, 2024

Hi, I just found several lists have the issue like this regarding charset: (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members listas-charset-issue(a)mailman.domain.com anders(a)domain.com beth(a)domain.com charlie(a)domain.com david(a)domain.com ellen(a)domain.com Traceback (most recent call last): File "/local/mailman/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_members.py", line 222, in members display_members(ctx, mlist, role, regular, File "/local/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_members.py", line 109, in display_members print(f'{address.display_name} <{address.original_email}>', UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in position 9: ordinal not in range(256) Since this service is running since time of python2, I guess the old lists handled accented characters was to save as latin-1. But how can I fix this now? Note: apparently the list remains working just fine. It is just the command line failing. And perhaps some other side effect. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

2 4

Badsignature on uwsgi-error.log
by Helio Loureiro March 22, 2024

March 22, 2024

Hi, I keep receiving a lot of errors like this: --- Logging error --- Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher task = SignedPackage.loads(task[1]) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads return signing.loads( File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age)) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign result = super(TimestampSigner, self).unsign(value) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign raise BadSignature('Signature "%s" does not match' % sig) django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/logging/__init__.py", line 1100, in emit msg = self.format(record) File "/usr/lib/python3.10/logging/__init__.py", line 943, in format return fmt.format(record) File "/usr/lib/python3.10/logging/__init__.py", line 678, in format record.message = record.getMessage() File "/usr/lib/python3.10/logging/__init__.py", line 368, in getMessage msg = msg % self.args TypeError: not all arguments converted during string formatting Call stack: File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/management/commands/qcluster.py", line 22, in handle q.start() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 78, in start self.sentinel.start() File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start self._popen = self._Popen(self) File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen return _default_context.get_context().Process._Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen return Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ self._launch(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch code = process_obj._bootstrap(parent_sentinel=child_r) File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap self.run() File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 168, in __init__ self.start() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 172, in start self.spawn_cluster() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 248, in spawn_cluster self.pusher = self.spawn_pusher() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 201, in spawn_pusher return self.spawn_process(pusher, self.task_queue, self.event_out, self.broker) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 197, in spawn_process p.start() File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start self._popen = self._Popen(self) File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen return _default_context.get_context().Process._Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen return Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ self._launch(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch code = process_obj._bootstrap(parent_sentinel=child_r) File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap self.run() File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 358, in pusher logger.error(e, traceback.format_exc()) Message: BadSignature('Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match') Arguments: ('Traceback (most recent call last):\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher\n task = SignedPackage.loads(task[1])\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads\n return signing.loads(\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads\n base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age))\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign\n result = super(TimestampSigner, self).unsign(value)\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign\n raise BadSignature(\'Signature "%s" does not match\' % sig)\ndjango.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match\n',) The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY on setting.py are the same. Any clue what could be the issue? And this is on the latest mailman. > pip freeze aiosmtpd==1.4.4.post2 alembic==1.13.1 arrow==1.3.0 asgiref==3.7.2 atpublic==4.0 attrs==23.2.0 authheaders==0.16.2 authres==1.2.0 blessed==1.20.0 certifi==2024.2.2 cffi==1.16.0 charset-normalizer==3.3.2 click==8.1.7 cmarkgfm==2024.1.14 cryptography==42.0.3 defusedxml==0.7.1 Django==4.1.13 django-allauth==0.61.1 django-appconf==1.0.6 django-compressor==4.4 django-extensions==3.2.3 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.11 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 dkimpy==1.1.5 dnspython==2.5.0 docutils==0.20.1 falcon==3.1.3 flufl.bounce==4.0 flufl.i18n==5.0.2 flufl.lock==8.0.2 greenlet==3.0.3 gunicorn==21.2.0 HyperKitty==1.3.8 idna==3.6 lazr.config==3.0 lazr.delegates==2.1.0 mailman==3.3.9 mailman-hyperkitty==1.2.1 mailman-web==0.0.8 mailmanclient==3.3.5 Mako==1.3.2 MarkupSafe==2.1.5 mistune==2.0.5 mysql==0.0.3 mysqlclient==2.2.4 networkx==3.2.1 nh3==0.2.15 oauthlib==3.2.2 packaging==23.2 passlib==1.7.4 postorius==1.3.10 psutil==5.9.8 publicsuffix2==2.20191221 pycparser==2.21 Pygments==2.17.2 PyJWT==2.8.0 PyMySQL==1.1.0 python-dateutil==2.8.2 python3-openid==3.2.0 pytz==2024.1 rcssmin==1.1.1 readme-renderer==42.0 redis==3.5.3 requests==2.31.0 requests-oauthlib==1.3.1 rjsmin==1.2.1 robot-detection==0.4 six==1.16.0 SQLAlchemy==2.0.27 sqlparse==0.4.4 types-python-dateutil==2.8.19.20240106 typing_extensions==4.9.0 urllib3==2.2.0 uWSGI==2.0.24 wcwidth==0.2.13 Whoosh==2.7.4 xapian @ file:///local/mailman/xapian-1.4.23-cp310-cp310-linux_x86_64.whl zope.component==6.0 zope.configuration==5.0.1 zope.event==5.0 zope.hookable==6.0 zope.i18nmessageid==6.1.0 zope.interface==6.2 zope.schema==7.0.1 Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

4 6

need help to migrate from Mailman2 to Mailman3 (french if possible)
by pascalleval＠yahoo.fr March 22, 2024

March 22, 2024

Hello everybody, I'm trying to migrate my mailing lists on Debian 11 server from Mailman2 to Mailman3, and I'm having difficulties ! Mailman3 is already functional, but I could not configurate Postfix for this. Is there anyone speaking french that could help me ? Thanks in advance.

4 5

ValueError: The ADMINS setting must be a list of 2-tuples.
by David Partain March 21, 2024

March 21, 2024

Greetings, We're trying to move from an ancient and bad Ubuntu-package based installation of mailman3 to a venv-based do-it-the-right-way installation. # mailman --version GNU Mailman 3.3.9 (Tom Sawyer) Things seem much better than past migration attempts. We are, though, seeing tons of errors in uwsgi-error.log that look like this: Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/wsgi.py", line 131, in __call__ response = self.get_response(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 140, in get_response response = self._middleware_chain(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 58, in inner response = response_for_exception(request, exc) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 144, in response_for_exception log_response( File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 241, in log_response getattr(logger, level)( File "/usr/lib/python3.10/logging/__init__.py", line 1506, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.10/logging/__init__.py", line 1624, in _log self.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 1634, in handle self.callHandlers(record) File "/usr/lib/python3.10/logging/__init__.py", line 1696, in callHandlers hdlr.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 968, in handle self.emit(record) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 128, in emit self.send_mail(subject, message, fail_silently=True, html_message=html_message) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 131, in send_mail mail.mail_admins( File "/local/mailman/venv/lib/python3.10/site-packages/django/core/mail/__init__.py", line 124, in mail_admins raise ValueError("The ADMINS setting must be a list of 2-tuples.") ValueError: The ADMINS setting must be a list of 2-tuples. Our ADMINS setting in /etc/mailman3/settings.py has ADMINS = ( ('Mailman Suite Admin', 'someone(a)our.domain', 'someoneelse(a)our.domain'), ) Can someone point me in a direction to correct this? Thanks in advance. David

3 4

mailman3 3.2.2 python3.8 problem on focal
by Thomas Stein March 21, 2024

March 21, 2024

Hello list! I saw a few posts regarding the "Uncaught runner exception: module 'time' has no attribute 'clock'" problem but no solution to that. It seems this issue sneaked in at some point. I was getting aware of it when suddenly notifications to non-member posts did not work anymore. Everything else seems still to work. So, what is the prefered solution here? Is it possible to "repair" focal? There is python2.7, python3.6 and python3.8 installed currently. Or do I need to switch to a supported distribution like debian something? Wait for ubuntu 24.04? Any hints are really appreciated. cheers! t.

2 3

SpamAssassin and clamav?
by Marisa Giancarla March 16, 2024

March 16, 2024

Is there a way to have mm3 use SpamAssassin and/or clamav? Marisa

3 3

How to disable global templates for all lists
by christopher.claus＠tgcamberg1848.de March 14, 2024

March 14, 2024

Hallo togeher, I´m using the docker version from maxking and mailman core-version 3.3.9. I was wondering why there were messages in the list with "non-configured" footers. I found the files > mailman-core:/opt/mailman# find / -name "*list:member:*" /usr/lib/python3.11/site-packages/mailman/templates/de/list:member:generic:footer.txt /usr/lib/python3.11/site-packages/mailman/templates/de/list:member:digest:masthead.txt /usr/lib/python3.11/site-packages/mailman/templates/ca/list:member:generic:footer.txt /usr/lib/python3.11/site-packages/mailman/templates/ca/list:member:digest:masthead.txt /usr/lib/python3.11/site-packages/mailman/templates/nl/list:member:generic:footer.txt but I found no option to disable them. How can I disable these global list-configuration? Best regards, chrclaus

3 2

outgoing messages not sent in a busy loop
by Igor Serebryany March 13, 2024

March 13, 2024

incoming messages are showing up in hyperkitty but not going out as emails to list members. i've tried enabling the following debug logging: format: %(asctime)s (%(process)d) %(message)s datefmt: %b %d %H:%M:%S %Y propagate: no level: info path: mailman.log [logging.smtp] level: DEBUG [logging.smtp-failure] level: DEBUG [logging.runner] level: DEBUG [logging.debug] level: debug [logging.smtp-failure] level: debug with these options, if i run `tail -f *` in the `log` directory of mailman, i get the following in essentially a busy loop: ``` ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1c9ad050> ==> debug.log <== Mar 13 19:08:46 2024 (17) [NNTPRunner] starting oneloop Mar 13 19:08:46 2024 (17) [NNTPRunner] ending oneloop: 0 Mar 13 19:08:46 2024 (18) [OutgoingRunner] finishing filebase: 1710356926.1738262+0a50dc0e393ba4de10bcdadb5376d4330f670c77 Mar 13 19:08:46 2024 (18) [OutgoingRunner] doing periodic Mar 13 19:08:46 2024 (18) [OutgoingRunner] committing transaction Mar 13 19:08:46 2024 (18) [OutgoingRunner] checking short circuit Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing filebase: 1710356926.2733445+d044aeb93be86fbf662b6e0feffc89d0f2e4eb66 Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing onefile Mar 13 19:08:46 2024 (18) [outgoing] <function deliver at 0x7fef1cda27a0>: <CADJyiOV1RAth=3CkNoHJ1qTVzedzX8BG0k6iwe019jXau30pLw(a)mail.gmail.com> ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1cb0f390> ``` which doesn't give me a lot to go on. anyone know what could be causing this or any way to get additional debug information?

2 1

Hyperkitty tracebacks: possible DB corruption?
by peter＠chubb.wattle.id.au March 13, 2024

March 13, 2024

Hi Folks, Just recently I've started seeing backtraces from Django when trying to view old threads in hyperkitty. They say that more than one LastView is being returned, and at a later date cannot delete a LastView. I'm using the Debian-packaged hyperkitty and postorius, but this code hasn't changed from upstream. The backtraces come when a logged in used revisits a thread. So I see: Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ MultipleObjectsReturned at /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ get() returned more than one LastView -- it returned 2! Then later on I see: LastView.objects.delete(pk=del_id) ^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Manager' object has no attribute 'delete' Here are the backtraces: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/thread.py", line 162, in thread_index last_view_obj, created = LastView.objects.get_or_create( File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 581, in get_or_create return self.get(**kwargs), False File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 439, in get raise self.model.MultipleObjectsReturned( and Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/2022/1/ AttributeError at /hyperkitty/list/devel(a)sel4.systems/2022/1/ 'Manager' object has no attribute 'delete' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 127, in archives return _thread_list(request, mlist, threads, extra_context=extra_context) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 173, in _thread_list LastView.objects.delete(pk=del_id)

3 6

localtime() cannot be applied to a naive datetime
by Freerk Bosscha March 12, 2024

March 12, 2024

Since yesterday I get the following error-message when I go to the webinterface: ValueError at /admin/login/ localtime() cannot be applied to a naive datetime Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Exception Type: ValueError Exception Value: localtime() cannot be applied to a naive datetime Exception Location: /usr/lib/python3/dist-packages/django/utils/timezone.py in localtime, line 207 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: vr, 1 Mrt 2024 11:52:50 +0100 Mailman info: mailman info GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman3:xxxxxxx If this issue was posted before, i'm sorry, i haven't found it: Any ideas how to solve this issue would be appreciated Environment: Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Python Version: 3.9.2 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', 'django_mailman3.lib.auth.fedora') 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: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 145. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 143. response = response.render() File "/usr/lib/python3/dist-packages/django/template/response.py" in render 106. self.content = self.rendered_content File "/usr/lib/python3/dist-packages/django/template/response.py" in rendered_content 83. content = template.render(context, self._request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py" in render 61. return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 169. with context.bind_template(self): File "/usr/lib/python3.9/contextlib.py" in __enter__ 117. return next(self.gen) File "/usr/lib/python3/dist-packages/django/template/context.py" in bind_template 246. updates.update(processor(self.request)) File "/usr/lib/python3/dist-packages/postorius/context_processors.py" in postorius 38. mailman_day=(timezone.localtime(timezone.now()).day == MAILMAN_DAY), File "/usr/lib/python3/dist-packages/django/utils/timezone.py" in localtime 207. raise ValueError("localtime() cannot be applied to a naive datetime") Exception Type: ValueError at /admin/login/ Exception Value: localtime() cannot be applied to a naive datetime

2 2

Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)
by Wikinaut March 8, 2024

March 8, 2024

Hello, I miss sadly the option of both: i) discarding the current message of a sender (not member of a closed list) ; and in the same action ii) adding this person to the whitelist, i.e. accept further mails from this sender. How can this be achieved?

3 4

Re: [Mailman-Developers] Re: Help on Gitlab
by Mark Sapiro March 8, 2024

March 8, 2024

Plese keep the thread on the list. On 3/8/24 6:36 AM, Daniel Azubuine wrote: > Sir, I get this error > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python: can't > open file '/home/daniel/Documents/repos/mailman/mailman/setup.py': > [Errno 2] No such file or directory > ERROR: invocation failed (exit code 2)/ > _______________________________________________ summary > ________________________________________________ > ERROR: qa: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python > /home/daniel/Documents/repos/mailman/mailman/setup.py --name (exited > with code 2) > when i run tox -e qa. What is your tox version (tox --version)? You shouldn't need this, but adding ``` skipdist = True ``` in the [tox] section of tox.ini may help. > I also get this when i run tox -e py310-diffcov > ------------- > src/mailman/interfaces/listmanager.py (75.0%): Missing lines 37 > ------------- > Total: 4 lines > Missing: 1 line > Coverage: 75% > ------------- > > ERROR: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/py310-diffcov/bin/diff-cover coverage.xml --fail-under=100 --compare-branch origin/master (exited with code 1) This is expected output in this case. Line 37 in your src/mailman/interfaces/listmanager.py is not covered by any tests. Modifying the test_cannot_create_a_list_twice test in src/mailman/model/tests/test_listmanager.py to use assertRaisesRegex rather than assertRaises may help. See <https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertRai…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

mm3 installation question
by advorkin＠cs.princeton.edu March 7, 2024

March 7, 2024

Hello, everyone. I just completed the initial installation by following the instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install I went with the apache/uswgi configuration. The site is up and running, but if I click Postorius, it gets redirected to https://mysite.com/postorius/lists and I get not found error message. The same goes for Lists and Archives. What did I do wrong? I've found some discussions online, but they seem to be related to a different installation, thus my confusion. Thank you!

4 10

mass unsubscribe/subscribe
by ronn.ramirez＠pge.com March 6, 2024

March 6, 2024

Hi Mailman Admins, Whenever we mass subscribe or unsubscribe more than 500+ users, we would get a "500-internal-server-error" or a timeout. Is there something we can tweak or increase to way to increase this threshold?

3 2

export/import list?
by Dave McGuire March 1, 2024

March 1, 2024

I'm migrating to a new Mailman3 instance, finally escaping a fairly old (3.1.1) and problematic distribution repo install on a Linux VM and moving to a venv install in a native SmartOS Zone. I've gotten everything running well and integrated with our (fairly complex) mail server. I'd like to begin migration of the lists on the old mm3 instance. Is there a way to export a list from one Mailman 3 instance and import it into another, on a different machine? Ideally some way to capture its settings, members, members' settings, etc? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

6 9

Migration from old server to new server failed
by Helio Loureiro March 1, 2024

March 1, 2024

Hi, So we tried to the migration following the steps: - stop mailman in the old machine (v3.1.1 from ubuntu packages) - dump DB mailman3 and mailman3web - backup /var/lib/mailman3 content On the new machine: - checkout from git the version 3.1.1 to match production and install the services - stop mailman3 and mailman3-web on the new machine - load DBs into new machine - copy content from /var/lib/mailman3 into /local/mailman/var (which means: archives/ cache/ data/ ext/ lists/ locks/ messages/ public_suffix_list.dat queue/ templates/ web/) - start mailman3 and mailman-3web - run mailman3-web migrate And I stopped here. Because it crashed. (venv) mailman@new-mailman3-server ~ (v3.1.1) [0|SIGINT]> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0003_alter_emailaddress_create_unique_verified_email... OK Applying account.0004_alter_emailaddress_drop_unique_email... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK Applying hyperkitty.0017_file_attachments... OK Applying hyperkitty.0018_threadcategory_color... OK Applying hyperkitty.0019_auto_20190127_null_description... OK Applying hyperkitty.0020_auto_20190907_1927... OK Applying hyperkitty.0021_add_owners_mods...Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) MySQLdb.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 96, in wrapped res = handle_func(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/migrate.py", line 349, in handle post_migrate_state = executor.migrate( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 252, in apply_migration state = migration.apply(state, schema_editor) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/migration.py", line 130, in apply operation.database_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/operations/fields.py", line 108, in database_forwards schema_editor.add_field( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/schema.py", line 104, in add_field super().add_field(model, field) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 636, in add_field return self.create_model(field.remote_field.through) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 447, in create_model self.execute(sql, params or None) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 199, in execute cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: File "/local/mailman/venv/lib/python3.10/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") I tried to drop the table, but then it complained about another one. I dropped all the complained tables and as result hypperkitty never started. So I went back to see why the first error happened. Any clue what to do next? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

3 8

Google Summer of Code 2024
by Stephen J. Turnbull Feb. 26, 2024

Feb. 26, 2024

Hi, everybody It's that time of year again! PSF is in GSoC 2024, I'm 99% certain PSF will accept Mailman as a suborg (don't ask about the 1%, it's embarrassing ;-). Student applications open on March 18. So ... If you have ideas for improving Mailman 3, whether misfeatures that need fixing or cool new features, please consult our ideas page https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202024 to get an idea of level of detail and style of description needed (and to see if maybe it's already there. You can send them to me if they're already formed in your mind, or send them here for input from users on requirements, or to mailman-developers(a)python.org for input on implementation feasibility and appropriateness for GSoC. If you know anybody who would be interested in participating as a contributor, please encourage them to look at us. Rules are somewhat relaxed from years ago. They still don't accept below college age, but they no longer restrict to students. They're also offering multiple period lengths from 8 to 22 weeks (stipends vary according to period and by price level in country of residence, see https://developers.google.com/open-source/gsoc/help/student-stipends) They're not as generous as a few years ago, at least for the "rich" countries (US, UK, Japan). You don't need to be an experienced coder or project manager to be a secondary mentor, just willing to communicate with the code contributor. If you're interested in being a primary or secondary mentor, the burden is likely to be "as much as you want". We rarely get more than one good application, and we have enough "default" primary mentors to cover the likely maximum number of slots we could be allocated. It would be very helpful to us and to the PSF organization administrators if you express interest and get signed up by the end of next week, but as far as I know we can add or substitute mentors at any time. Potential mentors should 1. Have a Google account (needed for step 2, and required by GSoC) 2. Sign up with Python-GSoC at https://forms.gle/coJYxhor6FAZcZfU8 3. If you have been a GSoC mentor or org admin in the past, go to https://summerofcode.withgoogle.com and accept the contributor agreement and program rules for 2024. (Definitely if you did last year, probably for 2022 the system still remembers you, and unlikely it has more memory than that.) Steve

1 0

Settings for prevention of spam obfuscation
by Richard Rosner Feb. 26, 2024

Feb. 26, 2024

Are there any settings that may help with making it easier seeing spam as spam? E.g. some mail programs, including Outlook, allow the user to set a from mail address that most mail clients will show instead of the true sender address, but the senders mail address is still present in the sender header field. While some people and companies carelessly abuse that functionality, hiding their true mail address, those bad practices also are abused my spammers and others. Does mailman have any settings that would remove any such obfuscations, e.g. in this case detect the manipulated from address and replace it with the sender address? While I do run my own spam filter, it's virtually getting harder every day to make sure you detect all spam while not having too many false positives. If it was possible to reverse at least the most obvious manipulations, that would probably already help. Also, it would make it much easier for the users to see at first glance who actually wrote an email. It's always less trustworthy if the senders address is shown as user3168(a)suspiciousdomain.gg instead of it being manipulated to say support(a)yourprovider.com.

3 8

Unable to get Postfix to bounce messages to non-existent lists
by skenny＠scss.tcd.ie Feb. 21, 2024

Feb. 21, 2024

We have Mailman working well in our environment, but there's one thing I can't seem to make happen no matter what I try. The situation is as follows: Postfix runs on on a different server than Mailman. Its main.cf says local_recipient_maps = $alias_maps transport_maps = regexp:/var/mailman-data/postfix_lmtp relay_domains = regexp:/var/mailman-data/postfix_domains The file postfix_lmtp is initially generated by Mailman (running on a different machine). A background process creates a version of the file wherein the lmtp IP address is changed to the network IP of the Mailman server, and that version is sync'd over to the Postfix server. On the latter, a typical block for a list then reads as follows (where A.B.C.D is the IP address of the Mailman server): /^some-list(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-bounces(\+.*)?(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-confirm(\+.*)?(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-join(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-leave(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-owner(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-request(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-subscribe(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-unsubscribe(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 The only problem with this is that if someone sends a message to a non-existent mailing list, Postfix nevertheless accepts the mail, and it loiters in the queue for several days before eventually being bounced back to the sender. I want to get Postfix to reject mail to non-existent mailing lists immediately. I've come up short with each variation of main.cf settings I've tried, and would greatly appreciate any advice. Many thanks Stephen Kenny

3 4

Hyperkitty is not archiving due to 405 error - GET instead of POST
by Matthias Feb. 15, 2024

Feb. 15, 2024

Hi there, I am running mailman3 on Debian 12 - latest package (GNU Mailman 3.3.8 (Tom Sawyer)). Message handling in general is working fine, but as soon as a message is released, archiving with Hyperkitty is not working, due to a 405 error: --- Feb 11 16:18:48 2024 (3479662) HyperKitty failure on http://lists.domain.tld/mailman3/hyperkitty/api/mailman/archive: (405) Feb 11 16:18:48 2024 (3479662) Could not archive the message with id <170766472771.3479669.4791049109141956450(a)otherdomain.tld> Feb 11 16:18:48 2024 (3479662) archiving failed, re-queuing (mailing-list jahrgang.domain.tld, message <170766472771.3479669.4791049109141956450(a)otherdomain.tld>) Feb 11 16:18:48 2024 (3479662) Exception in the HyperKitty archiver: Feb 11 16:18:48 2024 (3479662) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError --- When tracing this back, even the frontend Nginx server receives a get in his logs, hence I assume that hyperkitty is really creating a GET instead of a POST request? --- 217.72.204.162 - - [11/Feb/2024:16:18:48 +0100] "GET /mailman3/hyperkitty/api/mailman/archive HTTP/1.1" 405 0 "-" "python-requests/2.28.1" --- Any idea how to trace this down any further? Any help is really appreciated! Thanks, Matthias

2 2

Retrieve users from a list
by pau.baiges＠csuc.cat Feb. 11, 2024

Feb. 11, 2024

A moderator has deleted all the users from a list, is there a way to recover them?

5 6

add / remove / set moderation bit of non-members via mailman shell
by Zaheer Abbas Feb. 9, 2024

Feb. 9, 2024

I have a situation where I need to add / remove 10-20 non-members to a particular list every week and set the moderation bit to 'accept immediately (bypass other rules). I do the above via postorius because I couldn't find a way to do this via mailman shell. Can anyone help me please to achieve the above? I know how to remove all non-members via /opt/mailman/mm/bin/mailman shell -l list.example.com for nonmember in m.nonmembers.members: ... nonmember.unsubscribe() ... commit() I am just having difficulties adding the non-members and setting the moderation bit to 'Accept' Currently I am using Mailman 3.2.2 (La Villa Strangiato) and Postorius Version 1.2.4 so cant use 'postorius => settings -> message acceptance -> id_accept_these_nonmembers' -- Regards, Zaheer

2 1

Problems with mailman core translation and other details
by celi＠dieese.org.br Feb. 9, 2024

Feb. 9, 2024

Hi. We did a fresh install of the Debian Mailman 3 full package. I'd like all components to be translated into pt_BR. I downloaded the latest updated translations from weblate, which says that 100% of the project (all components) are translated. I checked and recompiled mailman.po with msgfmt without errors. I followed all instructions I saw, included the ones from the topic How to change the language in mailman3 in this list. Everything almost OK, except from the fact that none of mailman's core email messages are being translated, even though mailman.po shows the right messages. Also, strange things happen to these .po files. The web interface is almost perfect, but some messages (just some) are not correct - although the corresponding django.po appears to be OK. It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. #: templates/postorius/lists/summary.html:88 #, python-format msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the " "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" " " msgstr "" "\n" " Para se inscrever você pode enviar um e-mail com o assunto " "'subscribe' para\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " ou use o formulário abaixo:\n" What am I doing wrong? Or what can I do to make things suitable? Additional info: GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Postorius v. 1.3.4 HyperKitty v. 1.3.4 Thanx for any help

4 9

Hiding an ML from a site
by Odhiambo Washington Feb. 8, 2024

Feb. 8, 2024

I host two MLs on the same server/same MM3 instance. Under the Django Admin interface, I created two sites. I expected that each ML will belong to its own site and should not be visible on another site. On https://mm3-lists.kictanet.or.ke/mm/lists/, you can see the two lists. How do I stop the "Users" list from showing up on this site ( https://mm3-lists.kictanet.or.ke/mm/lists/) since it belongs to its own site - https://exim4u.org/mm/lists/ ? -- 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]

5 10

search this list searches more then just this list
by Marco van Tol Feb. 6, 2024

Feb. 6, 2024

Hi there, We run the following versions: mailman-core: 3.3.9 mailman-core-api: 3.1 mailman-core-python: 3.11.6 hyperkitty: 1.3.8 We have several lists on our server, I will write down a list of example list names that are good enough for the purpose of my question. xx(a)domain.tld <mailto:xx@domain.tld> yy-xx(a)domain.tld <mailto:yy-xx@domain.tld> zz-xx(a)domain.tld <mailto:zz-xx@domain.tld> When I now visit the archives for xx(a)domain.tld <mailto:xx@domain.tld> and enter a search phrase in “search this list”, the results include the other 2 lists. It looks like “search this list” searches for keyword in any listname that matches the one from "this list". Is there a way to really only search “this list” when I go to the archives for xx(a)domain.tld <mailto:xx@domain.tld>? I have tried to change the url for the results to have a ‘^’ in front of the listname, but that gives an error :-) Thanks in advance! Marco van Tol

4 23

Disable all mail capabilities
by Hope Less Feb. 2, 2024

Feb. 2, 2024

I have a decades old list that was abandoned on my server. I upgraded it to mailman3 but it never came back to life. It is causing me some grief. I want to keep the archives up but totally disable any mail capabilities. I have turned off mail for the domain but I still get 'crap' that tries to relay. I've manually tried to remove stuff from the transport tables in Postfix but I still get mail. I'm not sure where the problem lies. If I can't stop this I'll have to remove the list entirely which includes the archives. I really wish to leave the archives up. Any idea on how I can remove the mail capabilities and leave the rest? Thank You.

4 4