[spfbis] Question regarding RFC 7208

Terence at CRS <TerenceW@crswebsite.com> Wed, 03 May 2023 11:21 UTC

X-Hostcollective-MailScanner-eFa-Information: Please contact postmaster@internetmailserver.net for more information
Received: from SMG03.dotnetplayground.com (SMG03 [192.168.120.13]) (no client certificate requested) by sc01.internetmailserver.net (MailScanner Milter) with SMTP id 4QBDzK3ZtczH3Xwn; Wed, 3 May 2023 04:21:17 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sc01.internetmailserver.net 4QBDzK3ZtczH3Xwn
Received: from SM14.internetmailserver.net (UnknownHost [192.168.120.34]) by SMG03.dotnetplayground.com with SMTP; Wed, 3 May 2023 04:21:09 -0700
X-SmarterMail-Authenticated-As: twehle@crswebsite.com
DKIM-Signature: v=1; a=rsa-sha256; d=crswebsite.com; s=8DAF25EDD73109C; c=simple/simple; t=1683112869; h=reply-to:from:to:subject:date:organization:message-id:mime-version: x-mailer:thread-index; bh=2MtUXSzosmOdLWtNXjxeQzXPfKkHQWTDDGDyOaBR1yQ=; b=fe9+5bcE0Rjl83zOTj7UrwKBBHPnFm4/HaHJECa/0O6vsPkKYcLCk88jmUdiNXuJUZaOfatIVPl SxXLGjSflTs86NG8DzorAuAuWzvWbaXFzpV9aJhRCad746/RmIYnv5YVIIupnMJ9s4kSrlTX/m7KW yqqC/pceSvlhXyglo3MODfmlcxS2RHL5qYFYrS2YB/0+1am3AQsOnxXsteZi14kmvOJAHMqW6lDdd bEeBpK6qRtMDwEJGACtGflTJhjeqfl6bgjkQ4ocUpmLXqB89gW4x+aqFlL9Ezv0leMSNskETZjk0u KVLjrJypPUeDQrioj0NODCgM6sSE5RSGGvcA==
Received: from MyLenovo (ip68-0-44-155.hr.hr.cox.net [68.0.44.155]) by SM14.internetmailserver.net with SMTP (version=Tls12 cipher=Aes256 bits=256); Wed, 3 May 2023 04:20:48 -0700
Reply-To: TerenceW@crswebsite.com
From: Terence at CRS <TerenceW@crswebsite.com>
To: spfbis@ietf.org
Date: Wed, 03 May 2023 07:20:49 -0400
Organization: CRS
Message-ID: <020d01d97db1$50de7560$f29b6020$@crswebsite.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_020E_01D97D8F.C9CFE2A0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: Adl9r6yiwh5pQx9vTZyo93Kombe3YQ==
Content-Language: en-us
X-Exim-Id: 020d01d97db1$50de7560$f29b6020$
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/89t7iq6U2I7QcYDT3tix_kS5_Zg>
X-Mailman-Approved-At: Sun, 07 May 2023 12:50:34 -0700
Subject: [spfbis] Question regarding RFC 7208
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spfbis/>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 May 2023 15:28:50 -0000

Good morning.

 

We use a service to send out emails for our customers.

The From email is from the sending server, so there should be no SPF error.
If you reply to the email you are sent to the customer email.

Most email servers allow this, but a few do not including ioa.com and
gate.net which will not deliver the email.

If you'll review the header you'll see that the From address matches the
envelope address.

Why would we then get this rule triggered and the email not delivered?

Thank you.

Terence Wehle

888-448-4049

www.floorscheduleweb.com <http://www.floorscheduleweb.com> 

 

rule:

Email on the Internet can be forged in a number of ways. In particular,
existing protocols place no restriction on what a sending host can use as
the "MAIL FROM" of a message or the domain given on the SMTP HELO/EHLO
commands. This document describes version 1 of the Sender Policy Framework
(SPF) protocol, whereby ADministrative Management Domains (ADMDs) can
explicitly authorize the hosts that are allowed to use their domain names,
and a receiving host can check such authorization.

 

return error:

  johnes@ioa.com <mailto:johnes@ioa.com> 

    host mx02.earthlink-vadesecure.net [51.81.61.71]

    Remote host closed connection in response to HELO
mail1.exim.smtpcorp.com (EHLO response was:

    550 5.7.1 HELO command rejected - ELNK001_203 -
https://postmaster-earthlink.vadesecure.com/inbound_error_codes/#_203):

    retry timeout exceeded

 

Email Header:

Received: from [10.96.31.33] (helo=ss16-010)

              by smtpcorp.com with esmtpsa
(TLS1.0:ECDHE_SECP256R1__RSA_SHA1__AES_256_CBC__SHA1:256)

              (Exim 4.96-S2G)

              (envelope-from shift-reminder@myfloorschedule.com
<mailto:shift-reminder@myfloorschedule.com> )

              id 1pu7Qr-rlnJZO-2W

              for johnes@ioa.com <mailto:johnes@ioa.com> ;

              Wed, 03 May 2023 08:01:49 +0000

MIME-Version: 1.0

From: "Shift Reminder" shift-reminder@myfloorschedule.com
<mailto:shift-reminder@myfloorschedule.com> 

To: johnes@ioa.com <mailto:johnes@ioa.com> 

Reply-To: glennc@c21mountainlifestyles.com
<mailto:glennc@c21mountainlifestyles.com> 

Date: 3 May 2023 01:01:49 -0700

Subject: Floor Duty Reminder

Content-Type: multipart/alternative;

boundary=--boundary_50571_e0bcab2a-d13a-475b-b2a1-026ba9f1199c

Message-Id: E1pu7Qr-rlnJZO-2W@message-id.smtpcorp.com
<mailto:E1pu7Qr-rlnJZO-2W@message-id.smtpcorp.com>

[spfbis] Question regarding RFC 7208 Terence at CRS
Re: [spfbis] Question regarding RFC 7208 Mark Alley
Re: [spfbis] Question regarding RFC 7208 Hector Santos