#974979 use configuration directories by default

Package:
src:courier
Source:
courier
Submitter:
PICCORO McKAY Lenz
Date:
2026-05-14 03:35:02 UTC
Severity:
wishlist
#974979#5
Date:
2020-11-17 14:42:18 UTC
From:
To:
directory configuration behaviour produces a better way of manage
courier, we need to simplified the management of the package

also directory behaviour is more easy to manage for people just by
addidinjg files per host name.. inclusively manpages refers in that
way

the only offers to that is in the courier-webadmin package and there's
no mention of the behaviour at the README of courier-base package but
almost in all the manpages that may confuse
---

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
#974979#10
Date:
2020-12-31 09:58:48 UTC
From:
To:
Hi,

from this wording, I have no idea what this bug is about, sorry.  Please
clarify your proposal.

Markus
#974979#19
Date:
2020-12-31 13:44:24 UTC
From:
To:
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.

This behaviour is less confused for the few tutorials and works better
to manipulate the files by scripts (as webadmin cgi does)

First setp to solve this is in courier-base package, must be changed
to true, this will create the minimal set of directories.

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..

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.

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.

as i said.. this behaviour is more elaborated but more organized
for huge servers like production real cases

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com


El jue, 31 de dic. de 2020 a la(s) 05:58, Markus Wanner
(markus@bluegap.ch) escribió:
#974979#24
Date:
2021-01-02 13:54:50 UTC
From:
To:
Control: tags -1 -moreinfo
Control: severity -1 wishlist
Control: retitle -1 use configuration directories by default

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.

If you're speaking of the `courier-base/webadmin-configmode` template
question, I'm with you.  This needs to vanish.

Manpages should be adjusted to clarify both is possible, IMO.

Yes, works that way.

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
#974979#35
Date:
2021-01-02 21:24:27 UTC
From:
To:
El sáb, 2 de ene. de 2021 a la(s) 09:54, Markus Wanner
(markus@bluegap.ch) escribió:
the question is made in courier-base .. cos webadmin depends on
manpages already point that! the html and web of courier is also
almost same as manpages!
as i said, manpages said it works for both! so directories must be default,
webadmin does not touch single files unless are need!. just need
directory structure be present..

i alreay include some of those direction in the !9 pull request!

dont worry about lot of commits.. merge rewuest will be squash wen
merged in one only message!
#974979#40
Date:
2026-05-14 03:33:05 UTC
From:
To:
Lenz,

Is this still an issue with the current version of currier (1.5.1-3)?
#974979#43
Date:
2026-05-14 03:33:05 UTC
From:
To:
Lenz,

Is this still an issue with the current version of currier (1.5.1-3)?