On Sun, Oct 27, 2013 at 12:01:47PM -0400, Charles Marcus wrote:
> But... in the postconf -n output, used parameters have only ONE
> space between the parameter name and the parameter argument (in
> spite of the fact that there are actually two spaces in main.cf),
> while unused parameter have two spaces.
This is not surprising (I used 4 spaces):
$ ( stdout=$( mktemp /tmp/stdout.XXXXXX )
stderr=$( mktemp /tmp/stderr.XXXXX )
printf "\n=== main.cf:\n"; cat /tmp/main.cf
postconf -c /tmp -n > $stdout 2>$stderr
printf "\n=== stdout:\n"; cat $stdout
printf "\n=== stderr:\n"; cat $stderr
rm $stdout $stderr )
=== main.cf:
mynetworks =
192.0.2.0/25,
192.0.2.128/25
hisnetworks =
192.0.2.0/25,
192.0.2.128/25
smtp_tls_protocols =
!SSLv2,
!SSLv3
=== stdout:
config_directory = /tmp
mynetworks = 192.0.2.0/25, 192.0.2.128/25
smtp_tls_protocols = !SSLv2, !SSLv3
=== stderr:
postconf: warning: /tmp/main.cf: unused parameter:
hisnetworks=192.0.2.0/25, 192.0.2.128/25
Parameters understood by Postfix are reported on stdout in a
normalized form with all runs of whitespace characters replaced by
a single space.
Parameters not understood by Postfix are reported as warnings on
stderr largely verbatim, the only change is that internal newlines
and whitespace around "=" are suppressed. There is little reason
to expect normalization of parameter values in warnings.
--
Viktor.
