On 12/04/2023 15:47 EEST Odhiambo Washington <odhiambo@gmail.com> wrote:
On Wed, Apr 12, 2023 at 3:24 PM Johannes Rohr <johannes@rohr.org> wrote:
Am 12.04.23 um 14:14 schrieb Johannes Rohr:
Am 12.04.23 um 13:58 schrieb Odhiambo Washington:
On Wed, Apr 12, 2023 at 2:31 PM Aki Tuomi via dovecot <dovecot@dovecot.org> wrote:
We finally managed to move from mailman2 to mailman3, and mail archives are now at https://dovecot.org/mailman3/archives and they can be now searched, too.
Please let us know if you have face any issues with the mailing list and we'll look into it.
[...]
What is the new signup method, given that signup is closed on this new MM3 instance?
I guess you can still subscribe via email. But why is account registration closed? I too manage a mailman3 instance. I cannot see any reason why you would want to disable account registration. A newly registered account does not automatically get new privileges, so this doesn't increase security. At the same time, it strips the user of the possibility to manage their account.
BTW, I am under the impression that archiving isn't set up properly. The newest mail in the archive (https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/) is of April 11. As in Mailman3, the mailing list manager (postorius) and the archiver (hyperkitty) are separate, it also took a bit of trial and error for me to ensure, that new mails are being archived. I don't remember what was the cause in my case. But I think the mailman-web log files revealed it to me.
While it's already getting OT, the archiving is done via mailman-web settings and cron. And maybe they better opt for the much faster Xapian indexer (https://github.com/notanumber/xapian-haystack/tree/master).
--
We have, in fact, opted for the Xapian indexer, given that the Whoosh indexer is not usable in practice.
I forgot to reopen the registration, I'll open it.
Aki