Re: whitelisting

On 8/26/2016 4:02 PM, /dev/rob0 wrote: > On Fri, Aug 26, 2016 at 10:31:20PM +0300, Aggelos wrote: >> Does this also apply for any REJECT or DEFER ? > > Reject actions are like permit actions; they end the processing of > restrictions in that stage. Postfix stops all restriction processing when

Re: whitelisting

On Fri, Aug 26, 2016 at 10:31:20PM +0300, Aggelos wrote: > So any OK (or permit) is not final until all restriction stages are > checked, right? A permit (or reject) action is final IN THAT STAGE. It ends processing of any further restrictions, e.g., in your smtpd_client_restrictions stage,

Re: whitelisting

On 26/08/2016 04:34 μμ, /dev/rob0 wrote: Some of your DNSBLs have been gone for many years. At least one (spamcop) is best for scoring; not safe for outright blocking of mail. Shouldn't I keep at least one of these DNSBLs, like zen.spamhaus.org ?

Re: [postfix-users] whitelisting

On 26/08/2016 03:51 μμ, Alex JOST wrote: This should work: smtpd_helo_restrictions = permit_mynetworks, check_client_access hash:/etc/postfix/maps/whitelisted_clients, reject_invalid_helo_hostname, reject_unknown_helo_hostname You were right...It worked indeed. :)

Re: whitelisting

On 26/08/2016 04:34 μμ, /dev/rob0 wrote: You seem to think that a permit action in client restrictions applies globally to all other restriction stages. This is wrong, and not according to documentation. Each set of restrictions is evaluated independently, and ANY reject or defer result

Re: Postfix update on Freebsd

Mel Pilgrim: > On 2016-08-25 01:22, li...@lazygranch.com wrote: > > Generally when I've seen these "underscore" updates, I try to > > recompile and the make file indicates there is nothing to do. But > > that may be because my configuration file doesn't use a option that > > caused the

Re: whitelisting

On 26/08/2016 07:17 μμ, Bill Cole wrote: But the smtpd_helo_restrictions come later in the order of checks, isn't that so? Yes, but you can't protect a message from smtpd_helo_restrictions with a whitelist in smtpd_client_restrictions. I see.

Re: whitelisting

On 8/26/2016 10:59 AM, Aggelos wrote: > > Then it should stop checking when it matches by IP the OK in > /etc/postfix/maps/whitelisted_clients, right? It stops checking smtpd_client_restrictions, and moves on to smtpd_helo_restrictions. *Each* smtpd_*_restrictions section must result in OK (or

Re: whitelisting

On 26 Aug 2016, at 11:59, Aggelos wrote: On 26/08/2016 03:58 μμ, @lbutlr wrote: [...] The restrictions are pressed in order until there is a result of OK or REJECT. Then it should stop checking when it matches by IP the OK in /etc/postfix/maps/whitelisted_clients, right? No, because an

Re: Postfix update on Freebsd

On 2016-08-25 01:22, li...@lazygranch.com wrote: Generally when I've seen these "underscore" updates, I try to recompile and the make file indicates there is nothing to do. But that may be because my configuration file doesn't use a option that caused the "underscore" to be added. Because you

Re: [postfix-users] whitelisting

On 26/08/2016 03:51 μμ, Alex JOST wrote: This should work: smtpd_helo_restrictions = permit_mynetworks, check_client_access hash:/etc/postfix/maps/whitelisted_clients, reject_invalid_helo_hostname, reject_unknown_helo_hostname Will try it and see ...

Re: whitelisting

On 26/08/2016 03:58 μμ, @lbutlr wrote: On 26 Aug 2016, at 06:09, Aggelos wrote: On 26/08/2016 02:53 μμ, Kiss Gabor (Bitman) wrote: smtpd_helo_restrictions = permit_mynetworks, reject_invalid_helo_hostname, reject_unknown_helo_hostname Yet, in the logs I still

Re: whitelisting

On Fri, Aug 26, 2016 at 03:09:17PM +0300, Aggelos wrote: > On 26/08/2016 02:53 μμ, Kiss Gabor (Bitman) wrote: > >>smtpd_helo_restrictions = permit_mynetworks, > >>reject_invalid_helo_hostname, > >>reject_unknown_helo_hostname > > > > > >>Yet, in the logs I still get these reports (sample

Re: newbie department

On 25 Aug 2016, at 15:56, D'Arcy J.M. Cain wrote: > I have clients who expect their email to behave in a very clearly defined > way. If someone sends an email to my system it must do one of two things - > be delivered to to a user (or at least his spam filter) or bounced back to

Re: newbie department

> On 25 Aug 2016, at 08:59, Glenn English wrote: > > Why do I get mail to names like dcpczy3foku+gcyvikdnlcei? > > They're not a lot of them, but they show up every few days, and I can't think > why anybody'd do this. At first I thought somebody was trying to access their

Re: whitelisting

On 26 Aug 2016, at 06:09, Aggelos wrote: > On 26/08/2016 02:53 μμ, Kiss Gabor (Bitman) wrote: >>> smtpd_helo_restrictions = permit_mynetworks, >>>reject_invalid_helo_hostname, >>>reject_unknown_helo_hostname >> >> >>> Yet, in the logs I still get these reports

Re: [postfix-users] whitelisting

Am 26.08.2016 um 14:09 schrieb Aggelos: On 26/08/2016 02:53 μμ, Kiss Gabor (Bitman) wrote: smtpd_helo_restrictions = permit_mynetworks, reject_invalid_helo_hostname, reject_unknown_helo_hostname Yet, in the logs I still get these reports (sample on one line): Aug 26 03:37:52

Re: [postfix-users] whitelisting

On 26/08/2016 02:53 μμ, Kiss Gabor (Bitman) wrote: smtpd_helo_restrictions = permit_mynetworks, reject_invalid_helo_hostname, reject_unknown_helo_hostname Yet, in the logs I still get these reports (sample on one line): Aug 26 03:37:52 postfix/smtpd[27675]: NOQUEUE: reject: RCPT

Re: [postfix-users] whitelisting

> smtpd_helo_restrictions = permit_mynetworks, > reject_invalid_helo_hostname, > reject_unknown_helo_hostname > Yet, in the logs I still get these reports (sample on one line): > > Aug 26 03:37:52 postfix/smtpd[27675]: NOQUEUE: reject: RCPT from > spam1.vodafone.gr[213.249.16.2]: 450

whitelisting

I am trying to white list two client IPs: 213.249.16.2 213.249.16.3 I have put the following in /etc/postfix/maps/whitelisted_clients: 213.249.16.3 OK 213.249.16.2 OK I have run postmap hash:<...etc...> and reloaded postfix. main.cf ends like this: