Hi Tom,
On Thu, 28 Oct 2004, tom shepherd wrote: > > hello, > > > i'm getting some problems with my SA installation, and hope someone can > help. > > i'm using SpamAssassin 3.0.1 on OS X 10.3.4 > > > > the problem is that when i run: > > # spamassassin -tD > spam-sample This is the problem. You're redirecting the stdout output of spamassassin to the file spam-sample. This is assuming that MacOSX shell behavior is the same as just about every other *nix (I'd hope that it is). Here's what you want: spamassassin -tD < spam-sample or alternatively to redirect all of the output, both stdout and stderr to a file spamassassin -tD < spam-sample >& outputfile <snipped> > but instead, i get this: > > debug: SpamAssassin version 3.0.1 > debug: Score set 0 chosen. > debug: running in taint mode? yes > debug: Running in taint mode, removing unsafe env vars, and resetting > PATH > debug: PATH included '/bin', keeping. > debug: PATH included '/sbin', keeping. > debug: PATH included '/usr/bin', keeping. > debug: PATH included '/usr/sbin', keeping. > debug: Final PATH set to: /bin:/sbin:/usr/bin:/usr/sbin spamassassin is waiting for input on stdin. I think that the taint mode is normal. It's detecting that you ran it from a user context with a full path and lots of "unnecessary" environment variables. It works around this by resetting the path and undefining a bunch of env variables. -Greg
