@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 it, but I can’t see how
that is put in place automatically. On re boot, it’s once again disabled, and
pf is not working. Even though the plist is loading.
reboot
sudo pfctl -s info
No ALTQ support in kernel
ALTQ related functions disabled
Status: Disabled Debug: Urgent
sudo pfctl -e
sudo pfctl -s info
No ALTQ support in kernel
ALTQ related functions disabled
Status: Enabled for 0 days 00:00:12 Debug: Urgent
any ideas?
Robert
> On 5 Mar 2016, at 00:42, Bill Cole
> <postfixlists-070...@billmail.scconsult.com> wrote:
>
> 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?
>>
>
> Which is the three active rules that would be generated by having this at the
> end of /etc/pf.conf when it was last reloaded:
>
> block return in log quick proto tcp from 174.46.142.137 to any port
> {25,465,587}
>
> Your rule may differ in small ways, yet be entirely reasonable. If you have a
> rule in pf.conf that doesn't seem to have resulted in one or more in the
> active listing, maybe you just forgot to reload:
>
> pfctl -f /etc/pf.conf
>
> Or if the rule shows in the active list but isn't working, maybe this will
> help:
>
> pfctl -e
>
Robert Chalmers
rob...@chalmers.com <mailto:rob...@chalmers.com>.au Quantum Radio:
http://tinyurl.com/lwwddov
Mac mini 6.2 - 2012, Intel Core i7,2.3 GHz, Memory:16 GB. El-Capitan 10.11.
XCode 7.2.1
2TB: Drive 0:HGST HTS721010A9E630. Upper bay. Drive 1:ST1000LM024 HN-M101MBB.
Lower Bay
