From users-return-121693-archive-asf-public=cust-asf.ponee.io@spamassassin.apache.org  Tue Jan 14 13:38:20 2020
Return-Path: <users-return-121693-archive-asf-public=cust-asf.ponee.io@spamassassin.apache.org>
X-Original-To: archive-asf-public@cust-asf.ponee.io
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [207.244.88.153])
	by mx-eu-01.ponee.io (Postfix) with SMTP id 38CCB18061A
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 14 Jan 2020 14:38:20 +0100 (CET)
Received: (qmail 62641 invoked by uid 500); 14 Jan 2020 13:38:19 -0000
Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@spamassassin.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@spamassassin.apache.org>
List-Post: <mailto:users@spamassassin.apache.org>
List-Id: <users.spamassassin.apache.org>
Delivered-To: mailing list users@spamassassin.apache.org
Received: (qmail 62630 invoked by uid 99); 14 Jan 2020 13:38:18 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jan 2020 13:38:18 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 846041812B7
	for <users@spamassassin.apache.org>; Tue, 14 Jan 2020 13:38:17 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=6.31
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, SPF_HELO_PASS=-0.001,
	SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled
Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
	dkim=pass (1024-bit key) header.d=wombaz.de
Received: from mx1-ec2-va.apache.org ([10.40.0.8])
	by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
	with ESMTP id A0YnKhB9uTU3 for <users@spamassassin.apache.org>;
	Tue, 14 Jan 2020 13:38:15 +0000 (UTC)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=87.230.18.40; helo=mail.wombaz.de; envelope-from=alex@wombaz.de; receiver=<UNKNOWN> 
Received: from mail.wombaz.de (mail.wombaz.de [87.230.18.40])
	by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id CB390BC5C3
	for <users@spamassassin.apache.org>; Tue, 14 Jan 2020 13:38:14 +0000 (UTC)
Received: from [IPv6:2a02:908:121:2320:525:3cc7:c511:cb40] (unknown [IPv6:2a02:908:121:2320:525:3cc7:c511:cb40])
	(Authenticated sender: alex@wombaz.de)
	by mail.wombaz.de (Postfix) with ESMTPSA id B059AA037B
	for <users@spamassassin.apache.org>; Tue, 14 Jan 2020 14:38:06 +0100 (CET)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.101.5 at mail.wombaz.de
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wombaz.de;
	s=default; t=1579009086;
	bh=/Vij8YuC6NRPcTDF2S3BfvPhcQId4IDCaIlyFHRlOw4=;
	h=To:From:Subject:Date:From;
	b=AMeU+Pb/XVWJs+cQIQLccOJboMW1NmLm5ADtg8FaA5ySmxti8giZgGlgUVexn17TD
	 +WzA5nUwM4WyzkBpYB5fBEdSF78C/dztaDkczuzi+YRgBJCH72sSzq4O4jydnjfnnA
	 acZl4wVBov7WE8hamiaoWqQeq10Sufu2DQiW8Auc=
To: users@spamassassin.apache.org
From: Alex Woick <alex@wombaz.de>
Subject: Spamassassin always says DKIM_INVALID
Message-ID: <7e37bf65-e028-3011-0503-e6b3ff598688@wombaz.de>
Date: Tue, 14 Jan 2020 14:38:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.3.1
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------AEFC197B93F6175A0656A549"
Content-Language: de-DE

This is a multi-part message in MIME format.
--------------AEFC197B93F6175A0656A549
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Spamassassin (3.4.3, the same with previous) declares all or almost all 
the incoming DKIM-signed messages as DKIM_INVALID, and I'm not 
understanding why.
I'm running opendkim on the mail server as milter with Postfix, and the 
opendkim headers say the same dkim signatures are all valid.

Example headers of some mail from this list.
Opendkim says ok:

Authentication-Results: mail.wombaz.de;
	dkim=pass (2048-bit key) header.d=linkcheck.co.uk header.i=@linkcheck.co.uk header.b="PXrrNHdB"

But Spamassassin says it's invalid:

X-Spam-Status: No, score=-15.5 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS,TXREP,
	USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.3

Link to complete message:
https://pastebin.com/raw/1DLtnuRX

Spamassassin is running as spamc/spamd, and is embedded in Postfix with 
spamass-milter. System is running on CentOS 7.

Postfix milter config is this:

smtpd_milters =
   unix:/var/run/opendkim-postfix/sock,
   unix:/var/run/opendmarc-postfix/sock,
   unix:/var/run/clamav-milter/clamav-milter.socket,
   unix:/run/spamass-milter/postfix/sock

Any idea how to find out why Spamassassin isn't able to successfully 
verify dkim sigs, while at the same time Opendkim says it's valid? I 
just activated the dkim plugin of Spamassassin but didn't configure 
anything dkim-related, since there is nothing specific to do.

Alex

--------------AEFC197B93F6175A0656A549
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Spamassassin (3.4.3, the same with previous) declares all or almost
    all the incoming DKIM-signed messages as DKIM_INVALID, and I'm not
    understanding why.<br>
    I'm running opendkim on the mail server as milter with Postfix, and
    the opendkim headers say the same dkim signatures are all valid.<br>
    <br>
    Example headers of some mail from this list.<br>
    Opendkim says ok:<br>
    <pre>Authentication-Results: mail.wombaz.de;
	dkim=pass (2048-bit key) header.d=linkcheck.co.uk <a class="moz-txt-link-abbreviated" href="mailto:header.i=@linkcheck.co.uk">header.i=@linkcheck.co.uk</a> header.b="PXrrNHdB"

</pre>
    But Spamassassin says it's invalid:<br>
    <pre>X-Spam-Status: No, score=-15.5 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS,TXREP,
	USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.3

</pre>
    Link to complete message:<br>
    <a href="https://pastebin.com/raw/1DLtnuRX">https://pastebin.com/raw/1DLtnuRX</a><br>
    <br>
    Spamassassin is running as spamc/spamd, and is embedded in Postfix
    with spamass-milter. System is running on CentOS 7.<br>
    <br>
    Postfix milter config is this:<br>
    <pre>smtpd_milters =
  unix:/var/run/opendkim-postfix/sock,
  unix:/var/run/opendmarc-postfix/sock,
  unix:/var/run/clamav-milter/clamav-milter.socket,
  unix:/run/spamass-milter/postfix/sock

</pre>
    Any idea how to find out why Spamassassin isn't able to successfully
    verify dkim sigs, while at the same time Opendkim says it's valid? I
    just activated the dkim plugin of Spamassassin but didn't configure
    anything dkim-related, since there is nothing specific to do.<br>
    <br>
    Alex<br>
  </body>
</html>

--------------AEFC197B93F6175A0656A549--