Control: tags -1 -moreinfo Control: severity -1 wishlist Control: retitle -1 use configuration directories by default
On 12/31/20 2:44 PM, PICCORO McKAY Lenz wrote:
Currently Courier uses several configuration files in /etc/courier that can be replaced by a subdirectory whose contents are concatenated and treated as a single, consolidated, configuration file.
Ah, understood. Thanks for explaining. I'm already using multiple files in a directory in most cases. It seems well possible already, but just a matter of defaults. I agree the directories should be created by default.
First setp to solve this is in courier-base package, must be changed to true, this will create the minimal set of directories.
If you're speaking of the `courier-base/webadmin-configmode` template question, I'm with you. This needs to vanish.
Later in a new revision remove the question and migrate to use only directories (that can co-exist with normal files), manpages of the courier suite points so many times about those directories..
Manpages should be adjusted to clarify both is possible, IMO.
by example the esmtpacceptmailfor: can be a single file in the path /etc/courier/esmtpacceptmailfor of a directory at the path /etc/courier/esmtpacceptmailfor.dir and all files inside will be parsed as single one.
Yes, works that way.
better example is hosted domains, can be a single file in /etc/courier/hosteddomains but is better a directory /etc/courier/hosteddomains and each domain could be a single file (named as the domain without dots) and with domain inside in plain text.
I don't necessarily think that's a good approach, but I agree that it should be possible. However, I think it already *is* possible now. It clearly works for me (tm). Anything in specific that doesn't work when configuring using multiple files in a directory?
Regards Markus
