From: Rick Knight <rick_kni...@rlknight.com> Date: Tue, 13 Oct 2009 09:42:18 -0700 Jeff Mincy wrote: > From: Rick Knight <rick_kni...@rlknight.com> > Date: Tue, 13 Oct 2009 08:53:21 -0700 > > Just following this thread because I recently got dcc working also. In > my case I didn't have dcc installed. After installing dcc everything > seems to be working but now I'm wondering about dccifd. On my system > dccproc is in /usr/local/bin but dccifd is in /var/dcc/libexec/. I also > have start-dccifd in /var/dcc/libexec. I assume I need to add > dcc_dccifd_path to my local.cf and then run start-dccifd before starting > spamassassin. Is that correct? > > Run spamassassin --test-mode. If spamassassin finds dccifd it will > say 'dccifd is available': > > % spamassassin --test-mode --debug dcc < MESSAGE 2>&1 | fgrep dccifd > 134:[14145] dbg: dcc: dccifd is available: /var/lib/dcc/dccifd > 135:[14145] dbg: dcc: dccifd got response: X-DCC-sonic.net-Metrics: pinky 1156; bulk Body=1 Fuz1=many Fuz2=many > > If you get 'dccifd is not available: > ... dbg: dcc: dccifd is not available: no r/w dccifd socket found > > then you need to use dcc_dccifd_path or dcc_home > -jeff > Thanks Jeff, When I run test-mode I just get this bash: MESSAGE: No such file or or directory I'm sure I'm just useing the command wrong.
create a file called MESSAGE that contains a complete spam message with full headers.