<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-signature">Looks like it is still failing for me.
This is from about 5 minutes ago sending from my @arrl.net address
to an @gmail.com address via my ISP's SMTP server.<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>
-------- Forwarded Message --------
<table class="moz-email-headers-table" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
</th>
<td>Mail delivery failed: returning message to sender</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
<td>Mon, 30 Jan 2023 17:38:51 +0100</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
<td>Mail Delivery System <a class="moz-txt-link-rfc2396E"
href="mailto:mailer-daemon@perfora.net"><mailer-daemon@perfora.net></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
<td><a class="moz-txt-link-abbreviated
moz-txt-link-freetext" href="mailto:KJ4ERJ@arrl.net">KJ4ERJ@arrl.net</a></td>
</tr>
</tbody>
</table>
<br>
<br>
This message was created automatically by mail delivery software.<br>
<br>
A message that you sent could not be delivered to one or more of<br>
its recipients. This is a permanent error.<br>
<br>
The following address failed:<br>
<br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:kn6oeg@gmail.com">kn6oeg@gmail.com</a>:<br>
SMTP error from remote server for TEXT command, host:
gmail-smtp-in.l.google.com (64.233.191.26) reason: 550-5.7.26 The
MAIL FROM domain [arrl.net] has an SPF record with a hard f<br>
ail<br>
550-5.7.26 policy (-all) but it fails to pass SPF checks with the
ip:<br>
550-5.7.26 [74.208.4.194]. To best protect our users from spam and
phishin<br>
g,<br>
550-5.7.26 the message has been blocked. Please visit<br>
550-5.7.26 <a class="moz-txt-link-freetext"
href="https://support.google.com/mail/answer/81126#authentication">https://support.google.com/mail/answer/81126#authentication</a>
fo<br>
r more<br>
550 5.7.26 information.
co12-20020a0566383e0c00b00371bd058965si6817973jab.<br>
83 - gsmtp<br>
</div>
<div class="moz-cite-prefix"><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 8:45 PM, MJ Inabnit wrote:<br>
</div>
<blockquote type="cite"
cite="mid:99f5db7d-729c-bda4-2710-01be6ecf4175@arrl.net">
<pre class="moz-quote-pre" wrap="">
I forwarded these posts to <a class="moz-txt-link-abbreviated" href="mailto:hq@arrl.org">hq@arrl.org</a> and just received two support
ticket confirmations. Hopefully they will be able to correct this asap.
Tnx & 73
j
On 1/18/23 5:14 PM, Lynn W Deffenbaugh (Mr) wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">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.
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.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 1/18/2023 6:15 PM, R Kirk via aprssig wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">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.
-----Original Message-----
From: Lynn W Deffenbaugh (Mr) <a class="moz-txt-link-rfc2396E" href="mailto:KJ4ERJ@arrl.net"><KJ4ERJ@arrl.net></a>
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>
Sent: Wed, Jan 18, 2023 5:52 pm
Subject: [aprssig] ***SPAM*** Re: arrl.net domain e-mail sending
failures? (***SPAM*** removed)
If you have a non @arrl.net address, you can likely send to gmail.com
from there.
Glad to know it's not just me! And yes, I'm hoping someone here has a
line on who to call at the ARRL.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
PS. And your reply to my ***SPAM*** got marked as ***SPAM*** as well.
This is going to get VERY old VERY quickly!
On 1/18/2023 4:28 PM, MJ Inabnit wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I just got 5 in a row from gmail. I assumed some kind of filter on the
jpg images I sent my friend who was shopping at hardware store. So
finally I removed all images and that too bounced. I am NOT savvy in
this arena and hope someone can contact ARRL.
Tnx & 73
j
On 1/18/23 12:33 PM, Lynn W Deffenbaugh (Mr) wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">This is slightly off-topic with respect to APRS, but since that's the
bulk of the e-mail that I send as <a class="moz-txt-link-abbreviated" href="mailto:KJ4ERJ@arrl.net">KJ4ERJ@arrl.net</a>, I thought I'd ask it
here.
Has anyone recently noticed that e-mail sent from the @arrl.net domain
to an @gmail.com address bounces? This seems to have started just
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">this
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">week for me. I've included the bounce text below, and for anyone that
understands SPF, here's a link to arrl.net's SPF TXT record.
<a class="moz-txt-link-freetext" href="https://www.nslookup.io/domains/arrl.net/email/spf/">https://www.nslookup.io/domains/arrl.net/email/spf/</a>
It would seem that we have to send our @arrl.net e-mails out through
pobox.com in order to pass gmail's enforcement of the SPF.
I don't know if it would fix the gmail issue, but does anyone know who
to contact at the ARRL to try changing the final -all (fail) to a ~all
(softfail) or ?all (neutral)?
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
PS. Here's the Mail delivery failed that I'm getting from gmail:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error.
The following address failed:
<a class="moz-txt-link-abbreviated" href="mailto:qp2trz@gmail.com">qp2trz@gmail.com</a>:
SMTP error from remote server for TEXT command, host:
gmail-smtp-in.l.google.com (64.233.191.26) reason: 550-5.7.26 The MAIL
FROM domain [arrl.net] has an SPF record with a hard fail
550-5.7.26 policy (-all) but it fails to pass SPF checks with the ip:
550-5.7.26 [74.208.4.197]. To best protect our users from spam and
phishing,
550-5.7.26 the message has been blocked. Please visit
550-5.7.26https://support.google.com/mail/answer/81126#authentication
for more
550 5.7.26 information.
x11-20020a02ac8b000000b00389e24ff4cesi30253548jan.
129 - gsmtp
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>