Sorry Ryan, my bad... I added a -C and the path to the config files in .promailrc and it's working like a charm now. Thanks for your help! (whatever your name is................)
At 11:21 AM 8/4/2004, Ryan Thompson wrote:
Steve Suhre wrote to Ryan Thompson:
Thanks Matt,
It's Ryan, actually. :-) I think Matt responded to your first message.
I noticed the default score, but if I add garbage to the config file and run --lint it complains, so I assumed it was reading it... The setting is low for test purposes only. The user info is helpful, I'll look into that.
Exactly. Like I said in my last message, spamassassin (the command line utility) is probably running as a different user, and, thus, pulling the user config from a different location, as compared to your procmail user.
- Ryan
At 04:33 PM 8/3/2004, Ryan Thompson wrote: [...]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
-- 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
--- Steve Suhre Antero web technologies 719.634.8161 [EMAIL PROTECTED]
