https://bugs.exim.org/show_bug.cgi?id=2148
Heiko Schlittermann <hs@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hs@???
--- Comment #2 from Heiko Schlittermann <hs@???> ---
(In reply to Martin Nicholas from comment #0)
> I'm seeing log lines like this with the Debian build:
> 20170713-smtp25-mx0-mainlog:2017-07-13 08:05:19 1dVZ7f-0006EU-P1 DKIM:
> d=canalrivertrust.org.uk s=mandrill c=relaxed/relaxed a=rsa-sha256 b=1024
> i=ikipedia.org/wiki/.mu
> 20170712-smtp25-mx6-mainlog:2017-07-12 16:19:36 1dVKMR-0005cX-Ab DKIM:
> d=info.petsathome.com s=petsathome c=relaxed/relaxed a=rsa-sha1 b=1024
> i=ars.comâ
>
> Sometimes [verification succeeded] appears at the end of the offending log
> line, sometime it doesn't.
> Other log lines from other DKIM signers look ok.
>
> In the message body the i= parameter is sensible:
> Received: from mail136-6.atl41.mandrillapp.com ([198.2.136.6])
> by mx0.tvscience.co.uk with esmtps (TLS1.2:RSA_AES_256_GCM_SHA384:256)
> (Exim 4.89)
> (envelope-from
> <bounce-md_10513099.596729ad.v1-355b6549e3dd422e8b4b35877a894c3d@mandrillapp.
> com>)
> id 1dVZ7f-0006EU-P1
> for cart-throw@???; Thu, 13 Jul 2017 08:05:19 +0000
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=mandrill;
> d=canalrivertrust.org.uk;
> h=From:Subject:Reply-To:To:Message-Id:Date:MIME-Version:Content-Type;
> i=notices@???;
> bh=3m2yK5xE2CuzE1v9+AulwlHPa/qZ+JOFsyQFkIdqHsI=;
> b=pGtSDWjppFScQmpHCva9Z28zPrXHC0CmLfpWMFDebIFgAYDlacdo7IdUiOTSyu/
> 48bWxSBF+ybi7
>
> soCiAwFS3F8CJHfkcu/BqoP8JX1fG1tNBW9RfjbaPK6bJ2FJDm49B0p6D7/lFoJoihlZ36UNDXFJ
> dS16Q1fQnqd006rfyMY=
>
> Looks to me like something broke after the upgrade to Debian Stretch. Since
> then all log entries for canalrivertrust.org.uk & info.petsathome.com have
> been garbage. There are other offenders too, not all of which are Mailchimp
> clients.
>
> I run exim4 using inetd (actually tcpsvd).
>
> Can dig further if needed.
The official repo contains a exim-4_89+fixes branch. This branch includes a fix
for your issue.
As Andreas statet already, if you use a current Debian package, the
distro package should include the fix already.
--
Heiko
--
You are receiving this mail because:
You are on the CC list for the bug.
