dkim fails ?

[Mark Martinec]

Benny,

> X-Spam-Status: No, score=0.457 tagged_above=-100 required=5
>     tests=[ALL_TRUSTED=-0.1, AWL=0.767, DKIM_ADSP_ALL=0.8,
>     KHOP_THREADED=-1.5, NO_X_MAILER=0.5, T_RP_MATCHES_RCVD=-0.01]
>     autolearn=unavailable
> Authentication-Results: localhost.junc.org (amavisd-new); dkim=pass
>     header.i=@junc.org

> dev-perl/mail-dkim 0.38
> mail-filter/amavisd-new 2.6.3-r2
> mail-filter/spamassassin 3.3.1-r4
> mail-mta/postfix 2.8.3

> why do it have dkim_adsp_all when dkim_valid in spamassassin ?

Apparently SpamAssassin did not see any DKIM signature in the
mail header section, let alone finding a valid one, otherwise
you'd see rules DKIM_SIGNED and DKIM_VALID rules hitting too.

Have you by any chance set score for these two rules to zero?
Is the Authentication-Results inserted by the same amavisd/SA
pair as the X-Spam-Status, or is there any other processing
going on inbetwen?


On Tuesday May 31 2011 20:17:47 Andreas Schulze wrote:
> ADSP is Author Domain Signing Practices
> in short: the domainowner tells the world the he/she/it signs _ALL_ mail
> an tells the verifier also what to do it an unsigned mail is seen.
> $ dig _adsp._domainkey.junc.org txt +short
> "dkim=all"
> so nothing failed but a higher spamscore for signing all mails
> wonders me too.

The DKIM_ADSP_* rules only hit in the absence of a DKIM_VALID.

  Mark