Ok, this has something to do with Debian's retarded chroot options for smtpd.
I turned chroot back on for postfix and change the milter entry to point to the chrooted bit, and it works.
How very annoying. I wonder if I can get postfix to use a network socket for its DNS lookups instead and then perhaps RDNS_NONE would be useful.
Hi Todd,
Process is there,
~# pidof spamass-milter
19999
And process is using /var/spool/postfix/spamass/spamass.sock like configured!
~# lsof -p `pidof spamass-milter`
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
spamass-m 19999 spamass-milter cwd DIR 253,0 4096 2 /
spamass-m 19999 spamass-milter rtd DIR 253,0 4096 2 /
spamass-m 19999 spamass-milter txt REG 253,0 58592 28994 /usr/sbin/spamass-milter
spamass-m 19999 spamass-milter mem REG 253,0 1437064 138319 /lib/libc-2.11.3.so
spamass-m 19999 spamass-milter mem REG 253,0 131258 138177 /lib/libpthread-2.11.3.so
spamass-m 19999 spamass-milter mem REG 253,0 90504 134258 /lib/libgcc_s.so.1
spamass-m 19999 spamass-milter mem REG 253,0 530736 138469 /lib/libm-2.11.3.so
spamass-m 19999 spamass-milter mem REG 253,0 1043976 11949 /usr/lib/libstdc++.so.6.0.13
spamass-m 19999 spamass-milter mem REG 253,0 63528 28781 /usr/lib/libmilter.so.1.0.1
spamass-m 19999 spamass-milter mem REG 253,0 128744 138181 /lib/ld-2.11.3.so
spamass-m 19999 spamass-milter 0u CHR 1,3 0t0 545 /dev/null
spamass-m 19999 spamass-milter 1u CHR 1,3 0t0 545 /dev/null
spamass-m 19999 spamass-milter 2u CHR 1,3 0t0 545 /dev/null
spamass-m 19999 spamass-milter 3u unix 0xffff88001db13800 0t0 8901270 socket
spamass-m 19999 spamass-milter 4u unix 0xffff88001db12f00 0t0 8901271 /var/spool/postfix/spamass/spamass.sock
spamass-m 19999 spamass-milter 5r FIFO 0,8 0t0 8901273 pipe
spamass-m 19999 spamass-milter 6w FIFO 0,8 0t0 8901273 pipe
And this file exists and can be read/write by postfix:
# ls -l /var/spool/postfix/spamass/spamass.sock
srw-rw---- 1 postfix postfix 0 Nov 11 15:08 /var/spool/postfix/spamass/spamass.sock
She is running and maybe listening, and postfix cannot talk with her. I cannot see any misconfiguration.
On 2013-11-11 15:46, Todd Lyons wrote:
On Mon, Nov 11, 2013 at 5:57 AM, Simon Loewenthal <address@hidden> wrote:
Spoke too soon. Nov 11 14:55:19 lt postfix/smtpd[19157]: warning: connect to Milter service unix:/var/spool/postfix/spamass/spamass.sock: No such file or directory
So you have configured postfix to try to talk through
/var/spool/postfix/spamass/spamass.sock to the spamassassin milter.
Step 1 is to make sure that the socket file exists:
# ls -dl /var/spool/postfix/spamass/ drwxr-xr-x 2 spamass-milter root 1024 Nov 11 14:51 /var/spool/postfix/spamass/ # ls -l /var/spool/postfix/spamass/spamass.sock srw-rw---- 1 postfix postfix 0 Nov 11 14:51 /var/spool/postfix/spamass/spamass.sock
The file exists, but that doesn't mean that anything is attached to
it. Next, make sure the milter is running:
# pidof spamass-milter
19041
Next, if it is indeed running, look to see what files it has open:
lsof -p `pidof spamass-milter`
There I think you will find your misconfiguration. Either you have
spamass-milter configured to write the socket file somewhere else, or
only using TCP.
...Todd
_______________________________________________
Spamass-milt-list mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/spamass-milt-list