- Mailman-users - lists.mailman3.org

Captcha
by Paul Tomblin Nov. 10, 2026

Nov. 10, 2026

I know that the captcha guide isn't an official Mailman3 product, but I'm trying to follow the instructions on https://eu.kictanet.or.ke/~wash/mailman3-captcha-guide.html and I've gotten to the part where it says to run: `python -c " import django, os os.environ.setdefault('DJANGO_SETTINGS_MODULE','mailman_web.settings') django.setup() from django.conf import settings print('django_recaptcha in INSTALLED_APPS:', 'django_recaptcha' in settings.INSTALLED_APPS) print('CAPTCHA_SERVICE:', settings.CAPTCHA_SERVICE) "` And I'm getting the result django_recaptcha in INSTALLED_APPS: False Traceback (most recent call last): File "<string>", line 7, in <module> print('CAPTCHA_SERVICE:', *settings.CAPTCHA_SERVICE*) *^^^^^^^^^^^^^^^^^^^^^^^^* File "/opt/mailman/venv/lib/python3.13/site-packages/django/conf/__init__.py", line 104, in __getattr__ val = getattr(_wrapped, name) *AttributeError*: 'Settings' object has no attribute 'CAPTCHA_SERVICE' However, in /etc/mailman3/settings.py, I have ### CAPTCHA support CAPTCHA_SERVICE = 'recaptchaV3' RECAPTCHA_PUBLIC_KEY_V3 = '<never mind>' RECAPTCHA_PRIVATE_KEY_V3 = '<never mind>' INSTALLED_APPS += ['django_recaptcha'] # django_recaptcha's own startup system check only reads the unsuffixed # setting names below — without this alias it silently falls back to # Google's public test keys and fails checks.recaptcha_test_key_error on # every Django system check run (including mailman-web's cron jobs). RECAPTCHA_PUBLIC_KEY = RECAPTCHA_PUBLIC_KEY_V3 RECAPTCHA_PRIVATE_KEY = RECAPTCHA_PRIVATE_KEY_V3 I do see the Captcha logo on the login pages. -- Paul Tomblin

2 1

documentation for older versions?
by bulger＠baeri.org Nov. 3, 2026

Nov. 3, 2026

The version installed with pip at the moment is 3.3.10, but the only 3.3 documentation online that I can find is for 3.3.11b1. Is there a way to access the 3.3.10 version, or older versions in general?

3 4

postgresql throws SSL warnings
by IEM Network Operation Center (IOhannes m zmölnig) Nov. 3, 2026

Nov. 3, 2026

