Steve Suhre wrote to Matt Kettler and [EMAIL PROTECTED]:
Thanks, that helps... I'm running it locally, on one user account until I can get it working, hence the .procmailrc file. I ran 'spamassassin --lint 'and it didn't complain, but still no header rewrite. Not running spamd yet. It is processing the email, modifying the original message per report_safe, and adding other headers, it just won't rewrite the subject line!!! Is there a particular place in the config file where it belongs? Here's the meat of my config file:
Your example doesn't even contain a subject line.
---- required_score 1.0
Whoa. Really? You're going to have a boatload of FPs with that threshold. The default of 5.0 is already aggressive enough for most people's aggressive tendencies. :-)
However:
X-Spam-Status: Yes, score=22.2 required=5.0 tests=DIET_1,DRUGS_SLEEP,
Note the "required=5.0". Obviously your config isn't getting read, for, if it was, the above would read "required=1.0".
rewrite_header Subject *****SPAM*****
Looks fine, but I bet this isn't getting read, either. :-)
Run a message through spamassassin -t < message.txt on the command line, and see if you get different results. My hunch is that spamassassin runs as a different user when invoked from your procmail, and, as a result, is reading a different user config. You may do well to force the config path with one of --userprefs or --siteconfigpath as options to spamassassin. See spamassassin(1) for syntax, semantics, and details.
Cheers, - Ryan
-- Ryan Thompson <[EMAIL PROTECTED]>
SaskNow Technologies - http://www.sasknow.com 901-1st Avenue North - Saskatoon, SK - S7K 1Y4
Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America
