But if you’re sending to someone that is redirecting and the failure happens at the redirect that cannot be your problem… 


> On Jul 4, 2019, at 10:36 AM, gregrwm <tclug1 at whitleymott.net> wrote:
> 
> we wish.  but in the real world we need to deal with and interface with poor protocols and sorry software.  almost nobody specifies strict spf compliance.  this is probably why.  so i guess i also will back off to advisory only.  yes it is my problem when folks dont receive my emails.
> 
> 
> On Thu, Jul 4, 2019 at 9:29 AM Ryan Coleman <ryan.coleman at cwis.biz <mailto:ryan.coleman at cwis.biz>> wrote:
> Correct. Their problem, not yours. :) Just annoying. 
> 
> 
>> On Jul 4, 2019, at 2:44 AM, gregrwm <tclug1 at whitleymott.net <mailto:tclug1 at whitleymott.net>> wrote:
>> it's not mine.  note the similarity with the node that issued the notice.  i see now, it's the spf forwarding trap.  by specifying strict spf compliance, i break their forwarding of my messages.  hmm.
>> >$  host 192.185.48.84
>> >84.48.185.192.in-addr.arpa domain name pointer gateway23.websitewelcome.com <http://gateway23.websitewelcome.com/>.
>> 
>> 
>> On Wed, Jul 3, 2019 at 6:28 PM Ryan Coleman <ryan.coleman at notcwis.biz <mailto:ryan.coleman at notcwis.biz>> wrote:
>> Looks to me like your external IP (192.185.48.84) is not on the SPF1 list… 
>> 
>> Here’s mine for d3photography:
>>> v=spf1 a mx include:zoho.com <http://zoho.com/> include:spf.smtp2go.com <http://spf.smtp2go.com/> ~all
>> 
>> You’re definitely lacking you’re 192.185 IP in that include list.
>> 
>> https://whatismyipaddress.com/ip/192.185.48.84 <https://whatismyipaddress.com/ip/192.185.48.84>
>> Hostname:	gateway23.websitewelcome.com <http://gateway23.websitewelcome.com/>
>> 
>>>> Ryan
>> 
>> 
>>> On Jul 3, 2019, at 10:58 AM, gregrwm <tclug1 at whitleymott.net <mailto:tclug1 at whitleymott.net>> wrote:
>>> i received the two delivery failure notices copied below (portions suppressed with ...).  it's clear heidi's address in my messages must have forwarded to her address at landvantage.com <http://landvantage.com/>, and i expect the problem is in the mail handler there.  but i dont want to overlook the possibility the error might be mine.  the zone definition for whitleymott.net <http://whitleymott.net/> is also copied below.  if anyone can see what's amis please advise.  i'vs also written to postmaster at gateway33.websitewelcome.com <mailto:postmaster at gateway33.websitewelcome.com>.  i also welcome your suggestions on where better to post this question.
>>> 
>>> 
>>> >$TTL  4h ;ttl for all RRs lacking an explicit ttl
>>> >@ SOA @ hostmaster.scalliondata.com <http://hostmaster.scalliondata.com/>. (
>>> >     696 ;serial
>>> >      4h ;secondary server refresh
>>> >      1h ;secondary server refresh retry
>>> >      4d ;expire unrefreshed secondary server
>>> >      4h ;ttl for no-such-domain (NXDOMAIN) responses from us
>>> >)
>>> >@ NS ns
>>> >googleffffffffed11605c CNAME                  google.com <http://google.com/>.
>>> >mail                   CNAME              ghs.google.com <http://ghs.google.com/>.
>>> >webmail                CNAME              ghs.google.com <http://ghs.google.com/>.
>>> >mx                     CNAME          ASPMX.L.GOOGLE.COM <http://aspmx.l.google.com/>.
>>> >smtp                   CNAME          ASPMX.L.GOOGLE.COM <http://aspmx.l.google.com/>.
>>> >@ MX 10                               ASPMX.L.GOOGLE.COM <http://aspmx.l.google.com/>.
>>> >@ MX 20                          ALT1.ASPMX.L.GOOGLE.COM <http://alt1.aspmx.l.google.com/>.
>>> >@ MX 20                          ALT2.ASPMX.L.GOOGLE.COM <http://alt2.aspmx.l.google.com/>.
>>> >@ MX 30                               ASPMX2.GOOGLEMAIL.COM <http://aspmx2.googlemail.com/>.
>>> >@ MX 30                               ASPMX3.GOOGLEMAIL.COM <http://aspmx3.googlemail.com/>.
>>> >@ MX 30                               ASPMX4.GOOGLEMAIL.COM <http://aspmx4.googlemail.com/>.
>>> >@ MX 30                               ASPMX5.GOOGLEMAIL.COM <http://aspmx5.googlemail.com/>.
>>> >@ TXT "v=spf1 a a:rose.fo4.net <http://rose.fo4.net/> a:okra.fo4.net <http://okra.fo4.net/> include:aspmx.googlemail.com <http://aspmx.googlemail.com/> -all"
>>> >@   A 206.123.88.191
>>> >www A 206.123.88.191
>>> >ns0 A 206.123.88.191
>>> >ns  A 209.240.82.11
>>> 
>>> 
>>> On Tue, Jul 2, 2019 at 12:39 PM Mail Delivery System <MAILER-DAEMON at gateway23.websitewelcome.com <mailto:MAILER-DAEMON at gateway23.websitewelcome.com>> wrote:
>>> This is the mail system at host gateway23.websitewelcome.com <http://gateway23.websitewelcome.com/>.
>>> 
>>> I'm sorry to have to inform you that your message could not
>>> be delivered to one or more recipients. It's attached below.
>>> 
>>> For further assistance, please send mail to postmaster.
>>> 
>>> If you do so, please include this problem report. You can
>>> delete your own text from the attached returned message.
>>> 
>>>                    The mail system
>>> 
>>> <... at landvantage.com <http://landvantage.com/>>: host mx10.mailspamprotection.com <http://mx10.mailspamprotection.com/>[184.154.208.34] said:
>>>     550 192.185.48.84 is not allowed to send mail from whitleymott.net <http://whitleymott.net/>. Please
>>>     see the SPF record, with scope mfrom, identity greg at whitleymott.net <mailto:greg at whitleymott.net>, and ip
>>>     192.185.48.84 (in reply to end of DATA command)
>>> 
>>> ---------- Forwarded message ----------
>>> From: gregory mott <greg at whitleymott.net <mailto:greg at whitleymott.net>>
>>> To: 
>>> Cc: David ... <...>, heidi... at ...com
>>> Bcc: 
>>> Date: Tue, 2 Jul 2019 12:38:35 -0500
>>> ...
>>> 
>>> 
>>> On Tue, Jul 2, 2019 at 11:05 AM Mail Delivery System <MAILER-DAEMON at gateway33.websitewelcome.com <mailto:MAILER-DAEMON at gateway33.websitewelcome.com>> wrote:
>>> This is the mail system at host gateway33.websitewelcome.com <http://gateway33.websitewelcome.com/>.
>>> 
>>> I'm sorry to have to inform you that your message could not
>>> be delivered to one or more recipients. It's attached below.
>>> 
>>> For further assistance, please send mail to postmaster.
>>> 
>>> If you do so, please include this problem report. You can
>>> delete your own text from the attached returned message.
>>> 
>>>                    The mail system
>>> 
>>> <... at landvantage.com <http://landvantage.com/>>: host mx10.mailspamprotection.com <http://mx10.mailspamprotection.com/>[108.163.228.170]
>>>     said: 550 192.185.146.78 is not allowed to send mail from whitleymott.net <http://whitleymott.net/>.
>>>     Please see the SPF record, with scope mfrom, identity greg at whitleymott.net <mailto:greg at whitleymott.net>,
>>>     and ip 192.185.146.78 (in reply to end of DATA command)
>>> 
>>> ---------- Forwarded message ----------
>>> From: gregory mott <greg at whitleymott.net <mailto:greg at whitleymott.net>>
>>> To: Sarah ... <... at gmail.com <http://gmail.com/>>
>>> Cc: Laurel ...<... at gmail.com <http://gmail.com/>>, Kurt ... <... at gmail.com <http://gmail.com/>>, David ... <...>, heidi... at ...com
>>> Bcc: 
>>> Date: Tue, 2 Jul 2019 11:05:17 -0500
>>> ...
>> 
>> --
>> this concludes test 42 of big bang inflation dynamics.  in the advent of an actual universe, further instructions will be provided.  000000000000000000000042
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> tclug-list at mn-linux.org <mailto:tclug-list at mn-linux.org>
> http://mailman.mn-linux.org/mailman/listinfo/tclug-list <http://mailman.mn-linux.org/mailman/listinfo/tclug-list>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20190705/99997b58/attachment-0001.html>