Wietse Venema:
> Wietse Venema:
> > Will Yardley:
> > > On Mon, Jul 21, 2014 at 04:42:57PM -0500, Noel Jones wrote:
> > > > This isn't an access map, and doesn't have the network notation
> > > > searches built into access maps. See the docs on mynetworks for the
> > > > syntax supported here:
> > > > http://www.postfix.org/postconf.5.html#mynetworks
> > > >
> > > > It might be easiest to use a flat file, which allows both names and
> > > > networks, rather than a hash: or cidr: table.
> > >
> > > http://www.postfix.org/postconf.5.html#mynetworks doesn't seem to
> > > mention in much detail what types of host patterns are recognized or how
> > > they're parsed. We've always had it as:
> >
> > There are no host patterns therefore they are not implemented.
>
> Actually, behavior depends on the parent_domain_matches_subdomains
> setting. The default setting includes mynetworks, meaning that
> example.com will match host.example.com by default. With mynetworks
> removed from from parent_domain_matches_subdomains, .example.com
> will match host.example.com.
>
> parent_domain_matches_subdomains is a feature that was meant to
> become empty over time.
I'll add some documentation to the text for mynetworks (adding a
pointer to parent_domain_matches_subdomains) and to the text for
parent_domain_matches_subdomains (describing which features it
controls).
Currently, parent_domain_matches_subdomains does not control the
behavior of smtpd_client_event_limit_exceptions. I'll fix that.
Since smtpd_client_event_limit_exceptions is meant to be similar
to mynetworks, it should behave in the same manner. There are already
a few features that borrow their parent-domain matching behavior
from mynetworks.
Wietse
