On 10/13/05, List <[EMAIL PROTECTED]> 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? > > Finally, since dccpro is running, how come i still unable to see X-DCC SMTP > headers in the mail? > > regards > > >
I think I had this issue once. Setting the dcc_home configuration variable helped SA detect the socket. I have use_dcc 1 dcc_home /var/dcc in my local.cf
