Wolfgang Zeikat wrote: > Bob Proulx wrote: > > spamassassin -d -t -D < mail.file | less > > Note: in the above command you did _not_ redirect STDERR to STDOUT
Oops. My bad. I should have shown that. I was concentrating on the options and neglected the right hand side. > > spamassassin -d -t -D 2>&1 | grep -i bayes | tee /tmp/sa.bayes-debug.out > > In this second command you _did_ redirect STDERR to STDOUT via > "2>&1" Yes. I actually did in both cases. I just didn't show it correctly in my email. The result for me is the same. Normally I have a script 'sat' that I pipe messages in through from my mailer. But for the test I did it from the command line to have a selfcontained test case. But normally I have this script. #!/bin/sh # spamassassin -d -t -D bayes 2>&1 | less # spamassassin -d -t -D 2>&1 | less spamassassin -d -t 2>&1 | less And as you can see I have all three combinations readily available. In order to have the content summary available I have removed the -D option entirely. That works. So this isn't urgent for me to figure out. But it is very odd. > My experience has been that I need to redirect STDERR to STDOUT in > order to catch the full output of > spamassassin -D -t Agreed. Thank you for your careful reading of my email. And I am embarrassed that I did not present it correctly. Bob
