> > > Am Montag, 22. M�rz 2004 20:41 schrieb Anders Norrbring: > > > > > Isn't there a need/use for dccifd when running Amavis-new / > SpamAssassin? > > Anyway, when I start it with "start-dccifd" as user 'vscan' I get a > socket > > in /var/dcc named dccifd. I guess all is well? > > > > But when I run spamassassin --lint -D I get this: > > > > debug: DCCifd is not available: no r/w dccifd socket found. > > > > I use DCC and like it. However, the real advantage of DCC is > greylisting. Anyway, add the following to local.cf and make sure the > uid running SA has rw rights to the socket. > > dcc_dccifd_path /var/dcc/dccifd > > Alex
Alright Alex! Thanks! Now I get this in the spamassassin lint run: debug: DCCifd is available: /var/dcc/dccifd debug: dcc_home not defined, should not get here Not that I know what it means by the 2:nd line, dcc_home shouldn't be explicitly defined as of what I can make out of the docs. Anyway, IF I set dcc_home /var/dcc in my local.cf file, then I get errors; debug: leaving helper-app run mode DCCifd -> check skipped: Connection refused connect: Connection refused ...propagated at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Dns.pm line 617. So I let it be undefined, seems like it should work by now.. By the way, how do I *stop* dccifd? I can start it simple enough by the start-dccifd script, but not stop it? But it should feel "cleaner" to shut it off when system is going down for halt or reboot. Anders.
