Subject: problems with new spamassassin 3.1.1 and spamass-milter 0.3.0
To: None <tech-pkg@NetBSD.org>
From: Carl Brewer <email@example.com>
Date: 03/16/2006 14:57:00
If you're running sendmail and spamass-milter 0.3.0 with
spamassassin 3.1.1, you may need to be aware of the following :
Excerpt from my discussion on the spamassassin mailing list.
(Theo Van Dinter) :
> The problem is caused by a specific feature that was added into
> SpamAssassin in 3.1.1 -- namely that we'll use the same line endings
> original message uses (LF vs CRLF). spamass-milter relied on the
> behavior (always use LF), which happened to work well with what libmilter
> So in this case, I would expect the spamass-milter code to be modified
> to take into account that line endings could either be CRLF (3.1.1 and
> beyond) or LF (3.1.0 and previous).
> (alternately, libmilter could be modified to handle either LF or
> would probably be easier to code, but harder to get that API changed...)
The spamassassin people suggest that they are now doing the right thing,
and that spamass-milter needs to change to deal with this on UNIX
systems so it feeds limbilter the right characters to prevent
the headers getting broken up and leaking.
I've send a headsup to the spamass-milter list, but this may bite
someone here before that gets fixed? A workaround is to add -M to
the spamass-milter startup, which tells it not to add any