[aprssig] ***SPAM*** Re: ***SPAM*** Re: ***SPAM*** Re: ***SPAM*** Re: arrl.net domain e-mail sending failures? (***SPAM*** removed)

[MJ Inabnit]

Greetings,

I emailed ARRL about this issue 18jan2023 and received generic response:
"Your request has been received and is being reviewed by our support
team. We'll get back to you as soon as we can."

On 6feb2023 I requested an update.  No response from ARRL.

Today (13feb2023) I telephoned the league & spoke with Margie w1mrg.
Her response is she couldn't help non-league folks .. I pointed out I
have been a member for my entire amateur service.  Reluctantly, she
indicated I can forward complaint directly to her email and she would
forward it to their IT dept..  She refused to identify WHO is the IT dept :|

Margie's email:  circulation at arrl.org

I will again send an "email failure to gmail.com" message and include
our conversation from this list, additionally include all my bounce
notices as a text file.

I hope everyone else will follow suit in hopes we might nudge the league
to remedy this snafu.

I'll also alert my division & section managers.

73
Jaye ke6sls at ARRL.NET


On 1/30/23 8:45 AM, Lynn W Deffenbaugh (Mr) wrote:
> 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.
> 
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> 
> 
> -------- Forwarded Message --------
> Subject: 	Mail delivery failed: returning message to sender
> Date: 	Mon, 30 Jan 2023 17:38:51 +0100
> From: 	Mail Delivery System <mailer-daemon at perfora.net>
> To: 	KJ4ERJ at arrl.net
> 
> 
> 
> 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:
> 
> kn6oeg at gmail.com:
> 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
> ail
> 550-5.7.26 policy (-all) but it fails to pass SPF checks with the ip:
> 550-5.7.26 [74.208.4.194]. To best protect our users from spam and phishin
> g,
> 550-5.7.26 the message has been blocked. Please visit
> 550-5.7.26 https://support.google.com/mail/answer/81126#authentication fo
> r more
> 550 5.7.26 information. co12-20020a0566383e0c00b00371bd058965si6817973jab.
> 83 - gsmtp
> 
> 
> 
> On 1/18/2023 8:45 PM, MJ Inabnit wrote:
>> I forwarded these posts to hq at arrl.org 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:
>>> 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:
>>>> 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) <KJ4ERJ at arrl.net>
>>>> To: MJ Inabnit <ke6sls at arrl.net>; aprssig at lists.tapr.org
>>>> 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:
>>>>> 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:
>>>>>> This is slightly off-topic with respect to APRS, but since that's the
>>>>>> bulk of the e-mail that I send as KJ4ERJ at arrl.net, 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
>>>> this
>>>>>> 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.
>>>>>>
>>>>>> https://www.nslookup.io/domains/arrl.net/email/spf/
>>>>>>
>>>>>> 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:
>>>>>>
>>>>>>> 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:
>>>>>>>
>>>>>>>        qp2trz at gmail.com:
>>>>>>>            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
> 
> 


-- 

wishing you well
Jaye, ke6sls--via the toshiba w/thunderchicken