On Wed, 15 Mar 2006, Theo Van Dinter wrote:
> 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 that the
> original message uses (LF vs CRLF). spamass-milter relied on the previous
> behavior (always use LF), which happened to work well with what libmilter
> expected.
>
> 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).
Silly question; would it be sufficient for the milter to just canonicalize
the message that it passes to SA by converting CRLF to a plain LF?
Or better, do the inverse of SA; for it to look at the first line of
the message and if terminated with a plain 'LF' take no special action
but if terminated with a 'CRLF' then go into canonicalize mode and
convert all instances of 'CRLF' to plain 'LF'.
Thus if SA (3.1 or 3.1.1) saw just 'LF' line endings should it
return data in the form that libmilter expects?
Dave
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
