Received header for spamc: Received: from mta12.mc.ihg.com
(unknown)#015#012#011by postoffice-2.autoelect.com (8.13.0/8.13.0) with
SMTP id unknown#015#012#011Mon, 12 Jul 2021 11:17:57
-0600#015#012#011(envelope-from
<bounce-34_html-3203040-15955-514005572-29...@bounce.mc.ihg.com>);#015
output "Received: from mta12.mc.ihg.com (unknown)#015#012#011by
postoffice-2.autoelect.com (8.13.0/8.13.0) with SMTP id
unknown#015#012#011Mon, 12 Jul 2021 11:17:57
-0600#015#012#011(envelope-from
<bounce-34_html-3203040-15955-514005572-29...@bounce.mc.ihg.com>);#015#012"
output "Received: by mta12.mc.ihg.com id hthska2fmd4d for
<emailaddrremo...@autoelect.com>; Mon, 12 Jul 2021 17:17:56 +0000
(envelope-from
<bounce-34_html-3203040-15955-514005572-29...@bounce.mc.ihg.com>)#015#012"
yields from spamd
received-header: unparseable: from mta12.mc.ihg.com (unknown) by
postoffice-2.autoelect.com (8.13.0/8.13.0) with SMTP id unknown Mon, 12
Jul 2021 11:17:57 -0600 (envelope-from
<bounce-34_html-3203040-15955-514005572-29...@bounce.mc.ihg.com>);
---
but when called via procmail call to spamc gives
received-header: parsed as [ ip=13.111.173.13 rdns=mta12.mc.ihg.com
helo=mta12.mc.ihg.com by=postoffice-2.autoelect.com ident= envfrom=
intl=0 id=050749FFD0 auth= msa=0 ]
received-header: relay 13.111.173.13 trusted? no internal? no msa? no
which has no unparseable relay errors.
-----
In the e-mail text the received lines are:
Received: from mta12.mc.ihg.com (mta12.mc.ihg.com [13.111.173.13])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by postoffice-2.autoelect.com (Postfix) with ESMTPS id 050749FFD0
for <emailaddrremo...@autoelect.com>; Mon, 12 Jul 2021 11:17:56
-0600 (MDT)
Other header lines (DKIM-Filter, Authentication-Results:
DKIM-Signature:) and then
Received: by mta12.mc.ihg.com id hthska2fmd4d for
<emailaddrremo...@autoelect.com>; Mon, 12 Jul 2021 17:17:56 +0000
(envelope-from
<bounce-34_html-3203040-15955-514005572-29...@bounce.mc.ihg.com>)
----
The DKIM verify wouldn't have happened till after spamass-milter saw it,
but it looks like the first received line is simply lost and replaced
with the second received header which will never have a chance of
matching SPF. But as I don't routinely look at the debug output, I may
well be misinterpreting it. As far as I know the spamass-milter
configuration is very generic
OPTIONS="-u spamass-milter -i 127.0.0.1 -d spamc"
SOCKET="/var/spool/postfix/spamass/spamass.sock"
SOCKETOWNER="postfix:postfix"
SOCKETMODE="0660"
--
William Haller
Linux System Administrator
Our Glorious Logo
610 Platte Road
Casper, WY 82601
Office: (307) 234-9311
Direct: (307) 233-0336
www.autoelect.com <http://www.autoelect.com>
Safety - It's Our Way
