Karamanga wrote the following on 5/28/2007 1:01 PM -0800: > Dear Daryl, ty for your reply, > > I got rid of the anti-drug.cf error buh just renaming this cf file. > > The error on DCC i dont understand. The plugin is installed and uncommentent > in the v310.pre file in the sa directory and i cheked the path to the dcc > dirs. Then i restarted sa and the error still appears ? > > Do you mean to tell me that the Pyzor error is a bogus message and that > Pyzor is working ? > (the pyzor setting was also uncommented in the v310.pre file an this path > is also correct) > > When i run spamassassin --lint test now, this the the result: > > > [15347] warn: config: failed to parse line, skipping: dcc_add_header 1 > [15347] warn: config: SpamAssassin failed to parse line, "/usr/sbin/dccifd" > is not valid for "dcc_dccifd_path", skipping: dcc_dccifd_path > /usr/sbin/dccifd > [15347] warn: config: failed to parse line, skipping: pyzor_add_header 1 > [15347] warn: lint: 3 issues detected, please rerun with debug enabled for > more information > > Is there a way to debug this further ? >
As Daryl said before, "pyzor_add_header" is not a valid configuration option with newer versions of SA. Neither is "dcc_add_header", so stop using both of those and the associated warnings will go away. As for dccifd, are you sure the path is correct? For example the path to my file is /var/dcc/dccifd. Also, are you sure dcc is running daemonized? Try: ps ax | grep dccifd - it should show something like: 31587 ? Ss 0:00 /var/dcc/libexec/dccifd 31588 ? Sl 6:19 /var/dcc/libexec/dccifd If not, then you will need to resolve that before dccifd will function properly. Bill
