spam filtering errors

[Ken Thomases]

On Jan 31, 2014, at 7:59 AM, Jonas Maebe wrote:

> Since the latest update of the mailing list server, a lot of mails sent to this list are wrongly classified as spam by CodeWeavers' mail server. I've already sent a mail about this to postmaster at codeweavers.com several months ago, but got no reply and nothing appears to have changed.
> 
> It seems that the main culprit is the "SINGLE_HEADER_3K" spamassassin check, in combination with a very low spam score threshold (1.0). Below is an example from Stefan Dösinger's last mail (titled "dpnet patches").

> X-Spam-Flag: YES
> X-Spam-Report: Spam detection software, running on the system "wine.codeweavers.com", has
> identified this incoming email as possible spam.  The original message
> has been attached to this so you can view it (if it isn't spam) or label
> similar future email.  If you have any questions, see
> the administrator of that system for details.
> Content preview:  Hi Alistair, A while ago I promised to have a closer look
>  at your dpnet patches. ItXs a bit delayed, but here are some comments. How
>   serious are you about dplay? Do you intend to do more work towards implementing
>   it, or is that just wishful thinking on my part? [...]
> Content analysis details:   (1.1 points, 1.0 required)
> pts rule name              description
> ---- ---------------------- --------------------------------------------------
> 3.0 SINGLE_HEADER_3K       A single header contains 3K-4K characters
> 0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
>                            (stefandoesinger[at]gmail.com)
> -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
>                            [score: 0.0000]
> 0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid

I do not see this in the raw email source for that same message as I received it.  Would a second SpamAssassin-enabled server (mail.codeweavers.com) have stripped the first server's analysis?

-Ken