Incoming mail DKIM failures on Build 352 & 353

Use this forum if you want to discuss a problem or ask a question related to a hMailServer beta release.
Post Reply
bazporter
Normal user
Normal user
Posts: 98
Joined: 2005-06-03 16:14

Incoming mail DKIM failures on Build 352 & 353

Post by bazporter » 2009-07-03 18:43

I have noticed on builds 352 & 353 that I am seeing DKIM failures on emails from senders that I have never seen this issue with on previous builds, and when these mails pass through SpamAssassin the DKIM headers are validated as passing. Here is an example header showing the hMailServer headers and SpamAssassin headers:

Code: Select all

Return-Path: snapshot@email.warehouseexpress.com
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on munged.munged.local
X-Spam-Level: 
X-Spam-Status: NO, score=-4.8 required=5.0 tests=BAYES_00,BP_HEADER_HMS,
	DKIM_SIGNED,DKIM_VERIFIED,DK_POLICY_SIGNALL,DK_SIGNED,HS_INDEX_PARAM,
	HTML_IMAGE_RATIO_04,HTML_MESSAGE,LOW_PRICE,RDNS_NONE autolearn=no
Received: from mta109d.dm-4.com ([64.40.119.109]) by munged.munged.net ; Fri, 3 Jul
 2009 16:01:07 +0100
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=x; d=email.warehouseexpress.com;
 h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type;
 i=snapshot@email.warehouseexpress.com; bh=S4kczdz0mZ3LEl58sdWlqvZi8mg=;
 b=HaCFybCpli16ort6Ih3QShnpOpwaXDnAtSMzkIBKRbsXQjIe3sBMqEUknM5iqBHWWVIwrrkQyFlj
 qT69wgtHRCcY2cjrGgkl9a4K9lkOppUvOEKf8oWsJANRKPnz82Ap68De3ZtM/3Zd9x4XMqRDZVZd
 NeA19mDHIs1ZZf+HDNw=
DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=x; d=email.warehouseexpress.com;
 b=IMPQCH95hLUsYIMgpLfEWseGiJoboXMPWmw0FKgiHldAu+R+ZlmZMytTjtxMJzqP8szHbMlRjMOq
 kAFTZRqV/qanR2QyezoIkFws5jpga5oFVKTeDkZ5qphHq2sJCJXsfEbh2vt0yrSLhTkPLvlbvTWl
 4c+xuQa25oKMgm3fQsY=;
Received: from dm-mta3 (127.0.0.1) by mta109d.dm-4.com (PowerMTA(TM) v3.5r8sb1) id
 h9oetk0nqjo1 for <munged@munged.net>; Fri, 3 Jul 2009 08:03:49 -0700
 (envelope-from <snapshot@email.warehouseexpress.com>)
Message-ID: <2hoflnol0kzacna2fwt35drewqf0pl@dm.msg>
Date: Fri, 03 Jul 2009 15:03:49 GMT
From: "Warehouse Express" <snapshot@email.warehouseexpress.com>
Reply-To: snapshot@email.warehouseexpress.com
To: "munged@munged.net" <munged@munged.net>
Subject: Fuji Compact Cameras plus Half Price Accessories
X-Mailer: 2HOFLN OL0KZAC NA2FWT3 5DREWQF0PL
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary=dmboundary
X-hMailServer-Spam: YES
X-hMailServer-Reason-2: Rejected by DKIM. - (Score: 5)
X-hMailServer-Reason-Score: 5
X-EsetId: D46FC425645625318F2B
Has anything been changed in the code in these recent builds that might be affecting this?

Regards
Barry

User avatar
martin
Developer
Developer
Posts: 6834
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: Incoming mail DKIM failures on Build 352 & 353

Post by martin » 2009-07-05 14:06

No, no changes have been made to DKIM functionality in latest builds.

Do you have debug logging enabled? Suggest you check the log. If you look for DKIM, you should see why the DKIM verification failed...

bazporter
Normal user
Normal user
Posts: 98
Joined: 2005-06-03 16:14

Re: Incoming mail DKIM failures on Build 352 & 353

Post by bazporter » 2009-07-05 17:47

Hi Martin,

I have enabled debug logging since I noticed it. It happened on a group of emails that I get infrequently so I'll keep and eye on it and when/if it happens again I'll respond back.

Many thanks.

Post Reply