HyperKitty/Mailman3 issues
Hi!
I tried setting up Scheduled Tasks as described in <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> but the "runjobs" command can't be found. I see the hyperkitty and mailman commands when using "help".
The "qcluster" service is working.
Using Django 2.1.1 and HyperKitty 1.2.1.
Maybe related to that, I have two issues with archives.
- Changing the archiving setting in the Web-UI to something else than public seems to have no effect. The already archived messages are still accessible in public.
- Related to 1., how can I remove a list archive without affecting other lists?
Regards, Florian Schulze
On 11/22/18 2:58 AM, Florian Schulze wrote:
Hi!
I tried setting up Scheduled Tasks as described in <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required>
but the "runjobs" command can't be found. I see the hyperkitty and mailman commands when using "help".
Does "help" show a list under [django_extensions] including runjob and runjobs?
Is 'django-extensions' in the list of INSTALLED_APPS in your Django settings?
The "qcluster" service is working.
Using Django 2.1.1 and HyperKitty 1.2.1.
Maybe related to that, I have two issues with archives.
- Changing the archiving setting in the Web-UI to something else than public seems to have no effect. The already archived messages are still accessible in public.
This is related. It is one of the "daily" jobs that updates this. Note that changing to "private" will require login after the "daily" jobs run, but changing to "do not archive" will leave the existing archive accessible.
- Related to 1., how can I remove a list archive without affecting other lists?
There's no easy way. For the "prototype" archiver, the archives for a list are in var/archives/prototype/listname@example.com/ and that directory can be removed, but that doesn't affect HyperKitty. HyperKitty's archives are in the Mailman database and multiple tables are involved.
One could try just removing the row for the list from the hyperkitty_mailinglist table. That may render the list's archive inaccessible via the web UI, but I have no idea what would be broken by doing this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 22 Nov 2018, at 19:53, Mark Sapiro wrote:
On 11/22/18 2:58 AM, Florian Schulze wrote:
Hi!
I tried setting up Scheduled Tasks as described in <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required>
but the "runjobs" command can't be found. I see the hyperkitty and mailman commands when using "help".
Does "help" show a list under [django_extensions] including runjob and runjobs?
Is 'django-extensions' in the list of INSTALLED_APPS in your Django settings?
That was the issue. Thanks!
The "qcluster" service is working.
Using Django 2.1.1 and HyperKitty 1.2.1.
Maybe related to that, I have two issues with archives.
- Changing the archiving setting in the Web-UI to something else than public seems to have no effect. The already archived messages are still accessible in public.
This is related. It is one of the "daily" jobs that updates this. Note that changing to "private" will require login after the "daily" jobs run, but changing to "do not archive" will leave the existing archive accessible.
After manually running the daily job, the archive is now private.
- Related to 1., how can I remove a list archive without affecting other lists?
There's no easy way. For the "prototype" archiver, the archives for a list are in var/archives/prototype/listname@example.com/ and that directory can be removed, but that doesn't affect HyperKitty. HyperKitty's archives are in the Mailman database and multiple tables are involved.
One could try just removing the row for the list from the hyperkitty_mailinglist table. That may render the list's archive inaccessible via the web UI, but I have no idea what would be broken by doing this.
I hope this will be added at some point. For now I have the archive set to private.
Thanks again for the pointers!
Regards, Florian Schulze
participants (2)
-
Florian Schulze -
Mark Sapiro