hi, today i finally migrated my mailman3 instance from Debian/bookworm to Debian/trixie, using the Debian packages of mailman3. everything worked great, and i'm now running: > Mailman Core Version: GNU Mailman 3.3.10 (Tom Sawyer) > Mailman Core API-Version: 3.1 > Mailman Core Python-Version: 3.13.5 (main, Aug 10 2026, 12:06:59) [GCC 14.2.0] the Debian packages have - python3-django-hyperkitty 1.3.12 - python3-django-postorius 1.3.13 - python3-psycopg2 2.9.10 the instance is backed by a local PostgreSQL-17 instance (17.11.0) during the upgrade, I noticed that postgresql is constantly writing warnings to its logfile, like so: > 2026-10-29 17:26:06.875 CET [171290] [unknown]@[unknown] LOG: could not accept SSL connection: EOF detected "constantly" meaning: about 4.5 times per second! or ~16400 lines per hour. this is obviously triggered by the webinterface, as the errors stop immediately if i issue a `systemctl stop mailman3-web`. it's also notable, that I do not notice any actual problems on the webinterface, including the archives (so the DB connection seems to work fine). accordingly, /var/log/mailman3/web/mailman-web.log doesn't indicate any problems. also, this issue is not something introduced by the upgrade: i got the same warnings with my old mailman3.3.8 instance with PostgreSQL-15. it's just that i noticed the errors only now. here's the relevant section (afaict) from /etc/mailman3/mailman-web.py: ~~~ DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman3web.db', 'USER': 'REDACTED', 'PASSWORD': 'REDACTED', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { }, } } ~~~ the ssl related settings in my /etc/postgresql/17/main/postgresql.conf are (these are just the defaults, i didn't change anything): ~~~ ssl = on ssl_cert_file = '/etc/ssl/certs/ssl-cert-snakeoil.pem' ssl_key_file = '/etc/ssl/private/ssl-cert-snakeoil.key' ~~~ since everything appears to work, i might ignore the issue, but since the logfiles get pretty big due to the permanent logging, i'd rather not... any ideas what is going on? -- IOhannes m zmölnig IEM network operation center https://noc.iem.at/

2 3

What are these about ?
by alain williams Nov. 3, 2026

Nov. 3, 2026

I receive several of these a day, not one an hour. • What are they ? (what do they mean) • How do I stop them ? (or should I do something with what they are telling me) This is from a Debian 13 (Trixie) machine running mailman as installed from the Debian package. TIA BTW: my earlier problems with Postorius caused by upgrading to Trixie have now been fixed by package updates. ----- Forwarded message from Cron Daemon <root(a)bf****.phcomp.co.uk> ----- Date: Mon, 02 Nov 2026 12:00:06 +0000 From: Cron Daemon <root(a)bf****.phcomp.co.uk> To: www-data(a)bf****.phcomp.co.uk Subject: Cron <www-data@bf****> [ -f /usr/bin/django-admin ] && systemctl is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly 12:00:03 [Q] INFO Enqueued [default] 20833 12:00:03 [Q] INFO Enqueued [default] 20834 12:00:03 [Q] INFO Enqueued [default] 20835 12:00:03 [Q] INFO Enqueued [default] 20836 12:00:03 [Q] INFO Enqueued [default] 20837 12:00:03 [Q] INFO Enqueued [default] 20838 12:00:03 [Q] INFO Enqueued [default] 20839 12:00:03 [Q] INFO Enqueued [default] 20840 ----- End forwarded message ----- -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

5 8

Directly confirm a superuser's email?
by Volkmar Grote Oct. 30, 2026

Oct. 30, 2026

Hi, I installed Mailman3, created a Django superuser, tried to log into the GUI, and was told there was a confirmation email being sent out. For some reason it was sent to "www-data(a)mailmans.domain", the postfix log says, not the configured email of "my-name(a)my.organisation", and ended in the bin since that user does not accept emails. Is there a way to create a "pre-confirmed" superuser without that email being sent? Or to manually confirm it on the command line? That would be quicker than brooding over the configuration files for another couple of hours. Thanks in advance Volkmar

2 2

Moving lists to different server and domain
by Julian Kippels Oct. 29, 2026

Oct. 29, 2026

Hi, I want to move all my lists to another server. While I am doing that, I also want to change all lists from listname(a)domain.tld to listname(a)lists.domain.tld How would I best go about this? Will I have issues with the archives of the lists when the domain changes? Thanks in advance, Julain

4 6

which mailman3 containers to use?
by Thing Oct. 24, 2026

Oct. 24, 2026

Hi, Is maxking/docker-mailman still the recommended container deployment for a new Mailman 3 installation in 2026? I am building a PoC on RHEL 10 using rootless Podman, with MariaDB running externally on the host (for now to ease backup issues). The repository appears somewhat inactive and its example compose file uses maxking/mailman-core:0.4 and maxking/mailman-web:0.4. Are these images still maintained and suitable for a new deployment, or is another container image or installation method now recommended? regards Steven

5 7

does users/find do a join with addresses?
by bulger＠baeri.org Oct. 20, 2026

Oct. 20, 2026

In the REST API, users/find is supposed to match on email or display_name (at least). When the user is linked to an address, that works. But when I unlink the address, the same query returns no results. If I get all users I can see that the user record still exists. Is there an inner join or some other kind of internal dependency at play here?

2 1

list archives bleeding across domains.
by Hugh Esco Oct. 16, 2026

Oct. 16, 2026

I launched a mailman installation a couple of days ago, `pip list and `cat /etc/os-release` output reproduced below. It hosts six domains and a handful of lists for most of them. My issue is that lists archives are being linked across domain names for annonymous user, and I fear probably for users who are logged in as well. I get it that one domain's news list is supposed to be public, but does it have to be listed on the page for each domain? Can't it be listed for anonymous users ONLY IF they browse to its domain? My settings_local.py includes: FILTER_VHOST = True SITE_ID = 0 I have another reason (MAILMAN_ARCHIVER_KEY is working) to believe that my settings_local.py file is being read into the configuration. Any advice? All help is appreciated. Thanks, -- Hugh Esco ((mm3) ) list@lists02:~$ cat /etc/os-release PRETTY_NAME="Ubuntu 24.04.5 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04.5 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=noble LOGO=ubuntu-logo list@lists02:~$ . /opt/local/mm3/bin/activate ((mm3) ) list@lists02:~$ mailman --version GNU Mailman 3.3.9 (Tom Sawyer) ((mm3) ) list@lists02:~$ mailman-web --version 4.2.30 ((mm3) ) list@lists02:~$ pip list Package Version ------------------- ----------- aiosmtpd 1.4.6 alembic 1.20.0 asgiref 3.12.1 atpublic 9.0.0 attrs 26.1.0 authheaders 0.16.3 authres 1.2.0 certifi 2026.7.22 cffi 2.1.1 charset-normalizer 3.5.2 click 8.5.0 comrak 0.0.16 cryptography 50.0.2 defusedxml 0.7.1 Django 4.2.30 django-allauth 65.19.7 django-appconf 1.2.0 django_compressor 4.6.0 django-extensions 4.1 django-gravatar2 1.4.5 django-haystack 3.4.0 django-mailman3 1.3.15 django-picklefield 3.4.0 django-q2 1.10.0 djangorestframework 3.17.2 dkimpy 1.1.8 dnspython 2.9.0 docutils 0.23 falcon 4.4.0 flufl.bounce 6.0.0 flufl.i18n 8.0.0 flufl.lock 10.0.0 greenlet 3.5.6 gunicorn 26.2.0 HyperKitty 1.3.12 idna 3.20 lazr.config 4.0.0 lazr.delegates 4.0.0 mailman 3.3.9 mailman-hyperkitty 1.2.1 mailman-web 0.0.9 mailmanclient 3.3.5 Mako 1.4.3 MarkupSafe 3.0.4 mistune 3.3.4 networkx 3.7 nh3 0.3.7 oauthlib 4.0.0 packaging 26.3 passlib 1.7.4 pip 26.2.1 postorius 1.3.13 psutil 7.2.2 psycopg2-binary 2.9.13 publicsuffix2 2.20191221 pycparser 3.11 Pygments 2.21.0 PyJWT 2.15.1 python-dateutil 2.9.0.post0 python-gettext 5.0 python3-openid 3.2.0 rcssmin 1.3.0 readme_renderer 46.0 requests 2.34.2 rjsmin 1.3.0 robot-detection 0.4 six 1.17.0 SQLAlchemy 2.0.54 sqlparse 0.6.0 typing_extensions 4.16.0 urllib3 2.8.0 uWSGI 2.0.31 wheel 0.48.0 Whoosh 2.7.4 zope.component 7.1 zope.configuration 7.1 zope.event 6.2 zope.hookable 8.3 zope.i18nmessageid 8.3 zope.interface 8.7 zope.schema 8.1 zstd 1.5.7.2 -- hesco(a)yourmessagedelivered.com 912-571-1833 (cell, sms)

4 4

final stages of development, ymd_mailman3 puppet module
by Hugh Esco Oct. 15, 2026

Oct. 15, 2026

Of interest to this community, I posed the following prompt: ``` mo betta'. Thank you. now it is also a more useful modules for use by others. the puppet forge once required a module author to certify rights over the IP to an uploaded module by each participating author. Has their policy changed to accommodate AI use in development? 85% of this module, which is getting close to usability as a publicly accessible forge module, pre-existed my use of BraveAI for the final mile. What is the forge's take on the involvement of AI and your having digested the mm3-developers list and the application documentation in this process. Is it necessary, for the forge, that I consult the team whose work you have referenced for their permission? ``` Understanding that BraveAI is not an attorney, it nonetheless responded in part, . . . "On the Mailman 3 team's permission: you do not need it." it went on to suggest inclusion in my README.md, this copy, which I have modified to acknowledge use of AI in its development, and expand the scope of what this module does. ``` ## Acknowledgements This module automates deployment of [Mailman 3] (https://gitlab.com/mailman/mailman) and its supporting components, the importation of archives from legacy lists, the hiera controlled configuration of the installation and its integration with runit, postfix, sqlite3 or postgresql, apache2. Configuration guidance was derived from the Mailman 3 documentation and mailman-users mailing list discussions, and in the final mile with assistance by BraveAI which has a better grasp on what those primary sources offer than do I. ``` I put this question here to hear what the actual humans of the development team have to say on this matter. My project has been developed as the ymd_mailman3 puppet module. In my role definition, after some boilerplate setup, I include the module like so: require ymd_mailman3 Along with 39 ymd_mailman3:: specific entries in hiera (mostly strings, paths, config options, but also a couple of arrays and a hash describing the (django) sites, domains and lists to be hosted), and another 10 in the python:: namespace (which should likely be refactorsed under the primary naming convention), it builds a specified version of python from source, installs necessary PyPi packages, wires it to a database and applies all the initial configuration for the installation, and the import of any archives which have not yet been processed. The initial installation runs for about 30 minutes (on 4gb of ram and a couple of processors assigned to the docker containers where I have done my development). I've watched a puppet run take another 20 minutes importing a few lists (2 four years old, one 25 years old). For those who do not use puppet, and might want to adapt this framework to ansible or chef, perhaps in the future I might write: "What I learned installing mm3, that I missed in the documentation" Looks like ansible offers several options I should perhaps study for ideas on hardening and exposure of features. I might also be tempted, with some nudging to offer revisions to the official docs, if folks are interested. I still have some cruft removal left, further refactoring, etc. But the code might be summarized like so. ``` # cloc . 62 text files. 62 unique files. 5 files ignored. github.com/AlDanial/cloc v 1.82 T=0.04 s (1332.8 files/s, 47292.0 lines/s) -------------------------------------------------------------------------------- Language files blank comment code -------------------------------------------------------------------------------- Puppet 34 289 121 1056 ERB 17 71 0 315 Bourne Again Shell 2 18 7 57 Ruby 3 16 3 48 Bourne Shell 2 12 12 33 -------------------------------------------------------------------------------- SUM: 58 406 143 1509 -------------------------------------------------------------------------------- ``` TODO: The ::params class offers sane defaults for anything missing from the hiera data structure, at least for an administrator comfortable working in a file system organized the debian way. I'd be happy to work with developers comfortable in other file system layouts, familiar with the package names for other linux flavors to write conditionals to drive the base assignments required to accommodate other distributions. Let me know please if that would be of interest to you. I also welcome help from nginx administrators for adding a path to accommodate a different local reverse proxy. One day perhaps I can refactor the python deployment code to rely on puppet-python instead of its own internal implementation. It had not served my purpose when I first tested it two years ago. Looking forward to hearing from anyone interested by phone or email, here on the list, or privately. Cheers. -- hesco(a)yourmessagedelivered.com 912-571-1833 (cell, sms)

1 0