- Mailman-users - lists.mailman3.org

Column 'starting_email_id' cannot be null
by kroerig＠web.de Aug. 18, 2025

Aug. 18, 2025

Hello, after upgrading from Debian 11 to Debian 12 achiving incoming mails always fails with Traceback (most recent call last): 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 435, in get raise self.model.DoesNotExist( During handling of the above exception (Thread matching query does not exist.), another exception occurred: File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 316, in _query self._do_get_result(db) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 147, in _do_get_result self._result = result = self._get_result() File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 349, in _get_result return self._get_db().store_result() During handling of the above exception ((1048, "Column 'starting_email_id' cannot be null")), another exception occurred: 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/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 117, in _decorator return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 163, in archive add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 739, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 763, in save_base pre_save.send( File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line 180, in send return [ File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line 181, in <listcomp> (receiver, receiver(signal=self, sender=sender, **named)) File "/usr/lib/python3/dist-packages/hyperkitty/signals.py", line 48, in Email_on_pre_save kwargs["instance"].on_pre_save() File "/usr/lib/python3/dist-packages/hyperkitty/models/email.py", line 239, in on_pre_save thread, _thread_created = Thread.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 588, in get_or_create return self.create(**params), True File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 453, in create obj.save(force_insert=True, using=self.db) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 739, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 776, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 881, in _save_table results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 919, in _do_insert return manager._insert( 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 1270, in _insert return query.get_compiler(using=using).execute_sql(returning_fields) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 66, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 78, in execute raise IntegrityError(*tuple(e.args)) Exception Type: IntegrityError at /hyperkitty/api/mailman/archive Exception Value: (1048, "Column 'starting_email_id' cannot be null") Postorius Version 1.3.8 HyperKitty Version 1.3.7 Any ideas how to fix this? Klauas

4 5

help with startup scripts
by Piet Barber Aug. 15, 2025

Aug. 15, 2025

Hello, I'm trying to get mailman3 working on Ubuntu. I'm following these instructions: https://docs.list.org/en/latest/install/virtualenv.html#setup-virtualenv I've gotten to the point where I can successfully su - to the mailman3 user, and manually start the mailman3 process with the startup command. However, when I follow the systemctl startup scripts as per the instructions at the URL above, it get stuck in the startup ... forever Starting from the command line works great! (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman start Starting Mailman's master runner Generating MTA alias maps (venv) mailman@arcus:~$ (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman status GNU Mailman is running (master pid: 47815) But when I try to start it from systemctl, it just hangs forever... root@arcus:/etc/nginx# systemctl start mailman3 If I background it, and check it out from systemctl status, I get that It's stuck in the startup mode. root@arcus:/etc/nginx# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: activating (start) since Wed 2025-08-13 23:12:05 UTC; 29s ago Process: 49024 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Tasks: 17 (limit: 4605) Memory: 878.0M (peak: 878.5M) CPU: 11.030s I've tried this with and without the forking entry in the systemctl configuration. No matter what I do, it's stuck in the ... Active: activating (start) since Wed 2025-08-13 23:13:37 UTC; 27s ago What am I missing? root@arcus:/etc/nginx# cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=syslog.target network.target postgresql.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid User=mailman Group=mailman Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop Restart=on-failure RestartSec=15 [Install] WantedBy=multi-user.target root@arcus:/# -- Piet Barber http://www.pietbarber.com/ http://blog.pietbarber.com/

4 7

db migration from mailman3.2.2 to mailman3.3.9 (sqlite3 to postgres16)
by Peter Thornton Aug. 13, 2025

Aug. 13, 2025

Hello, I know this question comes up here periodically, but I am having some trouble performing a data migration from an older version of mailman3 to a more recent one. We have a legacy environment with: mailman3.2.2 postorius 1.2.4 hyperkitty 1.2.2 there are two sqlite3 dbs for mailman core and mailman web. I've staged a new environment using the docker-mailman project with the following: mailman3.3.9 postorius 1.3.10 hyperkitty 1.3.8 there is a single postgres db here for both core and web. I've tried migration a few different ways, using pgloader, and also with some manual python scripts. Data is definitely not my forte, but I am struggling to get a working instance. I am running into several issues such as foreignkeyviolations, datatype mismatches, unique PK errors, etc.. Does anyone out there have a prescriptive process for this migration, or a suggestion for workflow/tooling that has worked in a similar upgrade process? Thanks! -Peter

2 1

default processing
by Sam Darwin Aug. 13, 2025

Aug. 13, 2025

Notice the repeated use of the word "default" (which is a great word, by the way). This creates confusion: Default action to take when this member posts to the list. List default -- follow the list's default member action. Default Processing -- run additional checks and accept the message. Due to backwards compatibility it may be difficult to change. But if it could be modified, how about: Action to take when this member posts to the list. List default -- follow the list's default member action. Standard Processing -- run additional checks and accept the message. In other words, in the context of message acceptance, the word "default" should have a certain selected meaning. Then make extra effort to choose other words for other actions, as proposed here, "Standard Processing", or something similar.

3 8

Website 404 error
by peter＠pi4cc.nl Aug. 11, 2025

Aug. 11, 2025

Hello I'm running Debian 12 with the latest version and installed mailman3 via apt install-mailman3-full. Everything works, I'm using MySQL as the database. There's something strange, and I can't find a source/solution. When I first access the website domain.nl/mailman3, it's redirected to domain.nl/mailman/postorius/lists/, resulting in a 404 error (3 after mailman is missing). When I accessed it a second time with the same link (domain.nl/mailman3), I was redirected to domain.nl/mailman3/postorius/lists and the welcome page appeared. This is strange... I tested it on a mobile device with Chrome and Firefox, and on a desktop with Chrome and Edge. All the results were the same. Is there a specific file to look add? Regards, Peter

3 2

Migration of archives mailman2 to mailman3: python: can't open file '/opt/mailman/manage.py': [Errno 2] No such file or directory
by Wikinaut Aug. 10, 2025

Aug. 10, 2025

Your current *) documentation says Migrate the list archives from Mailman 2 to Mailman 3 by running the following command: $ python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox (venv) /opt/mailman $ python manage.py python: can't open file '/opt/mailman/manage.py': [Errno 2] No such file or directory What did I wrong or what is that part of your documentation missing? *) https://docs.mailman3.org/en/latest/migration.html

3 6

I wanted to upgrade the mailman3 documentation, but cannot see the promised link "edit on github"
by Wikinaut Aug. 10, 2025

Aug. 10, 2025

https://docs.mailman3.org/en/latest/documentation.html#edit-on-gitlab Please can you fix that?

1 0

Vote irregularities
by Ron Aug. 10, 2025

Aug. 10, 2025

I've been playing with the voting system on a couple of lists (this one included). There are some weird behaviours I've noticed: * votes are frequently not immediately reflected - a page reload is required * some votes display as: 0 0 You dislike it (cancel) Here we see I've voted on a message, but the counts are still zero up and zero down. I just down-voted one of my posts as a test, and nothing changed in the page to reflect the vote. Often it takes multiple clicks, sometimes a page reload. Browser console shows voting generates a 200 response to a POST method, but the JSON confuses me: like 0 dislike 0 html '\n\n <form method="post" class="likeform"\n action="/archives/list/talk(a)lists.domain.tld/message/IK6WH4IQPZXOG3CIFV4CJGOKVFARGXA5/vote">\n <input type="hidden" name="csrfmiddlewaretoken" value="***">\n \n\t\t\n\t\t\t<a class="youlike vote "\n\t\t\thref="#like" data-vote="1" aria-label="Like thread">\n\t\t\t\t\t<i class="fa fa-thumbs-o-up"></i> 0\n\t\t\t</a>\n\t\t\t<a class="youdislike vote"\n\t\t\thref="#dislike" data-vote="-1" aria-label="Dislike thread">\n\t\t\t\t<i class="fa fa-thumbs-o-down"></i> 0\n\t\t\t</a>\n\t\t\n \n\n </form>\n' The uwsgi.log file entry for that vote is: [pid: 4010303|app: 0|req: 552908/575956] 127.0.0.1 () {66 vars in 1374 bytes} [Sun Aug 10 02:28:21 2025] POST /archives/list/talk(a)lists.domain.tld/message/IK6WH4IQPZXOG3CIFV4CJGOKVFARGXA5/vote => generated 696 bytes in 376 msecs (HTTP/1.1 200) 9 headers in 394 bytes (1 switches on core 1) Following the Permalink beside the voting options loads the specific message with no votes showing. Ctrl+F5 shows no votes. Re-casting vote and reloading shows no votes. Clicking "Back to thread" shows my message and: > 0 0 You dislike it (cancel) I don't think I've ever seen reliable voting on any MM3 site, including this one (I don't think I've seen zero / zero You {like|dislike} it (cancel) here, but multiple vote attempts to see the results is not unusual). Searching the archive shows something from ~6-7 years ago where caching was modified, seems relevant but nothing since. Am I alone in this, or is the feature so unused that nobody else noticed this?

2 1

Problem upgrading from 2.1 to 3, dockerized
by jesper.holck＠ibsgaarden.dk Aug. 9, 2025

Aug. 9, 2025

I recently followed the instructions here https://github.com/g4rf/dockerized-mailcow-mailman, and was able to create a new Mailman 3, Debian-based installation. I then followed the instructions here https://docs.mailman3.org/en/latest/migration.html in order to migrate from my old, Centos-based installation, to the new, Debian-based installation. It seemed to work well, but unfortunately a problem showed up. Whenever someone posted to one of the lists on the new installation, the messages were rejected by Postfix: postfix-mailcow-1 | Aug 5 20:55:48 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> postfix-mailcow-1 | Aug 5 20:55:49 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser1(a)gmail.com> proto=ESMTP helo=<[172.19.199.4]> postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser2(a)mail.dk> proto=ESMTP helo=<[172.19.199.4]> So, for each of the existing lists, I had to delete the old list and create a new one - with the same name and the same users. After this, everything seems to work as expected. Thanks for all the work you all has put into this, Jesper

2 1

mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."
by Wikinaut Aug. 8, 2025

Aug. 8, 2025

My post here is merely about the information output when running mailman addmembers/syncmembers where I discovered strange looking lines. I noticed that addmember and syncmember output looks like [ADD] =?utf-8?q?John_=28Foo=29_Doe_=5Bcomment1=5D_=5Bcomment2=5D?= <john.foo.doe(a)example.com> whereas the entries in the Web-GUI look fine. I triple-checked the textfile from which the names stem from, yes, the file is UTF8. Is this behaviour of addmember/syncmember command output commonly known - or is this a small cosmetic bug? PS. At some moment I had, probably from my test and legay data file, also these codings in about fifty entries of my users lists, but deleted that users with a small script, so that user list is now clean. My post here is merely about the information output when running mailman addmembers/syncmembers.

3 9