On 23 January 2002, Craig Hughes said:
> 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.
No -- I ran a loop like this:
for msg in greg-spam.mdir/cur/* ; do
echo $msg
out=greg-spam-out.mdir/cur/`basename $msg`
spamassassin -c ~/share/spamassassin -t < $msg> $out
done
The only console output from this was the 68 filenames in
greg-spam.mdir/cur. When I look directly (ie. with less) at one of the
output filenames in greg-spam-out.mdir/cur, the SA footer is there.
When I use mutt to read greg-spam-out.mdir, the SA footer is not shown.
Presumably mutt only reads Content-length bytes after the header.
This *is* kind of an artificial situation, since this is mail that's
already been received, delivered, and read; I think the Content-length
and Lines headers are added in the last step. In the wild, then, they
would not be present when SA is reading the message.
But still -- if you're going to munge the body, you should at least look
for Content-length and Lines and munge them too. (IMHO.)
Greg
--
Greg Ward - Linux geek [EMAIL PROTECTED]
http://starship.python.net/~gward/
"He's dead, Jim. You get his tricorder and I'll grab his wallet."
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
