On Wed, Dec 14, 2005 at 01:28:07PM -0500, Matt Kettler wrote: > > spamassassin -t < sample-nonspam.txt > sample-nonspam.txt > > Why'd you direct the output back to sample-nonspam.txt? If SA isn't working > you'll corrupt the file.
Beyond that, I don't even know if it'll work. In all likelihood, the shell will truncate the file and prep it for output while also opening it for input, then run spamassassin which will then have a blank file. > All of that output looks like SA is having a hard time parsing the message > headers. All the Node stuff has to do with parsing out mime sections, and the > PerMsgStatus.pm lines both have to do with manipulation of the message > headers. You get that exact behavior when doing "cat /dev/null | spamassassin", btw, which would be explained by my paragraph above. -- Randomly Generated Tagline: "It's one thing if government pork directly benefits me, but a quarter million dollars to fight Goth culture in Blue Springs, MO? Hey! If you want to fight the Goths, I know a couple of Huns and Mongols who'll do it for free!" - Lewis Black, The Daily Show
pgpzSwo2UuoMj.pgp
Description: PGP signature
