Thanks for the reply.
>> * primary MX with current policies. Also whitelists the backup MX
via check_client_access directive and via
>> permit_mynetworks
>>
>> Question:
>>
>> If a spam email makes it "in" through the backup MX and is delivered
to the primary, will the 'permit_mynetworks'
>> or 'check_client_access' directives prevent other checks from
blocking the email? In other words, do those two
>> directives only apply to mail that originates from the backup MX
itself or all mail that flows through it?
>
> nobody knows because nobody knows wat is in that configurations
check_client_access has the FQDN of the backup MX and "OK" as the value.
I had this entry there prior to making the other box a backup MX as a
way to make sure that nothing I implemented later on would reject the
mail coming from the box (logs, etc). That was the intention anyway.
> "check_recipient_access" in any ways is dangerous
I use it to whitelist or blacklist specific email addresses. So far I've
only used it to explicitly kill aliases that I've retired. It works
great for that purpose so far.
> empty "smtpd_recipient_restrictions" is not really smart
I remember reading that, and from what I remember it allows a MX to be
an open relay, which is why I've been very careful to not do that.
> why are you doing that instead configure them and place the line
*below* permit_mynetworks?
I'm not and don't mean to imply otherwise.
> check_recipient_access, check_sender_access and check_client_access
> with no relay and smtpd restricitons before makes you sooner or
> later to a open-realy, why was discussed here many times
That's not my setup.
>> Settings on the primary MX:
>>
>> smtpd_recipient_restrictions =
>> permit_mynetworks
>> reject_unauth_destination
>> check_recipient_access hash:/etc/postfix/recipient_access.conf
>> check_sender_access hash:/etc/postfix/sender_access.conf
>> check_client_access hash:/etc/postfix/client_access.conf
>> check_policy_service inet:127.0.0.1:10023
>> reject_invalid_helo_hostname
>> reject_non_fqdn_helo_hostname
>> reject_unknown_client_hostname
>> reject_unknown_sender_domain
>> reject_unknown_recipient_domain
>> reject_non_fqdn_sender
>> reject_non_fqdn_recipient
>> reject_unauth_pipelining
>> reject_rbl_client zen.spamhaus.org
>> reject_rbl_client b.barracudacentral.org
What you're seeing there is the results of me running:
postconf smtpd_recipient_restrictions | sed 's/, /\n/g'
so the output would be formatted for easier reading.