So far, since I got zdkimfilter to work properly I have recieved som
dkim=pass (usually from gmail) and some dkim=fails.. All seems ok. By
chance I compared the dkim=fail against what SpamAssassin said:
====== courier log
Jul 26 21:45:47 e350 courierfilter:
zdkimfilter[12888]:id=0000000000C804FC.0000000051F2D1E6.00003235:
verified: dkim=fail ([email protected], body hash mismatch,
stat=1) rep=0
Jul 26 21:45:47 e350 courierfilter:
zdkimfilter[12888]:id=0000000000C804FC.0000000051F2D1E6.00003235:
response: 250 Ok.
Jul 26 21:45:47 e350 courierd:
newmsg,id=0000000000C804FC.0000000051F2D1E6.00003235: dns;
repsys.dkim-reputation.org (repsys.dkim-reputation.org
[::ffff:46.4.178.182])
Jul 26 21:45:47 e350 courierd:
started,id=0000000000C804FC.0000000051F2D1E6.00003235,from=<[email protected]>,module=local,[email protected]!!8!12!/var/mail/domains/lechevalier.se/anders!!,addr=<[email protected]>
Jul 26 21:45:47 e350 courierd: Waiting. shutdown time=none, wakeup
time=none, queuedelivering=1, inprogress=1
Jul 26 21:45:47 e350 courierlocal:
id=0000000000C804FC.0000000051F2D1E6.00003235,from=<[email protected]>,addr=<[email protected]>,size=14751,success:
Message delivered.
Jul 26 21:45:47 e350 courierd:
completed,id=0000000000C804FC.0000000051F2D1E6.00003235
======
====== SpamAssassin log
Jul 26 21:45:43 e350 spamd[19824]: spamd: processing message
<[email protected]> for mail:8
Jul 26 21:45:47 e350 spamd[19824]: spamd: clean message (1.8/5.0)
for mail:8 in 3.8 seconds, 14419 bytes.
Jul 26 21:45:47 e350 spamd[19824]: spamd: result: . 1 -
BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HTML_IMAGE_ONLY_16,HTML_MESSAGE
scantime=3.8,size=14419,user=mail,uid=8,required_score=5.0,rhost=e350.lan.lechevalier.se,raddr=127.0.0.1,rport=48478,mid=<[email protected]>,bayes=0.499952,autolearn=no
======
What does body hash mismatch mean? Perhaps there are some headers not
checked by SA but are checked with zdkimfilter?
Spamassassin is run through pythonfilter-1.8. I believe pythonfilter
might be run first as it is doing greyfiltering. Are the added headers
from SpamAssassin the culprit?
These are the headers from the email above
======
Delivered-To: [email protected]
Return-Path: <[email protected]>
Authentication-Results: e350;
dkim=fail (body hash mismatch) [email protected]
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
e350.lan.lechevalier.se
X-Spam-Level: *
X-Spam-Status: No, score=1.8 required=5.0 tests=BAYES_50,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,HTML_IMAGE_ONLY_16,HTML_MESSAGE autolearn=no
version=3.3.2
Received: from repsys.dkim-reputation.org (repsys.dkim-reputation.org
[::ffff:46.4.178.182])
by e350 with ESMTP; Fri, 26 Jul 2013 21:45:42 +0200
id 0000000000C804FC.0000000051F2D1E6.00003235
Received-SPF: none (Address does not pass the Sender Policy Framework)
SPF=MAILFROM; [email protected];
remoteip=::ffff:46.4.178.182;
remotehost=repsys.dkim-reputation.org;
helo=repsys.dkim-reputation.org; receiver=mail.tnonline.net;
Received: from repsys.dkim-reputation.org (localhost [127.0.0.1])
by repsys.dkim-reputation.org (Postfix) with ESMTP id 5C210398384
for <[email protected]>; Fri, 26 Jul 2013 21:38:30 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=dkim-reputation.org; h=to
:subject:date:from:reply-to:message-id:mime-version:content-type
; s=default; bh=Zbv3XTgeAhngG+jukxXJGBaEkcA=; b=eYMOEw2x9oUjhWgh
MMBsrGuxNzz8MH8OAPpf7aRWvn0LtSBc93wXeSFqIe1LginJBp0VuGR9OaReUNH8
3D7ZRo/b03lPv9FWilixpc3vYEmlMIdSxUxbrY2uKrao/DsMoc3+xOlPppRRZPZa
MnbvRRZodqNEmyLAaGu626ME9Hc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=dkim-reputation.org;
h=to:subject
:date:from:reply-to:message-id:mime-version:content-type;
q=dns;
s=default; b=I/0X89H+UeDCXaLgwxI33JhjCuIIJpgfPtuzWK0XZyTCybtFX6
A6SfGecLWCPZpm2XofNtD4wkWMdfK7X4H9NFKWkgem5lUdapGKWFmFsdazDh+TPM
FoU77hgQr1eiljuaUq9C4WpuERorZxyn3jP7UG3DMATnZNxSgCBCY/LdM=
Received: by repsys.dkim-reputation.org (Postfix, from userid 33)
id 5497B3983D1; Fri, 26 Jul 2013 21:38:30 +0200 (CEST)
To: [email protected]
Subject: Proposal for DKIM-Reputation-Project
[f688b566190ceed5d63f440b7dc3b38e67d68b04]
Date: Fri, 26 Jul 2013 19:38:30 +0000
From: DKIM Reputation Project <[email protected]>
Reply-to: DKIM Reputation Project <[email protected]>
Message-ID: <[email protected]>
X-Priority: 3
MIME-Version: 1.0
Content-Type: multipart/related; type="text/html";
boundary="b1_5873b4b23ff3d57de56472c8c0240f9e"
Received-SPF: none (Address does not pass the Sender Policy Framework)
SPF=FROM; [email protected];
remoteip=::ffff:46.4.178.182;
remotehost=repsys.dkim-reputation.org;
helo=repsys.dkim-reputation.org; receiver=mail.tnonline.net;
--b1_5873b4b23ff3d57de56472c8c0240f9e
Content-Type: multipart/alternative;
boundary="b2_5873b4b23ff3d57de56472c8c0240f9e"
--b2_5873b4b23ff3d57de56472c8c0240f9e
Content-Type: text/plain; charset = "UTF-8"
Content-Transfer-Encoding: quoted-printable
======
Thanks for any input.
~A
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
