Re: Block IP rcpt-to or block MX

2017-10-23 Thread Noel Jones
On 10/23/2017 11:13 AM, Emanuel wrote: >> in those cases reject_rhsbl_recipient should do the job. > I not find information for "reject_rhsbl_recipient". http://www.postfix.org/postconf.5.html#reject_rhsbl_recipient > > is the same option?*|reject_rbl_client|* No.

Re: Block IP rcpt-to or block MX

2017-10-23 Thread Emanuel
El 20/10/17 a las 13:25, Matus UHLAR - fantomas escribió: On 20 Oct 2017, at 9:38 (-0400), Matus UHLAR - fantomas wrote: unless you know that hotmial.com is an malicious site, don't block it. On 20.10.17 10:43, Bill Cole wrote: Go to http://hotmial.com with a JavaScript-enabled browser and

Re: Block IP rcpt-to or block MX

2017-10-20 Thread Emanuel
Thanks for your help. El 20/10/17 a las 11:06, Dominic Raferd escribió: On 20 October 2017 at 14:50, Emanuel > wrote: Quota: *Obvs you need to hash the transport file and then reload postfix. This transport file can

Re: Block IP rcpt-to or block MX

2017-10-20 Thread Bill Cole
On 20 Oct 2017, at 12:25 (-0400), Matus UHLAR - fantomas wrote: On 20 Oct 2017, at 9:38 (-0400), Matus UHLAR - fantomas wrote: unless you know that hotmial.com is an malicious site, don't block it. On 20.10.17 10:43, Bill Cole wrote: Go to http://hotmial.com with a JavaScript-enabled browser

Re: Block IP rcpt-to or block MX

2017-10-20 Thread Matus UHLAR - fantomas
On 20 Oct 2017, at 9:38 (-0400), Matus UHLAR - fantomas wrote: unless you know that hotmial.com is an malicious site, don't block it. On 20.10.17 10:43, Bill Cole wrote: Go to http://hotmial.com with a JavaScript-enabled browser and tell me what you think. Or, DON'T DO THAT! At least,

Re: Block IP rcpt-to or block MX

2017-10-20 Thread Bill Cole
On 20 Oct 2017, at 9:38 (-0400), Matus UHLAR - fantomas wrote: unless you know that hotmial.com is an malicious site, don't block it. Go to http://hotmial.com with a JavaScript-enabled browser and tell me what you think. Or, DON'T DO THAT! At least, don't do it on a weakly-defended

Re: Block IP rcpt-to or block MX

2017-10-20 Thread /dev/rob0
On Fri, Oct 20, 2017 at 03:06:32PM +0100, Dominic Raferd wrote: > On 20 October 2017 at 14:50, Emanuel > wrote: > > > Quota: *Obvs you need to hash the transport file and then reload > > postfix. This transport file can easily be extended to cover > > similar

Re: Block IP rcpt-to or block MX

2017-10-20 Thread Dominic Raferd
On 20 October 2017 at 14:50, Emanuel wrote: > Quota: *Obvs you need to hash the transport file and then reload postfix. > This transport file can easily be extended to cover similar cases.* > > how to make this? > ​ postmap /etc/postfix/transport postfix reload​

Re: Block IP rcpt-to or block MX

2017-10-20 Thread Matus UHLAR - fantomas
On 20.10.17 10:21, Emanuel wrote: Is it possible to create a list where the IP of certain recipients can be blocked? IPs not, domains yes, use check_recipient_access http://www.postfix.org/SMTPD_ACCESS_README.html Our users incorrectly type the domain name of the recipient. *hotmial.com ==>

Re: Block IP rcpt-to or block MX

2017-10-20 Thread Dominic Raferd
On 20 October 2017 at 14:21, Emanuel wrote: > Hello, > > Is it possible to create a list where the IP of certain recipients can be > blocked? > > Here and example: > > Oct 19 10:15:09 smtp01 postfix/smtpd[11048]: 5C28C20018459: > client=myserver[172.17.111.242] > Oct