@Bill Cole
I’m pretty sure I have postscreen and postfix working right now… not too sure
if i’ts blocking what I wanted blocked - or if they just went away. However,
there are others - endlessly - trying. So something to do in my spare time?
Also, I can see that pfctl -e turns it on - enables i
ok, thanks Bill
I am still learning about pf.conf - and by adding your fix, I now get this.
Which seems entirely reasonable now :-)
Thanks, I’ll keep learning …
Robert
zeus:etc robert$ sudo pfctl -vnf /etc/pf.conf
pfctl: Use of -f option, could result in flushing of rules
present in the main r
Ok, thanks Bill.
I have postscreen enabled.
master.cf
smtp inet n - n - 1 postscreen
However, I had the postscreen_access_list setting set to ignore ….. so learning
all the time :-)
Now to look at pf. Thanks for the excellent tips there.
Robert
> On
On 4 Mar 2016, at 9:47, Robert Chalmers wrote:
thanks, that seems to work - how to make it permanent next …
but, it should be working in postfix in any case shouldn’t it?
Wep, weekend coming up.
Robert
On 4 Mar 2016, at 13:48, L.P.H. van Belle wrote:
Very simple, route it to localhost.
Li
On 2016-03-04 14:39, Robert Chalmers wrote:
How can I block this user from even attempting to access the mail
server?
Mac. OSX 10.11
Postfix.
I’ve even tried setting it in the firewall - but I’m missing
something, because there it is again...
I have the domain IP in a blacklist on both the pf.
On 03/04/16 08:39, Robert Chalmers wrote:
> How can I block this user from even attempting to access the mail server?
> Mac. OSX 10.11
> Postfix.
>
> I’ve even tried setting it in the firewall - but I’m missing something,
> because there it is again...
>
> I have the domain IP in a blacklist on b
thanks, that seems to work - how to make it permanent next …
but, it should be working in postfix in any case shouldn’t it?
Wep, weekend coming up.
Robert
> On 4 Mar 2016, at 13:48, L.P.H. van Belle wrote:
>
> Very simple, route it to localhost.
>
> Like :
> route add -host 174.46.142.137
