Wietse,
thank you for your response.
On 03/08/2017 10:44 AM, Wietse Venema wrote:
Robert Moskowitz:
But this is not the point. In fact, if there is no guidance on how to
use postconf for managing master.cf, it really does not matter which
version of postfix I use. Just maintain master.cf as we always have.
There is a nice http://www.postfix.org/postconf.5.html write up on
maintaining main.cf, but not on master.cf.
There is (obviously) no such guidance with Postfix releases that
pre-date the support to edit master.cf. Only Postfix versions that
support master.cf editing document these features (in the postconf(1)
manpage).
In short, you can list master.cf as a sequence of name=value pairs,
and you can specify name=value pairs to change master.cf.
When I look at man postconf, -o only updates main.cf. -M is only for
reporting what is in master.cf.
These features were added to facilitate automated configuration
management (Puppet, Chef, etc.). When every setting looks like a
name=value pair, it can be managed by programs that don't need to
understand Postfix configuration syntax.
It's probably overkill for a small site, but it's one of the attempts
to bring Postfix into the 21st century (along with JSON queue listings).
And so I stay with the old way of using 'cat >> master.cf' and sed to
update. That still works and is 'good enough' for my goals. Just wanted
to stay current with what is available in the release provided by the
Centos/Redhat maintainers.
Again, thank you for responding and thank you for this great product.
BTW, I am working in the IETF I2NSF workgroup where we are defining
architecture and protocols to maintain Network Security Functions. Some
of those will end up in remotely managed updates to Postfix. So on that
level, I get what you are doing.
take care.
