- Mailman-users - lists.mailman3.org

configuring postfix local recipient table
by Alexander Inzinger-Zrock April 30, 2025

April 30, 2025

**System Key Data** OS: Debian 12 mailman: GNU Mailman 3.3.10 (Tom Sawyer) Python: Python 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] Method: Python Virtual Environment Installation Ahoi, i am trying to configure a mailman3 instance to replace a mailman2 installation (both on different hosts). The mm3 instance is actually not reachable (Incoming) but can send (Outgoing), as is the desired state to be (we intend to swap IPs during change of systems). A. Verify Incoming To verify that emails send to the MTA (postfix) get properly handled and handed over to the mm3-instance i tried to substitute incoming email by a) swaks utility [1] (fail) b) telnet utility [2] (fail) c) command ''mailman inject'' [3] (success) With c) i copied a former generate testmail-file to the mm3-host and injected it directly to my testlist (leaving out the MTA). With a) and b) i tried to hand over a testmail via CLI to the MTA (postfix) what resulted in the error: "Recipient address rejected: User unknown in local recipient table" B. /etc/postfix/main.cfg A search in mailman-users(a)mailman3.org archives [4] pointed me to the configuration of postfix as MTA [5], especially settings with the 'local_recipients_maps' parameter that should be set like [5]: local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/path-to-mailman/var/data/postfix_lmtp what i did / already had done. C. aliasing, restarting services and test without , I then restarted postfix, rebuilt the postfix aliases (command ''newaliases'') and rebuilt the mailman aliases (command ''mailman aliases''), even tried with space-separation instead of coma-separation [6], testet again with same result. D. empty /opt/mailman/mm/var/data/postfix_lmtp and then i just found out that my postfix_lmpt file was empty (that i believe to be the the place from where the hastables take their input). Questions: 1. could somebody suggest a way, an entry should occur in postfix_lmtp? 2. What would be the appropriate order to manually generate aliases? first: postfix-command ''newaliases'' and second: mailman-command ''mailman aliases'' or reverse? 3. finding traces [7] of a file called postfix.cfg i can't find it (anymore) in the official installation instructions. Is that file (still?) necessary regarding: 3.1 parameter for default lookup table type 3.2 pointing to command ''postmap'' 4. to what user should the command ''postmap'' be available [8]? Any pointer to manuals or examples i may have missed or ideas on any of those 4 questions would be greatly appreciated. lg alexander Sources: [1] swaks utility https://jetmore.org/john/code/swaks/ [2] telnet utility https://de.wikipedia.org/wiki/Telnet [3] command ''mailman inject'' https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… [4] search mailman-users(a)mailman3.org archives 'user unknown in local recipient table' https://lists.mailman3.org/archives/search?q=user+unknown+in+local+recipien… [5] docs mm3: 'Hooking up your mail server' https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… [6] docs postfix: local_recipient_maps https://www.postfix.org/postconf.5.html#local_recipient_maps [7] traces of postfix.cfg + https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… + https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [8] docs mm3: transport maps (regarding command ''postmap'') https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…

5 20

Exception when rendering certain emails ([Django] ERROR (EXTERNAL IP): Internal Server Error...)
by Matt Blissett April 30, 2025

April 30, 2025

Hi, I get exceptions logged when certain pages in the email archives (imported from Mailman 2) are opened. For example, this thread: https://lists.tdwg.org/archives/list/tdwg-tag@lists.tdwg.org/thread/HZCJQBJ… Could this be a bug in parsing the message? It's deployed using the maxking Docker packages, v0.5.3b1. Thanks, Matt Log follows: Internal Server Error: /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies No exception message supplied Request Method: GET Request URL: https://lists.tdwg.org/archives/list/tdwg-tag@lists.tdwg.org/thread/HZCJQBJ… Django Version: 4.2.20 Python Executable: /usr/bin/uwsgi Python Version: 3.12.10 Python Path: ['.', '', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/usr/lib/python3.12/site-packages'] Server time: Wed, 30 Apr 2025 15:04:09 +0000 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', 'django.contrib.humanize', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google'] 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', 'allauth.account.middleware.AccountMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/views/thread.py", line 269, in replies replies_html = replies_tpl.render(context, request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 175, in render return self._render(context) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/defaulttags.py", line 238, in render nodelist.append(node.render_annotated(context)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/loader_tags.py", line 208, in render return template.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 177, in render return self._render(context) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1064, in render output = self.filter_expression.resolve(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 742, in resolve new_obj = func(obj, *arg_vals) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/templatetags/decorate.py", line 42, in render return mark_safe(text_renderer(content)) ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 120, in __call__ return self.parse(s)[0] ^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 93, in parse self.block.parse(state) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 457, in parse end_pos2 = self.parse_method(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 216, in parse_method return func(m, state) ^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 368, in parse_block_quote text, end_pos = self.extract_block_quote(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 345, in extract_block_quote end_pos = self.parse_method(m4, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 216, in parse_method return func(m, state) ^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 387, in parse_list return parse_list(self, m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/list_parser.py", line 64, in parse_list groups = _parse_list_item(block, bullet, groups, token, state, rules) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/list_parser.py", line 174, in _parse_list_item block.parse(child, rules) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 457, in parse end_pos2 = self.parse_method(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 214, in parse_method assert lastgroup ^^^^^^^^^ Exception Type: AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies Raised during: hyperkitty.views.thread.replies Request information: USER: mailman-admin GET: sort = 'thread' last_view = '' POST: No POST data FILES: No FILES data COOKIES: csrftoken = '********************' sessionid = '********************'

