On Mon, 22 Mar 2004, Stefan Ewert wrote: > Thx u gave me a right clou. The problem was that: the map file from dcc had > the wrong rights. i changed them and now i get this output: > <code> > debug: DCCifd is not available: no r/w dccifd socket found. > debug: executable for dccproc was found at /usr/bin/dccproc > debug: DCC is available: /usr/bin/dccproc > debug: entering helper-app run mode > debug: DCC: got response: X-DCC-EATSERVER-Metrics: localhost 1166; Body=13219 > Fuz1=2516685 Fuz2=2923681 > debug: leaving helper-app run mode > debug: DCC: Listed! BODY: 13219 of 999999 FUZ1: 2516685 of 999999 FUZ2: > 2923681 of 999999 > </code> > looks like is it working, the only problem is it that spamassassin doesnt find > the running socket in /var/run/dccifd.pid. > does anybody know who to tell spamassassin to work with this socket?
if there is dccproc only, there is no socket. spamd just calls the executable. the socket is created by dccifd only. regards, Matthias
