Viktor,

thanks for your reply.  More below.

On 03/08/2017 10:34 AM, Viktor Dukhovni wrote:
On Mar 8, 2017, at 8:16 AM, Robert Moskowitz <r...@htt-consult.com> wrote:

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.
All the postconf(1) command options are documented.  Just type:

        man postconf

to see what command options your version supports.  You can also
look at:

        http://www.postfix.org/postconf.1.html

And that is what I did. I saw what the options were, but no practical examples of them in use. That is what I meant by 'guidance'. The Postfix online manual has a lot of guidance on how to actually do things to Postfix to get it to do many valuable things.

which documents the latest version, and does its best to list
the first release in which various features appeared.  To see
the document for older releases, say 2.10, you can leverage github:

        
http://htmlpreview.github.io/?https://github.com/vdukhovni/postfix/blob/postfix-2.10/postfix/html/postconf.1.html

There is a nice http://www.postfix.org/postconf.5.html write up on maintaining 
main.cf, but not on master.cf.
The documentation in postconf(1) should be sufficient.  For 2.10 you have:

        Managing master.cf:

        postconf [-fMovx] [-c config_dir] [service ...]

        ...

        -f     Fold  long lines when printing main.cf or master.cf
               configuration file entries, for human  readability.

               This  feature  is  available  with  Postfix 2.9 and
               later.

        -M     Show  master.cf  file  contents  instead of main.cf

               file contents.  Specify -Mf  to fold long lines  for
               human readability.

               If service ...  is specified, only the matching ser-
               vices will be output. For  example,  "postconf  -Mf
               inet"  will  output all services that listen on the
               network.

               Specify zero or more arguments, each  with  a  ser-
               vice-type  name (inet, unix, fifo, or pass) or with
               a service-name.service-type  pair,  where  service-
               name is the first field of a master.cf  entry.

               This  feature  is  available  with  Postfix 2.9 and
               later.

        -o name=value
               Override main.cf parameter settings.

               This  feature  is  available  with Postfix 2.10 and
               later.

        -v     Enable verbose logging for debugging purposes. Mul-
               tiple -v options  make  the software increasingly
               verbose.

        -x     Expand $name in main.cf or master.cf parameter val-
               ues. The expansion is recursive.

               This  feature  is  available  with Postfix 2.10 and
               later.

So, in Postfix 2.10, you can display [selected] master.cf entries
or update overrides (-o parameters) for a given service.

But -o does not actually update master.cf. That seems to be what -P does in Postfix 2.11.

The master.cf modification features are much more extensive in
later releases.

And that is what I was looking for. I would have thought that somewhere there would be use examples of say, adding submission support into master.cf using postconf. I actually did find one such blog:

https://www.mind-it.info/2014/02/20/change-postfix-master-cf-postconf/

But the blogger does not state what version he used. Obviously it was at least 2.11.

Again thank you.

Reply via email to