Loren Wilton wrote: > It would help if you could somehow capture the SA output on that lint > failure. It would probably point to the problem. > > Loren
Here is an excerpt from spamassassin --lint -D output debug: Score set 0 chosen. debug: running in taint mode? yes debug: Running in taint mode, removing unsafe env vars, and resetting PATH debug: PATH included '/sbin', keeping. debug: PATH included '/usr/sbin', keeping. debug: PATH included '/usr/bin', keeping. debug: PATH included '/usr/local/sbin', keeping. debug: PATH included '/usr/local/bin', keeping. debug: PATH included '/usr/ccs/bin', keeping. debug: Final PATH set to: /sbin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/ccs/bin debug: ignore: using a test message to lint rules debug: using "/usr/local/share/spamassassin" for default rules dir debug: using "/etc/mail/spamassassin" for site rules dir debug: using "/root/.spamassassin" for user state dir debug: using "/root/.spamassassin/user_prefs" for user prefs file Failed to parse line in SpamAssassin configuration, skipping: N_" debug: bayes: 27812 tie-ing to DB file R/O /var/qmail/.spamassassin/bayes_toks debug: bayes: 27812 tie-ing to DB file R/O /var/qmail/.spamassassin/bayes_seen debug: bayes: found bayes db version 2 Thanks for your help > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu There's no place like 127.0.0.1
