News:

Bored?  Looking to kill some time?  Want to chat with other SMF users?  Join us in IRC chat or Discord

Main Menu

DKIM Failing Only From SMF Via SMTP

Started by pftq, September 10, 2016, 03:13:55 PM

Previous topic - Next topic

pftq

I'm sending emails via SMTP port 465 and getting failed DKIM signatures in the headers.  Any other script I have as well as sending emails from cPanel directly result in properly signed DKIM signatures.  SMF2 also signs the DKIM properly just fine, so it seems code specific to how SMF1 has been writing its emails/headers.  SPF and DMARC pass just fine, fortunately, but I'd still like to get to the bottom of this.


Delivered-To: [email protected]
Received: by 10.202.3.2 with SMTP id 2csp958024oid;
        Sat, 10 Sep 2016 12:06:24 -0700 (PDT)
X-Received: by 10.157.38.202 with SMTP id i10mr12892292otd.79.1473534384876;
        Sat, 10 Sep 2016 12:06:24 -0700 (PDT)
Return-Path: <[email protected]>
Received: from -- (--. [--])
        by mx.google.com with ESMTPS id h13si6400215otd.285.2016.09.10.12.06.24
        for <[email protected]>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Sat, 10 Sep 2016 12:06:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of [email protected] designates -- as permitted sender) client-ip=--;
Authentication-Results: mx.google.com;
       dkim=fail [email protected];
       spf=pass (google.com: domain of [email protected] designates -- as permitted sender) [email protected];
       dmarc=pass (p=REJECT dis=NONE) header.from=pftq.com
Received: from -- ([--])
by -- with esmtps (TLSv1.2:DHE-RSA-AES256-SHA:256)
(Exim 4.85)
(envelope-from <[email protected]>)
id 1binbl-0003TU-DJ
for [email protected]; Sat, 10 Sep 2016 15:06:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=pftq.com;
s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:Date:
Reply-To:From:To:Subject:Sender:Message-ID:Cc:Content-ID:Content-Description:
Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
List-Post:List-Owner:List-Archive;
bh=wHXwN3mb8EXxQXYWbXhvWhb9b9NuNBZu+vi5ZzGVns8=; b=ZcLg5+vsZKSbiRS6KuzFb9+ZEv
OxV2oin7QFUbXoC0H3vNqueZo8DP9h8bc5Hfwzb0CEI+3avsaz+F/2jElKInBhrH4N8zvWgYrrXz5
xCR1XF0S1GxGDHCFgvxiTgvX/lBvJpJ2QTTFtozYrd6cKvzFJj5DmcpVoB5nJ8VuSIsOPz93R5NoZ
bBP+4m5j15Zpyh+yIOlMQY5Gv/QtHnB2fg0cYPhNaBDd/rFr76Dkkee69M1y0l0vN96X0OnVHf2Ru
EHbw6R0orKyHenFW822lgZBT5ByYYpjr+PuT0vJq7DdnIufVemZpoBpc+qyGwa7WHFbkivV7/M/i1
YQzYJ8Gg==;
Received: from [--] (port=42035 helo=ssl://pftq.com)
by -- with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from <[email protected]>)
id 1binbZ-001pP3-Hn
for [email protected]; Sat, 10 Sep 2016 15:06:21 -0400
Subject: Re: test
To: <[email protected]>
From: "pftq" <[email protected]>
Reply-To: <[email protected]>
Date: Sat, 10 Sep 2016 19:06:21 -0000
X-Mailer: SMF
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="SMF-ce2b05d21745e8b2cdc0c7f8ba9cc582"
Content-Transfer-Encoding: 7bit

Illori

SMF 1.1.* is no longer getting support with patches/upgrades. you will need to upgrade to SMF 2.0 at some point as SMF 1.1.* does not support the current versions of PHP. i doubt you will find anyone with much interest in fixing an issue in SMF 1.1.* as its code is so old and outdated.

pftq

Yeah - just seeing if anyone might happen to have come across this or have any ideas.

Advertisement: