<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-signature">The "clunky workaround" is up to the
owner of the domain, arrl.net in this case, to properly define a
DNS TXT record specifying where e-mails are expected to
originate. It's all part of the SPF or Sender Policy Framework
defined in RFC 7208 which apparently gmail is recently enforcing
and/or arrl.net recently defined to deny most originators.</div>
<div class="moz-signature"><br>
</div>
<div class="moz-signature">The ARRL can fix this by fixing the SPF
DNS TXT record to allow @arrl.net e-mails to originate anywhere.
They need to do this, or their e-mail aliasing is completely
useless. It is NOT gmail's problem.<br>
</div>
<div class="moz-signature"><br>
</div>
<div class="moz-signature">Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
<br>
<br>
<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 1/18/2023 6:15 PM, R Kirk via
aprssig wrote:<br>
</div>
<blockquote type="cite"
cite="mid:305568351.1859356.1674083757239@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="color:black;font: 10pt arial;">This seems to be a
fault of GMail, not AARL or others. My boat group has had the
same types of problems when GMail would arbitrarily reject valid
emails. There's some clunky workaround which should not be
neccessary.<br>
<br>
<br>
<div
style="font-family:arial,helvetica;font-size:10pt;color:black"><font
size="2">-----Original Message-----<br>
From: Lynn W Deffenbaugh (Mr) <a class="moz-txt-link-rfc2396E" href="mailto:KJ4ERJ@arrl.net"><KJ4ERJ@arrl.net></a><br>
To: MJ Inabnit <a class="moz-txt-link-rfc2396E" href="mailto:ke6sls@arrl.net"><ke6sls@arrl.net></a>;
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br>
Sent: Wed, Jan 18, 2023 5:52 pm<br>
Subject: [aprssig] ***SPAM*** Re: arrl.net domain e-mail
sending failures? (***SPAM*** removed)<br>
<br>
<div dir="ltr">If you have a non @arrl.net address, you can
likely send to gmail.com <br clear="none">
from there.<br clear="none">
<br clear="none">
Glad to know it's not just me! And yes, I'm hoping
someone here has a <br clear="none">
line on who to call at the ARRL.<br clear="none">
<br clear="none">
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile
and Win32<br clear="none">
<br clear="none">
PS. And your reply to my ***SPAM*** got marked as
***SPAM*** as well. <br clear="none">
This is going to get VERY old VERY quickly!<br
clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
<div class="yqt4885616358" id="yqtfd15188"><br
clear="none">
On 1/18/2023 4:28 PM, MJ Inabnit wrote:<br clear="none">
> I just got 5 in a row from gmail. I assumed some
kind of filter on the<br clear="none">
> jpg images I sent my friend who was shopping at
hardware store. So<br clear="none">
> finally I removed all images and that too bounced.
I am NOT savvy in<br clear="none">
> this arena and hope someone can contact ARRL.<br
clear="none">
><br clear="none">
> Tnx & 73<br clear="none">
> j<br clear="none">
><br clear="none">
> On 1/18/23 12:33 PM, Lynn W Deffenbaugh (Mr) wrote:<br
clear="none">
>> This is slightly off-topic with respect to
APRS, but since that's the<br clear="none">
>> bulk of the e-mail that I send as <a
shape="rect" ymailto="mailto:KJ4ERJ@arrl.net"
href="mailto:KJ4ERJ@arrl.net" moz-do-not-send="true"
class="moz-txt-link-freetext">KJ4ERJ@arrl.net</a>, I
thought I'd ask it<br clear="none">
>> here.<br clear="none">
>><br clear="none">
>> Has anyone recently noticed that e-mail sent
from the @arrl.net domain<br clear="none">
>> to an @gmail.com address bounces? This seems
to have started just this<br clear="none">
>> week for me. I've included the bounce text
below, and for anyone that<br clear="none">
>> understands SPF, here's a link to arrl.net's
SPF TXT record.<br clear="none">
>><br clear="none">
>> <a shape="rect"
href="https://www.nslookup.io/domains/arrl.net/email/spf/"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.nslookup.io/domains/arrl.net/email/spf/</a><br
clear="none">
>><br clear="none">
>> It would seem that we have to send our
@arrl.net e-mails out through<br clear="none">
>> pobox.com in order to pass gmail's enforcement
of the SPF.<br clear="none">
>><br clear="none">
>> I don't know if it would fix the gmail issue,
but does anyone know who<br clear="none">
>> to contact at the ARRL to try changing the
final -all (fail) to a ~all<br clear="none">
>> (softfail) or ?all (neutral)?<br clear="none">
>><br clear="none">
>> Lynn (D) - KJ4ERJ - Author of APRSISCE for
Windows Mobile and Win32<br clear="none">
>><br clear="none">
>> PS. Here's the Mail delivery failed that I'm
getting from gmail:<br clear="none">
>><br clear="none">
>>> This message was created automatically by
mail delivery software.<br clear="none">
>>><br clear="none">
>>> A message that you sent could not be
delivered to one or more of<br clear="none">
>>> its recipients. This is a permanent error.<br
clear="none">
>>><br clear="none">
>>> The following address failed:<br
clear="none">
>>><br clear="none">
>>> <a shape="rect"
ymailto="mailto:qp2trz@gmail.com"
href="mailto:qp2trz@gmail.com" moz-do-not-send="true"
class="moz-txt-link-freetext">qp2trz@gmail.com</a>:<br
clear="none">
>>> SMTP error from remote server for
TEXT command, host:<br clear="none">
>>> gmail-smtp-in.l.google.com (64.233.191.26)
reason: 550-5.7.26 The MAIL<br clear="none">
>>> FROM domain [arrl.net] has an SPF record
with a hard fail<br clear="none">
>>> 550-5.7.26 policy (-all) but it fails to
pass SPF checks with the ip:<br clear="none">
>>> 550-5.7.26 [74.208.4.197]. To best protect
our users from spam and<br clear="none">
>>> phishing,<br clear="none">
>>> 550-5.7.26 the message has been blocked.
Please visit<br clear="none">
>>>
550-5.7.26https://support.google.com/mail/answer/81126#authentication<br
clear="none">
>>> for more<br clear="none">
>>> 550 5.7.26 information.<br clear="none">
>>>
x11-20020a02ac8b000000b00389e24ff4cesi30253548jan.<br
clear="none">
>>> 129 - gsmtp<br clear="none">
>><br clear="none">
>> _______________________________________________<br
clear="none">
>> aprssig mailing list<br clear="none">
>> <a shape="rect"
ymailto="mailto:aprssig@lists.tapr.org"
href="mailto:aprssig@lists.tapr.org"
moz-do-not-send="true" class="moz-txt-link-freetext">aprssig@lists.tapr.org</a><br
clear="none">
>> <a shape="rect"
href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br
clear="none">
><br clear="none">
<br clear="none">
<br clear="none">
_______________________________________________<br
clear="none">
aprssig mailing list<br clear="none">
<a shape="rect" ymailto="mailto:aprssig@lists.tapr.org"
href="mailto:aprssig@lists.tapr.org"
moz-do-not-send="true" class="moz-txt-link-freetext">aprssig@lists.tapr.org</a><br
clear="none">
<a shape="rect"
href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br
clear="none">
</div>
</div>
</font></div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>