Hi, Just realised
that the -p refers only to a file socket and not a network one,
and that SA-milter likely did not support this anyway. I'm back
to figuring out why postfix won't work unchrooted with SA-milter
:( :(
address@hidden .co.uk
pgp 4BA78604
On 10/11/2013 23:55, Simon Loewenthal wrote:
Hi,
My Debian 6 mail server with postfix SA and spamass-milter has
worked well.
Today I turned of postfix chroot because RDNS_NONE results were
pointless because postfix could not resolve IP address, and I
decided to unchroot this. Sadly, this stopped my spamass-milter
file system sockets from working, even after I change the postfix
entry from
unix:/spamass/spamass.sock
to
unix:/var/postfix/spamass/spamass.sock
So, I thought I should be using tcp ports instead and with this in
mind I commented all of its SOCKET* entries, and set the -p flag
with:
-p 11783
There was nothing else listening on this port, yet if I started
spamass-milter failed, and it failed regardless the ports I
specified.
Its error message was:
Nov 10 23:35:24 lt spamass-milter[14244]: spamass-milter 0.3.1
starting
Nov 10 23:35:24 lt spamass-milter[14244]: SpamAssassin: Unable to
bind to port 11783: Permission denied
Nov 10 23:35:24 lt spamass-milter[14244]: SpamAssassin: Unable to
create listening socket on conn 11783
Nov 10 23:35:24 lt spamass-milter[14244]: spamass-milter 0.3.1
exiting
Did I miss a trick here? I should be very grateful if someone
would shine some light onto this!
Best regards ,S
_______________________________________________
Spamass-milt-list mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/spamass-milt-list
|