@JimReid
Just got this bounce from your own server - I suspect because my Static IP
doesn’t have a rDNS record. I’ve seen this before. But as Sky Broadband isn’t
interested in sorting a rDNS record for me… I just have to live with it.
This <5751bee9.skybroadband.com
Jim, yes.
I went for the line of least resistance, a plist file to enable pf at boot time.
The system has a pfctl.plist that loads pf.conf, but there is no automatic way
to then enable pf - which seems very odd.
So you have pfctl -f /etc/pf.conf loaded at boot-time, but the packet filter,
pf,
> On 5 Mar 2016, at 15:38, Robert Chalmers wrote:
>
> 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.
Did
@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
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
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
2016-03-05 0:56 GMT+00:00 Wietse Venema :
> Pawe? Grzesik:
> > Mar 4 22:52:09 mailtest postfix/pipe[16692]: EA9ACC794C: to=<
> p...@gmail.com>,
> > relay=dlp, delay=1.1, delays=0.31/0.01/0/0.78, dsn=2.0.0, status=sent
> > (delivered via tool service)
> > Mar 4 22:52:09