Re: [SAtalk] SA 2.0 flags sample-nonspam.txt

[Craig Hughes]

I'm guessing (from memory w/out actually looking) that the report is going to stderr and the processed message to stdout, so that's why mutt wasn't seeing it, and why correctly content-length and lines headers aren't touched.  If you're processing lots of messages, I'd advise using spamd/spamc instead of spamassassin, and in any case, I'd advise using -P not -t for actual processing as opposed to "testing"

C

On Wed, 2002-01-23 at 15:36, Greg Ward wrote:

On 23 January 2002, Craig Hughes said:
> Nothing unusual here.  spamassassin -t will always append that footer,
> just to let you know in detail which tests matched.  spamassassin -P
> will not do anything except add the X-Spam-Status: No line.

Ahh, I see.  I was confused because I ran spamassasin -t on a maildir
full of recent spam (and my complaints about it) to evaluate SA on
multiple messages.  Turns out I wasn't seeing the footer because mutt
was obeying either the "Content-length" or "Lines" header.  (These might
have been added by mutt in the first place; this maildir started life as
an mbox, and I just converted it so I could access one message at a time
more easily.)

Perhaps SpamAssassin should munge the Content-Length and/or Lines
headers when it adds a header or footer?

        Greg
-- 
Greg Ward - Unix nerd                                   [EMAIL PROTECTED]
http://starship.python.net/~gward/
God is real, unless declared integer.

_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk