Tibor Molnar writes:
Can archiving be changed anywhere in mailman3 configs, so then all new lists created do not archive by default?
Unfortunately, no. Once we get last year's GSoC merged, there will be, but that's going to have to wait a few weeks as it's not really ready and I don't have time for a while.
What you can do is create a style in Python and make that the default. In $SITE_PKGS/mailman/styles/default.py, append:
-------------------------------- cut here -------------------------------- from mailman.interfaces.archiver import ArchivePolicy
@public @implementer(IStyle) class ArchivesDefaultDisabledStyle(LegacyDefaultStyle):
"""The legacy default style with archiving disabled."""
name = 'archives-disabled'
description = _('Ordinary discussion mailing list style,'
' with archiving disabled')
def apply(self, mailing_list):
super().apply(self, mailing_list)
mlist.archive_policy = ArchivePolicy.never-------------------------------- cut here --------------------------------
In mailman.cfg find and modify or create:
-------------------------------- cut here -------------------------------- [styles] default: archives-disabled -------------------------------- cut here --------------------------------
Untested, feel free to ask if it doesn't seem to work.
This really should be implemented as a plug-in so default.py being overwritten in an upgrade won't be a problem, but the plug-in API is annoyingly complicated and the example plug-in over-engineered, and I couldn't get it to work (and in the project where I learned to do this I am not being paid enough to care ;-). The approach above was straightforward.
Eventually I'll get around to doing the plug-in approach, and maybe in the meantime Mark or Abhilash will speak up. If Those Who Know don't show up soon, ask again in the medium term (but before you update Mailman and it gets overwritten :-).
Steve