On Wed, Jan 23, 2002 at 06:59:58PM -0500, Greg Ward wrote:
| 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.
How did you invoke mutt?
Was it
mutt -f $out
(with $out from above)
If so, then mutt sees an mbox folder, not a single message, and I
expect it would obey Content-Length: there. I think the mail delivery
system puts that in (certainly for the Lines: header it is the
delivery system).
Instead try putting all you $out into a separate maildir folder and
see what mutt does with it then. (I don't know, but I expect it to
not look at any such header)
-D
--
Folly delights a man who lacks judgement,
but a man of understanding keeps a straight course.
Proverbs 15:21
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
