On 6/5/25 10:22, Sam Darwin via Mailman-users wrote:
Deleting all archives and importing the older messages first... that worked correctly. It is a large destructive actions though, should that count as the official solution?
No, that shouldn't be the "official" solution.
It may be too late now, but did you restart mailman-web? See the thread (started by you) at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/J...
Detour:
While debugging it seemed to be an interesting question whether the mailman3-web periodic cron tasks had been running, and if those tasks affected the hyperkitty import. Referring to "Cron Jobs for Mailman Web" https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-ma... Those instructions are not dumping stdout/stderr to a log file, nor rotating the log files. What is your opinion if I sent a pull request that adds "Method 2 - Advanced", and include logging for the crons. Or maybe I am missing something. Is the output of the cron tasks getting logged in your environment?
Any output to stdout or stderr from any of the crons will be emailed to
the owner of the crontab or the address in a MAILTO= in the crontab. You
should ensure that mail to mailman is deliverable
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan