[aprssig] arrl.net domain e-mail sending failures?

[Nick VA3NNW]

Thus spake Lynn (D) - KJ4ERJ:

> 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)?
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.

I'm now seeing:

arrl.org. TXT "v=spf1 mx a ip4:104.207.196.0/27 ip4:192.254.121.248 
ip4:23.21.109.197 ip4:23.21.109.212 ip4:216.33.126.11 
include:spf.protection.outlook.com include:_phishspf.knowbe4.com ~all"

I believe the final "~all" is acceptable?

The zone SOA has a serial of 2023011804, which may or may not mean 
2023-01-18, 04th version of the zone that day (this is a common format 
for serials, but definitely NOT a hard standard)

Note that knowbe4 are a fairly famous IT security consultancy / training 
company (I think Kevin Mitnick ended up there), so _phishspf.knowbe4.com 
is probably being contracted to perform phishing tests for them. They 
may have (incorrectly/misleadingly?) instructed them how to set their 
SPF appropriately?

Unfortunately if enough gmail people "report as spam" on those phising 
tests, it may or not matter what their SPF says, arrl.org may get a 
reputation as a spam domain     :-/

Compare the similar domain of Canadian ve/vaNxxx at rac.ca aliases:

rac.ca. TXT "v=spf1 +a +mx +ip4:51.222.44.74 +ip4:51.79.20.155 
+include:servers.mcsv.net ~all"

... again "~all"?

Nick VA3NNW

-- 
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209, IRLP #2410 on VE3RBM
use Std::Disclaimer;    sig at noseynick.net
Do Passwords PROPERLY! ... see https://noseynick.net/vault.html
We are born naked, wet and hungry. Then things get worse.