Mark Labeste writes:
]$ mailman conf -s archiver.hyperkitty Usage: mailman conf [OPTIONS] Try 'mailman conf -h' for help.
Error: No such section: archiver.hyperkitty
mailman conf reads the configuration. There is no configuration for
HyperKitty in the default configuration (mailman/config/schema.cfg and
the active mailman.cfg).
You need to have an [archiver.hyperkitty] section in the active mailman.cfg. If you never added one, check the documentation for what needs to go in there and add one.
If you already have a HyperKitty section, run mailman info, which
will tell you what mailman.cfg is being used. If it gives an
unexpected answer, you're probably just running mailman in a "wrong"
place (wrong only because the search algorithm finds the unexpected
configuration file). Try running mailman from a different current
working directory.
There is one tricky point. For reasons I don't understand, mailman
will often create var/etc/mailman.cfg, and it will be empty
except for comments. I've found it very easy to trip over that file,
so I usually do ln -s /etc/mailman3/mailman.cfg var/etc/mailman.cfg
to placate the evil spirits.