On 16 May 2016, at 18:44, Gomes, Rich wrote:
True, but I have always set up Sendmail that way, using the access
file like an allow list.
I would like postfix to be setup in a similar fashion
Unlike Sendmail, Postfix does not have a single access map against which
a diversity of SMTP parameters are checked. If you believe you need such
an architecture, use Sendmail. Your initial approach of using
$mynetworks was more appropriate and might have worked just fine except
that you apparently have some configuration that you haven't mentioned
and no one has guessed. For example, on my personal server I have 29
items in my smtpd_recipient_restrictions list including 8 check_*_access
directives carefully ordered among the reject_* directives, allowing for
extremely fine control. Most cases can't justify that sort of complexity
but it seems like everyone has their own favorite Postfix tricks,
including people who package it for various OS distributions.
If you are used to Sendmail, you are very likely to project some
Sendmail behaviors on similar features in Postfix incorrectly. The
72k-word postconf(5) man page may seem daunting and I can't recommend
reading it from top to bottom, but it is very complete and MUCH easier
to navigate than Sendmail's cf/README and every file in the cf/cf tree
implementing every feature you find interesting. postconf(5) is always
the first place to look when a setting isn't behaving as you expect.
Since you seem to be new to Postfix you should probably also read some
of the documentation from Postfix's "readme" directory in full:
BASIC_CONFIGURATION_README
STANDARD_CONFIGURATION_README
SMTPD_ACCESS_README
And for important tips on how to get help HERE efficiently, the last ~50
lines of the DEBUG_README file are critical. We don't know what version
of Postfix you're running, whether you built from source or are using
some OS packager's quirky variant, or what, if any, other non-default
settings you have which don't do what you expect and might influence the
issues you're having.
