On 12/12, Steve Thomas wrote: > spamassassin -t < email.txt On 12/12, Matt Kettler wrote: > pipe it through spamassassin -t > > Note: -t mode FORCES sa to generate a report, and it WILL contain text
Works beautifully, thank you both. I swear I looked at the man page... don't know how I missed that, it even says "report" :/ On 12/12, Evan Platt wrote: > spamassassin < filename1 > filename2 Won't work because my config tells SA not to generate reports. Got spamprobe and spamassassin working together now - writes to IN.spam if they agree, IN.spam-sa if only SA thinks it's spam, IN.spam-sp if only SP thinks it's spam: :0 SCORE=| /usr/local/bin/spamprobe train :0fw:spamassassin.lock | /usr/local/bin/spamassassin :0 wf | /usr/bin/formail -I "X-SpamProbe: $SCORE" :0: * ^X-Spam-Status: Yes * ^X-SpamProbe: SPAM IN.spam :0: * ^X-SpamProbe: SPAM IN.spam-sp :0: * ^X-Spam-Status: Yes IN.spam-sa -- Break something. http://www.ChaosReigns.com ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