2 3

Auto discard after max_days_to_hold not working.
by Hitashi mancho April 29, 2025

April 29, 2025

Dear all, I have migrated around 300 mailing lists from Mailman 2 to Mailman 3. In most of the mailing lists we have configured "max_days_to_hold" to 2. It was working fine in Mailman 2. However, it is not working in Mailman 3. Mailman version: GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.9 Rocky Linux 9.5 Crontab: @daily /opt/mailman/venv/bin/mailman digests --periodic 00 08 * * * /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly Please guide me in this regard. Regards, Hitachi.

3 3

Mailman not starting after restoring from snapshot
by zachr＠mta.ca April 28, 2025

April 28, 2025

I made a snapshot of my mailman3 VM before running a script to modify a bunch of lists. I stupidly did not turn the VM off before I made the snapshot, so Im almost certain this is a corrupted DB problem from doing a snapshot restore. The issue is now that the mailman service will not start automatically. Im able to get to the web interface but I see the error "Mailman REST API not available. Please start Mailman core." I can su to the mailman user and run 'mailman start -f' which seems to get things going again and shows the lists as they were before the snapshot, which is good, but I would like to get the issue fixed so that services start normally. Any help is appreciated. Here is some terminal output: ===================== ''' root@mlist3:~# systemctl status mailman3 × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2025-04-28 13:24:43 UTC; 1min 39s ago Process: 1873 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=2) CPU: 776ms Apr 28 13:24:42 mlist3 systemd[1]: Starting mailman3.service - GNU Mailing List Manager... Apr 28 13:24:43 mlist3 mailman[1873]: Usage: mailman start [OPTIONS] Apr 28 13:24:43 mlist3 mailman[1873]: Try 'mailman start -h' for help. Apr 28 13:24:43 mlist3 mailman[1873]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Apr 28 13:24:43 mlist3 systemd[1]: mailman3.service: Control process exited, code=exited, status=2/INVALIDARGUMENT Apr 28 13:24:43 mlist3 systemd[1]: mailman3.service: Failed with result 'exit-code'. Apr 28 13:24:43 mlist3 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. root@mlist3:~# systemctl start mailman3 Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details. root@mlist3:~# journalctl -xeu mailman3.service ░░ ░░ A start job for unit mailman3.service has begun execution. ░░ ░░ The job identifier is 662. Apr 28 13:24:43 mlist3 mailman[1873]: Usage: mailman start [OPTIONS] Apr 28 13:24:43 mlist3 mailman[1873]: Try 'mailman start -h' for help. Apr 28 13:24:43 mlist3 mailman[1873]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Apr 28 13:24:43 mlist3 systemd[1]: mailman3.service: Control process exited, code=exited, status=2/INVALIDARGUMENT ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit mailman3.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 2. Apr 28 13:24:43 mlist3 systemd[1]: mailman3.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit mailman3.service has entered the 'failed' state with result 'exit-code'. Apr 28 13:24:43 mlist3 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. ░░ Subject: A start job for unit mailman3.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit mailman3.service has finished with a failure. ░░ ░░ The job identifier is 662 and the job result is failed. Apr 28 13:30:21 mlist3 systemd[1]: Starting mailman3.service - GNU Mailing List Manager... ░░ Subject: A start job for unit mailman3.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit mailman3.service has begun execution. ░░ ░░ The job identifier is 1074. Apr 28 13:30:21 mlist3 mailman[1986]: Usage: mailman start [OPTIONS] Apr 28 13:30:21 mlist3 mailman[1986]: Try 'mailman start -h' for help. Apr 28 13:30:21 mlist3 mailman[1986]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Apr 28 13:30:22 mlist3 systemd[1]: mailman3.service: Control process exited, code=exited, status=2/INVALIDARGUMENT ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit mailman3.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 2. Apr 28 13:30:22 mlist3 systemd[1]: mailman3.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit mailman3.service has entered the 'failed' state with result 'exit-code'. Apr 28 13:30:22 mlist3 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. ░░ Subject: A start job for unit mailman3.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit mailman3.service has finished with a failure. ░░ ░░ The job identifier is 1074 and the job result is failed. ''' ====================================== Thank you in advance for any assistance.

