On Tue, Apr 7, 2020 at 3:47 PM Ralph Seichter <abbot(a)monksofcool.net> wrote:
Clear Linux is keeping me both busy and confused. I have installed the
"dovecot" and "postfix" bundles, but wonder about the configuration.
may be down to the idea of statelessness again, but where are the config
files? Both Dovecot and Postfix require configuration beyond what could
be defined at compile-time on some Clear Linux build host who knows
nothing of my infrastructure, so I suspect the files to be hiding
somewhere? Both packages include extensive example config files in
their original release tarballs.
We weren't bundling the documentation which had the example configs.
I'll add that to the bundle definitions now.
On launch, Dovecot complains about a missing /etc/dovecot/dovecot.conf.
Sure enough, the whole folder is missing. Postfix is grumpy because
/etc/postfix does not exist either, so there's no main.cf, master.cf,
postfix-files etc., causing Postfix's integrity check to fail. Note that
I did not specify these particular locations, they are compiled in.
This is part of our stateless approach since we couldn't reasonably
make config files that had useful defaults, we do not ship active
I have since created the necessary files manually, either based on
servers of mine or by extracting defaults from the source tarballs.
That's probably not how it should be done, but what is the correct
method for Clear Linux?
I would honestly have the configs live in source control and be
provisioned as part of setting up hosts and not depend on any distro
default settings for these kinds of services.
Also, I get the following authentication error from Dovecot:
auth: Fatal: Support not compiled in for passdb driver 'ldap'
Ah I can enable that in the build, seems a reasonable enough thing.
While I can run "swupd bundle-add openldap", how do I change compile
time (!) options for Dovecot? On Gentoo Linux, I'd add "USE=ldap" to the
build. With MacPorts, I'd use the "+ldap" variant. However, I don't
a Clear Linux package for an LDAP-enabled Dovecot server, and my search
for documentation has so far failed to return more than "yes, these
You could build the package yourself from source and install it into
/usr/local with your modifications as should work for most anything.