Theo Van Dinter wrote: > 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.
Verified. My sa 3.1.0 works normally with: spamassassin -t <sample-nonspam.txt >out.txt and generates all the same errors as B.G. Mahesh when I do: spamassassin -t <out.txt >out.txt B.G. Mahesh, I suggest trying your test again with the output directed to a different file, or /dev/null, not the same file as the input. spamassassin -t <sample-nonspam.txt >out.txt or spamassassin -t <sample-nonspam.txt >/dev/null
