http://bugzilla.spamassassin.org/show_bug.cgi?id=3077
------- Additional Comments From [EMAIL PROTECTED] 2004-03-08 23:07 -------
Subject: Re: spamassassin -d is too damn slow
On Mon, Mar 08, 2004 at 10:55:59PM -0800, [EMAIL PROTECTED] wrote:
> To which SA operations will --mbox apply? -d only?
Nope. Everything.
> for example, will 'spamassassin -t --mbox < mail.mbox' test all the
> messages in mail.mbox and output the result to stdout?
Yep.
> and will 'spamassassin -r --mbox < mail.mbox' report all the
> mail in mail.mbox as spam? Similarly, for -k?
Yep.
For instance, I scared JM with this one:
grep T_ALL_TRUSTED results/spam-theo.log | awk '{print $3}' | xargs \
samailoffset -b | spamassassin-cvs --mbox -d | spamassassin-cvs -L --mbox | \
grep T_ALL_TRUSTED
Worked quite nicely. ;)
> What about, 'spamassassin -e --mbox < mail.mbox'?
I had to fake that one a little bit. Basically it'll return the exit
code if any of the messages are spam, or 0 if none are.
BTW: The process will be more efficient if you do:
spamassassin --mbox mail.mbox
If you do the redirect, and depending on your shell, spamassassin has
to create a temp file, send STDIN to it, then process over the file,
then delete it. Which is kind of pointless if STDIN is coming from a
file that already exists.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
