> On Oct 1, 2019, at 9:21 AM, linkcheck <post...@linkcheck.co.uk> wrote:
> 
> Most of the installation info I have read online gives something similar to
> my original posting for master.cf. I can understand removing the smtp_cert
> lines from the smtp section (hence the question) but was not aware I did not
> need any cert specifications in master.cf.

See http://www.postfix.org/master.5.html (or man -s 5 master).

SYNTAX
    ...
    Command name + arguments
        ...
              -o name=value (short form)
                     Override  the  named main.cf configuration parameter. The
                     parameter value can refer to other  parameters  as  $name

                     etc.,  just like in main.cf.  See postconf(5) for syntax.

                     NOTE 1: With the  "long  form"  shown  above,  whitespace
                     after  "{",  around  "=",  and before "}" is ignored, and
                     whitespace within the parameter value is preserved.

                     NOTE 2: with the "short form" shown above, do not specify
                     whitespace  around  the  "="  or  in parameter values. To
                     specify a parameter value that contains  whitespace,  use
                     the  long  form described above, or use commas instead of
                     spaces, or specify the value in main.cf. Example:

                     /etc/postfix/master.cf:
                         submission inet .... smtpd
                             -o smtpd_xxx_yyy=$submission_xxx_yyy

                     /etc/postfix/main.cf

                         submission_xxx_yyy = text with whitespace...

                     NOTE 3: Over-zealous use of parameter overrides makes the
                     Postfix  configuration  hard  to understand and maintain.
                     At a certain point, it might be easier to configure  mul-
                     tiple instances of Postfix, instead of configuring multi-
                     ple personalities via master.cf.

Since the "-o" options are *overrides*, if an option has the
right value in main.cf, there is no need for an override.

The only practical exception that comes to mind is that the
smtpd_mumble_restrictions (for various values of "mumble")
should have defensive overrides in the submission entry of
master.cf (setting most of them empty).

This is because the submission restrictions almost never 
match the inbound SMTP restrictions and once set rarely
need any changes, and it would be too easy to break the
former while making changes to the latter.

-- 
        Viktor.

Reply via email to