[me, explaining my test run of SA]
> 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
[dman responded]
> How did you invoke mutt?
> Was it
> mutt -f $out
> (with $out from above)
No, I ran mutt -f greg-spam-out.mdir. Note that that is a maildir; mutt
correctly found all the files in greg-spam-out.mdir/cur. And it seems
to have obeyed Content-length (or possibly Lines) when reading the
message.
Anyways, this is no longer a SpamAssassin issue. It looks like mutt's
just being a little too obedient of the headers.
> 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)
For the record, that's exactly what I did -- check my shell code again.
Greg
--
Greg Ward - software developer [EMAIL PROTECTED]
MEMS Exchange http://www.mems-exchange.org
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
