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 rate-limiting exemptions > only, whereas the other 2 are used for whitelisting in other places. > > I thought that, for networks that fall on classful boundaries, for > example, /24s, I could just do [in /etc/postfix/config/anvil_whitelist] > 10.0.0.5 OK > 172.16.34 OK > > or > 172.16.34. OK > > However, with either notation, messages with an IP falling within > (e.g.,) 172.16.34.0/24 seem to be getting rate-limited. > > This is Postfix 2.3.3 on RHEL 5. > > Adding the network in question to the CIDR map, in CIDR format, seems to > work as expected, but just wondering if there's a way to get the > expected behavior without adding an additional file and making our > config even more convoluted. > > w >
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. -- Noel Jones
