On Sun, 2020-10-04 at 22:09 +0200, Loïc Dachary wrote:
Hi, It turns out to be a feature added in 1.3.1 [0]. I wonder if the MySQL instructionslisted in this comment[1] are safe to use? I'm reluctant to upgrade because the machine is for production and using packages from Debian GNU/Linux buster is recommended. Cheers [0] https://gitlab.com/mailman/hyperkitty/-/issues/146 [1] https://gitlab.com/mailman/hyperkitty/-/issues/146#note_423111350
They worked for me :-) I cannot promise that I caught all dependencies, and I just needed something to clear the archives so they could be recreated (the mbox I imported was not clean). i.e. There may still be something in some some table that points to the list name. It did not delete the entry in hyperkitty_mailinglist initially so I edited my comment and added that in.
It was a quick and dirty route to clear emails from the list out the archive, nothing more. All it does it get the ids of the threads and emails in the list, remove records with references to these from other tables (attachments, votes, etc), remove internal references and drop the threads and emails. It is not optimal code, but then I hope I dont have to use it too often - I am just tied to the packages shipped in debian buster, so dont have 1.3.1.
-- Alex
On 04/10/2020 18:16, Loïc Dachary wrote:
Hi, I accidentally created an archive for a non existent mailing list with a command like: python3 manage.py hyperkitty_import --list-address test2@the.re --ignore-mtime --no-sync-mailman /tmp/f.mbox where test2@the.re does not exist. It succeeded and now the web interface shows this archive that has no associated mailing list. How can I remove it ? Thanks in advance for any tip you may have ;-)
-- Loïc Dachary, Artisan Logiciel Libre _______________________________________________Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/