At 10:52 PM 11/23/03 -0500, Angus McIntyre wrote:Can anyone tell me what I'm overlooking? Is there some magic switch required to get SpamAssassin to honor 'add_header' instructions?
First, run spamassassin --lint.. just as a sanity check ... Check for duplicate copies of spamc/spamd ... Run spamassassin -v.. is it really 2.60? Run spamassassin --lint -D and look at the debug output.. is it really parsing the rules directories you think it is?
Thank you for your suggestions, which were a big help in homing in on the problem (and yes, spamassassin was using different directories from the ones I'd assumed it was using, which is useful to know, although that wasn't the root cause).
Once the test you proposed had eliminated the obvious, I started looking at qmailscanner, and eventually found FAQ#14 at:
http://qmail-scanner.sourceforge.net/FAQ.php#cs
It turns out that qmailscanner's 'fast_spamassassin' mode calls 'spamc -c', which doesn't get any header information back from 'spamd' - just a status code. So that pretty much clears up the mystery of where my headers went to.
Thanks for your help.
Angus -- [EMAIL PROTECTED] http://pobox.com/~angus
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
