On Fri, Jul 25, 2014 at 05:22:58PM -0400, Wietse Venema wrote:
> Will Yardley:
> > Ah, but in my case, I am using '.domain.tld' vs. 'domain.tld', so I
> > guess my original question really was, does .domain.tld match subdomains
> > for $mynetworks / $smtpd_client_event_limit_exceptions when specifi
Will Yardley:
> Ah, but in my case, I am using '.domain.tld' vs. 'domain.tld', so I
> guess my original question really was, does .domain.tld match subdomains
> for $mynetworks / $smtpd_client_event_limit_exceptions when specified in
> that way?
In the case of mynetworks, it depends on the presenc
On Fri, Jul 25, 2014 at 10:09:08AM -0400, Wietse Venema wrote:
> Will Yardley:
> > > Actually, behavior depends on the parent_domain_matches_subdomains
> > > setting.
> So the present behavior is as if smtpd_client_event_limit_exceptions
> is not listed in parent_domain_matches_subdomains. It bor
Will Yardley:
> > 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
> > w
> 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.c
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:
> >
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/po
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
>
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 t
On Mon, Jul 21, 2014 at 04:42:57PM -0500, Noel Jones wrote:
>
> It might be easiest to use a flat file, which allows both names and
> networks, rather than a hash: or cidr: table.
Thanks - I think this is how it was setup at one point, and that
explains why.
w
On 7/21/2014 4:25 PM, Will Yardley wrote:
> We have:
> smtpd_client_event_limit_exceptions =
> 192.168.0.0/16,127.0.0.1,cidr:/etc/postfix/config/white_list,hash:/etc/postfix/config/white_list_internal_servers,hash:/etc/postfix/config/anvil_whitelist
>
> configured for Anvil. The last file is for
We have:
smtpd_client_event_limit_exceptions =
192.168.0.0/16,127.0.0.1,cidr:/etc/postfix/config/white_list,hash:/etc/postfix/config/white_list_internal_servers,hash:/etc/postfix/config/anvil_whitelist
configured for Anvil. The last file is for rate-limiting exemptions
only, whereas the other 2 a
12 matches
Mail list logo
