On Wed, Mar 15, 2006 at 04:31:24PM -0500, Paul Stavrides wrote: > The problem is an extra an extra "0D" in the X-Spam-Checker-Version > line, such that I see an "...0D 0D 0A 09..." by the time I look at the > headers in Windows. The line is getting munged when it is getting > wrapped.
Interesting. I was thinking it was the spamass-milter code... But researching things a little more, it looks like it's actually the milter API/library: http://www.milter.org/milter_api/smfi_chgheader.html "If longer headers are needed, make them multi-line. To make a multi-line header, insert a line feed (ASCII 0x0a, or \n in C) followed by at least one whitespace character such as a space (ASCII 0x20) or tab (ASCII 0x09, or \t in C). The line feed should NOT be preceded by a carriage return (ASCII 0x0d); the MTA will add this automatically." Previously, the milter could assume that folding was going to happen via "\n\t", but now it's "\r\n\t". Carl Brewer: > Is it possible to just turn off the X-Spam-Status header as a quick > workaround? I tried this in my local.cf but it didn't seem to work : > > report_safe 0 > remove_header all X-Spam-Status It'd be "remove_header all Status". You can try it, though if the problem is wrapping, you may end up with problems with Checker-Version which you can't disable (short of editing SA modules). Looking at the spamass-milter code, it looks like "-M" may also be a work-around for you (disables all markup). -- Randomly Generated Tagline: Do nothing unless you must, and when you must act -- hesitate.
pgpJ4OWNwnM4C.pgp
Description: PGP signature
