Washington Odhiambo writes
MM3 with Sqlite is not recommended for production. The virtualenv HOWTO even doesn't mention it.
I know now, but I have it in production now. It was the default in the Debian package.
So ideally, you should be using PostgreSQL or MariaDB.
But I don't know how to convert. I know very little about RDMS, have been avoiding them since my earliest childhood. ;-)
In a production setup, the MM3 core and Django config files should ideally reside in /etc/mailman3/
mailman@tagol:~$ mailman info | grep -v creden GNU Mailman 3.3.10 (Tom Sawyer) Python 3.12.9 (main, Feb 5 2025, 01:31:18) [GCC 14.2.0] config file: /etc/mailman3/mailman.cfg db url: sqlite:////var/lib/mailman3/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/
The output of the command 'mailman info' should show "config file: /etc/mailman3/mailman.cfg". with db_url pointing to an officially supported RDBM.
Well the list has been running off sqlite for years, so I believe all the data is there and it is correct.
That will tell you that MM3 is reading the expected config.
I think it does.
Having said that, let's say your choice is sqlite as the DB, does your list exist in the DB?
I think so.
Run this command from the DB and show output: select id, list_id from mailinglist;
mailman@tagol:~$ sqlite3 /var/lib/mailman3/data/mailman.db SQLite version 3.46.1 2024-08-13 09:16:08 Enter ".help" for usage hints. sqlite> select id, list_id from mailinglist; 1|bibnez.folks.email sqlite>
So it is in the database. Thank you so much for your help!
So presumably whatver is running "mailman shunt" is looking for the database in a different location.
-- Written by Thomas Krichel http://openlib.org/home/krichel on his 22199th day.