On 01/20/2011 02:28 PM, RW wrote:
> On Thu, 20 Jan 2011 11:49:56 +0100
> J4 <ju...@klunky.co.uk> wrote:
>
>> Good morning to all of you,
>>
>> This popped up in the spamd.log after a reboot (done to test
>> everything worked after a reboot).
>>
>> warn: dcc: dccifd -> check skipped: dcc: failed to connect to a
>> socket /var/dcc/dccifd: Connection refused
>>
>> The socket is there:
>> srw-rw-rw- 1 dcc spamd 0 Jan 10 09:40 /var/dcc/dccifd
>>
>> local.cf has :-
>> use_dcc 1
>> dcc_path /usr/local/bin/dccproc
> dccproc is the fallback client if there is no dccifd daemon running, I
> just use that. dccproc might be much less efficient than dccifd in a
> straight comparison, but compared to spamd/spamc it's negligible IMO.
Thank-you for the info.
I would like to run dccifd in of dccproc anyway. A half a second is
half a second gained.
Q: Should it be started as root, and then drop privs?I could add it to
init.d/dccifd as:-
dccifd -I dcc:dcc -Q -G off
-Q is there for testing. no point reporting stuff during testing.
-G off I have greylisting already implimented. I am unsure if this
will help or hinder.
Cheers,
S