3 2

Log Owner/Moderator actions ban address matching.
by Hitashi mancho April 28, 2025

April 28, 2025

Dear All, In Mailman 3, is there any way we can log the Owner/Moderator actions like moderator "x" approved the posting on list(a)example.com? Also, I have configured some local ban lists and some global ban lists as per my organization's policy. In my setup, I observed that when someone from the ban list posts to the list, that posting goes into a blackhole without leaving any trace. I may have made some configuration mistakes, but can we log the ban list matching or generate a notification if some postings match the ban list? Regards, Hitachi.

2 1

Info mails to list owners have "user@example.com" as from address (bounce score incremented)
by Ulf R. April 25, 2025

April 25, 2025

Hello, mails to list owners with subjects like <Mailaddress>'s bounce score incremented on <MyListName> comes from "user(a)example.com". Where is the right place to change this? We never defined this mail address anywhere. Thank you very much!

3 3

Getting an error for every post made to any list
by sun zi April 23, 2025

April 23, 2025

As mentioned in the subject, I am getting the following error after every post. Any assistance would be much appreciated: --- ERROR 2025-04-22 11:21:21,356 11617 django.request Internal Server Error: /archives/api/mailman/archive Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/query.py", line 916, in get_or_create return self.get(**kwargs), False ^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/query.py", line 637, in get raise self.model.DoesNotExist( hyperkitty.models.sender.Sender.DoesNotExist: Sender matching query does not exist. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.errors.StringDataRightTruncation: value too long for type character varying(255) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ 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/decorators/http.py", line 43, in inner return func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/hyperkitty/views/mailman.py", line 117, in _decorator return func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/views/decorators/csrf.py", line 56, in wrapper_view return view_func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/hyperkitty/views/mailman.py", line 163, in archive add_to_list(mlist_fqdn, msg) File "/opt/mailman/venv/lib/python3.11/site-packages/hyperkitty/lib/incoming.py", line 95, in add_to_list sender = Sender.objects.get_or_create(address=sender_address)[0] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/manager.py", line 87, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/query.py", line 923, in get_or_create return self.create(**params), True ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/query.py", line 658, in create obj.save(force_insert=True, using=self.db) File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/base.py", line 814, in save self.save_base( File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/base.py", line 877, in save_base updated = self._save_table( ^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/base.py", line 1020, in _save_table results = self._do_insert( ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/base.py", line 1061, in _do_insert return manager._insert( ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/manager.py", line 87, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/query.py", line 1805, in _insert return query.get_compiler(using=using).execute_sql(returning_fields) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1822, in execute_sql cursor.execute(sql, params) File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ django.db.utils.DataError: value too long for type character varying(255)

2 2

Login confusion
by Markus Grandpré April 22, 2025

April 22, 2025

Dear list, We've encountered an issue with Postorius after migrating from Mailman 2.1. It appears that Postorius is treating email addresses with differing capitalization as distinct user accounts. For example, <markus.grandpre(a)uni-konstanz.de> and <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate identities. This is causing significant confusion. Users registered with one capitalization pattern are not seeing the list subscriptions and settings that were previously associated with their account (imported from Mailman v2.1) which used a different capitalization. Is there a known configuration option or method within Postorius (or Mailman 3 itself) to normalize or unify account identification, effectively treating email addresses as case-insensitive for account matching? We need a solution that ensures users see their correct list memberships regardless of the capitalization they use when logging in or that was used during the original Mailman 2.1 import. Thank you in advance Markus -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

10 19

Moderator e-mails only going out once a day
by jkoral＠luc.edu April 22, 2025

April 22, 2025

Hi, I have just got done migrating from MM2 to MM3 and the users are experiencing issues with their moderated messages. After the message is sent, the moderator does not know about the message until the next day. I checked the maillogs and all those messages are being sent at the same time around midnight. I also noticed the messages are being sent from user(a)example.com, which I switched in /etc/mailman3/mailman.cfg to a generic e-mail address. Is there a way to change those moderator e-mails to send right away? Does having user(a)example.com in the config affect that? Thank you in advance, Joe

6 22

Upgrade docker-mailman to v0.5.2
by Christopher April 21, 2025

April 21, 2025

Hi Abhilash, I checkout the v0.5.2 for testing my upgrade from 0.4.6 and noticed, that the docker-image-version is still set to 0.4 in docker-compose.yaml. Is there any reason for it or should it be set to 0.5? I´m still using my good old mariadb. I did not find any upgrade-informations about breaking-changes. Do you have any experience with migrating from 0.4.6 to 0.5.2 on mariadb? Best regards Chrclaus

1 1