deoren:
> On 6/28/17 3:18 PM, Wietse Venema wrote:
> > deoren:
> >> On 6/28/17 1:32 PM, Wietse Venema wrote:
> >>
> >>> I suggest that you look at Postfix features that focus on 'unknown'
> >>> client names:
> >>>
> >>> http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname
> >>> http://www.postfix.org/postconf.5.html#reject_unknown_reverse_client_hostname
> >>>
> >>> These descriptions also discuss permanent versus temporary errors.
> >>
> >> Thank you for your reply.
> >>
> >> I use the first restriction in my setup, but was surprised whenever a
> >> check_client_access entry I added for a vendor's mail server (with an
> >> 'OK' result) still resulted in mail being rejected from that server's
> >> "client name".
> >
> > Yes, the text should be repeated in other places. There are about
> > seven check_client*access features, and only check_reverse_client_*
> > may use a client hostname that failed validation.
>
> Thank you for noting that. I took another look at the documentation
> (postconf.5.html) and I see where it notes the following for
> check_reverse_client_hostname_access:
>
> > unverified reverse client hostname, parent domains, client IP
> address, or networks obtained by stripping least significant octets
>
> Is this directive the equivalent of check_client_access, except that it
> allows the use of an unverified DNS entry in the checks?
It uses the 'unverified' reverse client hostname. I have no better
words to express that. There is no mention of DNS records, for the
simple reason that Postfix does not make DNS queries to determine
the client address->name or name->address mapping.
Wietse