> Since I upgraded, I'm seeing bits of the X-Spam-Header message
> in my mail bodies, like this :
The latest version changed things to make life on Windows systems better.
Instead of always using a \n for a line ending, it looks at the kind of line
ending it got on the first line of the input file, and uses that for the
output file. Thus, if \n comes in, \n will go out. If \r\n comes in, \r\n
will go out.
In theory this should work fine in all cases. But we know about theories
and the real world.
>From what you are seeing I would make the following guesses:
The input to SA has the first line encoded with \r\n, so that is what SA is
using.
Somehow that line wrap case was encoded differently upstream, and after SA
stuck on the \r\n ended up with something like \r\r\n or \n\r\n.
Alternately, the thing folowing SA works correctly with \r\n terminated
lines, except in the case of a continuation line, and there it gets
confused.
Loren
