Re: [spfbis] Question regarding RFC 7208

[Hector Santos <[e-mail]>]

+1 on suggestion.

myfloorschedule.com <http://myfloorschedule.com/> has a DMARC p=none record.   Using DMARC presumes there are two things expected in the transaction;  SPF and DKIM with aligned domains.  But the p=none policy suggest no rejection/quarantine is desired if errors are detected.

However, Local policy probably has other things going on related to DMARC/SPF.

Start with the SPF setup suggestion and also make sure there is a DKIM-signature the signer d=myfloorschedule.com <http://myfloorschedule.com/>


—
HLS

> On May 7, 2023, at 4:34 PM, Mark Alley <mark.alley=[e-mail]> wrote:
> 
> It appears myfloorschedule.com <http://myfloorschedule.com/> doesn't have an SPF record. This particular recipients mail filter might have a strict local policy about domains with no SPF record.
> 
> If you add an SPF record to "myfloorschedule.com <http://myfloorschedule.com/>" that looks something like the below, does that fix the problem? 
> 
> myfloorschedule.com <http://myfloorschedule.com/> IN TXT "v=spf1 include:spf.smtp2go.com <http://spf.smtp2go.com/> ?all"
> 
> Use the neutral ?all qualifier just to test so it doesn't change the behavior for other mail streams on the domain.
> 
> -Mark Alley
> 
> 
> On Sun, May 7, 2023, 2:50 PM Terence at CRS <[e-mail] <mailto:[e-mail]>> wrote:
>> 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 <http://ioa.com/> and gate.net <http://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:
>> 
>>   [e-mail] <mailto:[e-mail]>
>>     host mx02.earthlink-vadesecure.net <http://mx02.earthlink-vadesecure.net/> [51.81.61.71]
>> 
>>     Remote host closed connection in response to HELO mail1.exim.smtpcorp.com <http://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 <http://smtpcorp.com/> with esmtpsa (TLS1.0:ECDHE_SECP256R1__RSA_SHA1__AES_256_CBC__SHA1:256)
>> 
>>               (Exim 4.96-S2G)
>> 
>>               (envelope-from [e-mail] <mailto:[e-mail]>)
>> 
>>               id 1pu7Qr-rlnJZO-2W
>> 
>>               for [e-mail] <mailto:[e-mail]>;
>> 
>>               Wed, 03 May 2023 08:01:49 +0000
>> 
>> MIME-Version: 1.0
>> 
>> From: "Shift Reminder" [e-mail] <mailto:[e-mail]>
>> To: [e-mail] <mailto:[e-mail]>
>> Reply-To: [e-mail] <mailto:[e-mail]>
>> 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: [e-mail] <mailto:[e-mail]>_______________________________________________
>> spfbis mailing list
>> [e-mail] <mailto:[e-mail]>
>> https://www.ietf.org/mailman/listinfo/spfbis
> _______________________________________________
> spfbis mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/spfbis