On Tue, May 09, 2006 at 07:26:29PM +0200, Sietse van Zanen wrote: > Somehow the escape sequence when inserting headers into messages. Has > changed from \n\t to \n\r\t
Sort of, "\r\n\t".
> I wonder why the escape sequence suddenly includes a carriage return
> (\r) together with the newline (\n) and tab (\t). I use this machine as
> a spam removal gateway for my Exchange environment and Exchange is not
> amused by the carriage return and writes the part of the header after
> that and any other headers directly into the body of the message.
This has been discussed before, but the basics are that SpamAssassin
was previously always just adding in "\n", which caused problems on some
platforms where the line endings were supposed to be "\r\n". After much
debate about which way ("\r\n" vs "\n" vs ...) was correct, and whether
or not changing the behavior was a UI/API change versus a bug fix, etc,
we added in a patch to have the line ending determined and then use
that when adding in headers. Now SpamAssassin "does the right thing"
no matter what kind of line ending you throw at it. However, while half
the people are happy that this happens now, the other half are annoyed
that the previous "\n"-only behavior isn't the default anymore.
> I am using spamassassin 3.1.1, milter 0.3.0 sendmail 8.12.10 on redhat
> enterprise 3.0
[...]
> Anybody has any ideas how this can be fixed?
There's some difference of opinion around this question, but my general
opinion is that there should be an update to spamass-milter which
properly handles the newlines either way. I'm not sure whether or not
that's happened yet.
--
Randomly Generated Tagline:
A liar isn't believed even when he speaks the truth.
pgpywEx6eybTX.pgp
Description: PGP signature
