Add support for mailman.cfg include directory
It would be great if the mailman3 configuration mailman.cfg
would support an include directory, e.g. /etc/mailman3/conf.d
. Dynamically adding configuration for optional third-party components like the HyperKitty archiver would be way easier this way.
In particular, automating configuration in distribution packages would be much easier with a configuration include directory.
In Debian for example, packages are not allowed to touch the configuration of other packages (see Debian Policy - 10.7.4. Sharing configuration files). So e.g. the hyperkitty
package is not allowed to touch /etc/mailman3/mailman.cfg
from the mailman3-core
package.
In Debian we will go with a ugly workaround for the time being: we'll ask the admin during installation of mailman3-core
whether she wants the hyperkitty configuration included in mailman.cfg
and warn her that hyperkitty needs to be installed and configured for that to work.
What do Mailman3 upstream authors think about this feature? Would support for a config include directory for mailman.cfg
be a valid feature?