Re: [SAtalk] Getting a full report on uncaught spam

On Mon, Jun 30, 2003 at 03:26:37PM -0600, Mike Mills wrote: > /usr/bin/spamassassin -D spam ^ Missing redirection operator < ? -- Spam poison - don't use! ---> [EMAIL PROTECTED] <--- --- This SF.Net email sponsored

Re: [SAtalk] Getting a full report on uncaught spam

On Mon, Jun 30, 2003 at 03:26:37PM -0600, Mike Mills wrote: > info given in messages caught as spam. Am I invoking spamassassin > incorrectly? Is it just really slow? Yes, it's waiting for input on STDIN, it doesn't take a filename. ie: spamassassin -D < message -- Randomly Generated Taglin

Re: [SAtalk] Getting a full report on uncaught spam

At 03:26 PM 6/30/2003 -0600, Mike Mills wrote: I'm having trouble running spamassassin to find out why a spam was not caught. I've tried invoking as follows: /usr/bin/spamassassin -D spam or ~/sausr/bin/spamassassin -D spam where spam is the message exported to a file. In both cases the proces

[SAtalk] Getting a full report on uncaught spam

I'm having trouble running spamassassin to find out why a spam was not caught. I've tried invoking as follows: /usr/bin/spamassassin -D spam or ~/sausr/bin/spamassassin -D spam where spam is the message exported to a file. In both cases the process seems to get caught in an infinite loop,