and it worked so I stuck with what worked. Trust me I rather use the daemon, but this is a small company
and I have to get it working within a reasonable time and then move on to other projects.
Joe Emenaker wrote:
So... hang on a sec... you don't want to re-parse the mail message for X-Spam-Status because "it seems like a lot overhead", yet you don't mind running the spamassassin program for each message instead of running it as a daemon?
- Joe
Matt Silva wrote:
I'm using the spamassassin perl script file, but I see what you mean. I also need to brush up
on my bash scripting skills ... how do you set the process exitcode assuming you can do that with
the perl script.
Joe Emenaker wrote:
Matt Silva wrote:
Hi there, Ive been searching to see if SA has an exit code if it marks the mail as spam, and
I couldn't find anything conclusive. How can I determine if it has marked the currently inspected
mail as spam?
A section of the manpage for spamc reads:
-c Just check if the message is spam or not. Set process exitcode to 1 is message is spam, 0 if not spam or processing
failure occurs. Will print score/threshold to stdout (as ints) or 0/0 if there was an error.
- Joe
-- Matt Silva Empower Software Technologies, LLC 27851 Bradley Rd. Suite 120 Sun City, CA 92586
PH: (909) 672-6257 WB: www.storagecommander.com EM: [EMAIL PROTECTED]
