List wrote: > Hi, > > I am trying to get DCCifd running. Below is the debug from spamassassin > > [28450] dbg: plugin: registering glue method for check_dcc > (Mail::SpamAssassin::Plugin::DCC=HASH(0x982dd9c)) > [28450] dbg: dcc: dccifd is not available: no r/w dccifd socket found > [28450] dbg: util: executable for dccproc was found at > /usr/local/bin/dccproc > [28450] dbg: dcc: dccproc is available: /usr/local/bin/dccproc > [28450] dbg: info: entering helper-app run mode > [28450] dbg: dcc: opening pipe: /usr/local/bin/dccproc -H -R < > /tmp/.spamassassin28450P6b89ttmp > [28453] dbg: util: setuid: ruid=0 euid=0 > [28450] dbg: dcc: got response: X-DCC-NIET-Metrics: > brilliance.anonns.com 1080; Body=19099 Fuz1=193674 Fuz2=193670 > [28450] dbg: info: leaving helper-app run mode > > My socket is located -rw-r--r-- 1 root root 7 Oct 14 01:23 > /var/run/dcc/dccifd.pid and why cant spamassassin detect it?
Because that's not the socket, that's the pid file. The socket will be a zero-byte file something like this: srw-rw-rw- 1 root root 0 Oct 12 11:34 dccifd
