Thomas Hochstein writes
| Default database backend is SQLite3 in order to not break automated | installations. For productive setups, PostgreSQL or MySQL are much | better options though. See README.Debian for further information. <https://packages.debian.org/trixie/mailman3>
It's what I read at the time. But it's neither here nor there now. the sqlite has the list information, the question is why "mailman shunt" does not see it, when "mailman lists" does.
But if you go back to the error message, it says
| Mar 15 05:40:46 2026 (2658932) <a930211e778a4aa0829cee5b2a9e7db9@kbs-mg.de> | runner "in" shunting message for missing list: <object object at 0x7fb1ad1ad730>
it does appear that "<object object at 0x7fb1ad1ad730>" is the list_id, when it should in fact be "bibnez@folks.email". Ok. In the runner.py, line 237
| list_id = msgdata.get('listid', missing)
if I add right after line 237
| elog.error('%s is the list_id from the message', list_id)
I see log entry
| Mar 15 12:40:11 2026 (3262760) list_id is <object object at 0x7fbdd6175730>
So maybe just renaming .psv to .pck and moving to shunt does not make a file in the bad queue fit for unshunting.
Thanks and cheers!
-- Written by Thomas Krichel http://openlib.org/home/krichel on his 22199th day.