Re: Multiple lookup entries in an SQL table

2021-02-19 Thread Antonio Leding
Thanks Dan & Weitse - very much appreciated… - - - On 19 Feb 2021, at 17:23, Dan Mahoney wrote: From a database point of view, unless you have an ORDER BY statement in your query, the order returned could be either (unless postfix’s code is sorting them). If postfix only wants a single resu

Re: Multiple lookup entries in an SQL table

2021-02-19 Thread Dan Mahoney
From a database point of view, unless you have an ORDER BY statement in your query, the order returned could be either (unless postfix’s code is sorting them). If postfix only wants a single result, then your query would need a LIMIT statement in it. > On Feb 19, 2021, at 5:19 PM, Wietse Ven

Re: Multiple lookup entries in an SQL table

2021-02-19 Thread Wietse Venema
Antonio Leding: > Ok? > > So if I have the following: > > example.com OK > example.com REJECT > > Then the correct Postfix lookup behavior is to return OK,REJECT That is what the database client does. However, there is no Postfix code that wants "OK,REJECT" as a lookup result. Wietse

Re: Multiple lookup entries in an SQL table

2021-02-19 Thread Antonio Leding
Ok… So if I have the following: example.com OK example.com REJECT Then the correct Postfix lookup behavior is to return OK,REJECT Do I understand correctly? Also, I do understand that this type of config would be a corner case and likely not really something to be used so this is really more

Re: Multiple lookup entries in an SQL table

2021-02-19 Thread Viktor Dukhovni
On Fri, Feb 19, 2021 at 11:13:57PM +, Antonio Leding wrote: > I wanted to ask about the expected behavior if there are multiple > entries in an SQL table for the same lookup (IP address, network, > domain, etc.) which specify either the same or different actions > (REJECT, OK, etc.). As do

Re: smtpd_client_restriction map in CIDR? (Thanks & suggestion)

2021-02-19 Thread Gary Aitken
On 2/19/21 1:51 PM, Wietse Venema wrote: Postfix CIDR maps support CIDR. I don't understand how one would implement CIDR lookup keys in a hash: map. me either, thanks and to others who replied also It would be handy if postmap hash:foo printed a warning if it encountered CIDR or any other pro

Multiple lookup entries in an SQL table

2021-02-19 Thread Antonio Leding
Hello Postfix Community, I wanted to ask about the expected behavior if there are multiple entries in an SQL table for the same lookup (IP address, network, domain, etc.) which specify either the same or different actions (REJECT, OK, etc.). - - - example #1 1.2.3.4 OK 1.2.3.4 REJECT

Re: smtpd_client_restriction map in CIDR?

2021-02-19 Thread Wietse Venema
Gary Aitken: > I had the impression a map could contain client addresses in CIDR > notation, but apparently not. Is there a way to make restrictions > using CIDR notation? Postfix CIDR maps support CIDR. I don't understand how one would implement CIDR lookup keys in a hash: map. Wietse

Re: smtpd_client_restriction map in CIDR?

2021-02-19 Thread Benny Pedersen
On 2021-02-19 21:01, Gary Aitken wrote: $ postmap -q 209.85.217.52 hash:ok_client $ postmap -q 209.85 hash:ok_client $ postmap -q 209.85.128.0 hash:ok_client $ postmap -q 209.85.128.0/17 hash:ok_client OK change hash to cidr, and try again

Re: smtpd_client_restriction map in CIDR?

2021-02-19 Thread Matthias Kneer
Hi Gary, Is there a way to make restrictions using CIDR notation? Yes - just replace hash with cidr, like this: smtpd_client_restrictions = permit_mynetworks check_client_access cidr:/etc/postfix/ok_client reject More details: http://www.postfix.org/cidr_table.5.html Best regards,

smtpd_client_restriction map in CIDR?

2021-02-19 Thread Gary Aitken
I had the impression a map could contain client addresses in CIDR notation, but apparently not. Is there a way to make restrictions using CIDR notation? Here's what I was trying to do: smtpd_client_restrictions = permit_mynetworks check_client_access hash:/etc/postfix/ok_client reject /e