SpamAssassin not parsing/seeing all headers in an amavisd/milter setup?!

[Ralf Hildebrandt]

Hi!

I'm using SpamAssassin in an amavisd-new/Milter setup. 

Recently, I found some mails from a mailinglist, which contained a
whopping 246 almost identical (!) DKIM Headers.

SpamAssassin - when invoked from amavisd-new (!) - was tagging these mails as spam, since it couldn't see
Date:/Subject: and other headers.

It reports:
X-Spam-Status: Yes, score=5.9 tagged_above=2 required=4 tests=[BAYES_00=-1.9,
        DKIM_SIGNED=0.1, DKIM_VALID=-0.1, EMPTY_MESSAGE=2.32,
        MISSING_DATE=1.36, MISSING_FROM=1, MISSING_HEADERS=1.021,
        MISSING_MID=0.497, MISSING_SUBJECT=1.799, RP_MATCHES_RCVD=-0.001,
        SPF_PASS=-0.001, TXREP=-0.845, CRM114.UNSURE(-3.25)=0.650]
        autolearn=no autolearn_force=no

When piping the mail to "spamassassin -D", I'm getting:

X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	HEADER_FROM_DIFFERENT_DOMAINS,RP_MATCHES_RCVD,SPF_PASS,T_DKIM_INVALID
	shortcircuit=no autolearn=no autolearn_force=no version=3.4.1

My interim "solution" is to delete the DKIM headers.

But the real question is: Why is SA not seeing all the headers in that
setup?

-- 
Ralf Hildebrandt                   Charite Universitätsmedizin Berlin
ralf.hildebrandt at charite.de        Campus Benjamin Franklin
https://www.charite.de             Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155