On Sep 27, 2014, at 10.42, Viktor Dukhovni <postfix-us...@dukhovni.org> wrote:
> On Sat, Sep 27, 2014 at 10:24:13AM -0400, b...@bitrate.net wrote: > >> On Sep 27, 2014, at 07.48, Wietse Venema <wie...@porcupine.org> wrote: >> >>> Use "postconf -d", not "postconf -n". -n is for settings in the >>> configuration file, -d is for the built-in settings which include >>> the version, release date, and so on. >> >> This reminds me - some time long ago, I happened to notice that >> config_directory seems to be the lone exception to the postconf -n >> behavior described in postconf(1). It's not of much consequence, >> at least for me, but I was just curious why [assuming it's >> intentional]. > > To support the MAIL_CONFIG environment variable and the "-c" > command-line option, the value of "config_directory" is added to > the key-value hash of data extracted from main.cf. This is done > even when neither are specified. i see. may i ask how being included in postconf -n specifically ties into support for the MAIL_CONFIG environment variable and the "-c” command-line option? i’m not being skeptical - i genuinely don’t understand, and would like to. -ben
