<html><head></head><body><div class="ydp1371dde5yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">One additional note (from my own experience with email issues at a major cloud service provider) is that the "-all" directive in the SPF record must be last. The tokens in the SPF records are evaluated in order from left to right (with recursion at the point where an "include:" is found), and stop being evaluated when a match occurs. Since "all" matches everything, mail servers implementing SPF checks would never proceed to the "include:" directive that provides recursion to another list.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Re: adding lists.tapr.org to the list: that should be a "ip:lists.tapr.org", not an "mx:", because "mx:" means to check the mail exchangers records for the specified domain name rather than the IP address records.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Andrew Pavlin, KA2DDO<br></div><div><br></div>
</div><div id="ydp6ab0dc27yahoo_quoted_5586782412" class="ydp6ab0dc27yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, February 18, 2022, 05:22:13 PM EST, Bob Poortinga <aprssig@k9sql.us> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp6ab0dc27yiv7291800408"><div><div>I believe that I have found an issue that may be causing, or at least contributing, to the rejected email problem.<div><br clear="none"></div><div>The Sender Policy Framework (SPF) DNS TXT record for <a shape="rect" href="http://TAPR.ORG" rel="nofollow" target="_blank">TAPR.ORG</a> does not contain a reference to the IP address or hostname of '<a shape="rect" href="http://lists.tapr.org" rel="nofollow" target="_blank">lists.tapr.org</a> [173.230.155.76]".</div><div><br clear="none"></div><div>Here is the record:</div><div><br clear="none"></div><div>"v=spf1 a mx -all include:_<a shape="rect" href="http://spf.z2systems.com" rel="nofollow" target="_blank">spf.z2systems.com</a>"</div><div><br clear="none"></div><div>Let me break this down.</div><div>"v=spf1" is the SPF identifier and version number.</div><div>"a" means accept email from the IP address of the A record for <a shape="rect" href="http://TAPR.ORG" rel="nofollow" target="_blank">TAPR.ORG</a> (which is 35.196.172.173.)</div><div>"mx" means accept email from the host listed as the MX (mail exchanger) for <a shape="rect" href="http://TAPR.ORG" rel="nofollow" target="_blank">TAPR.ORG</a> (which is "<a shape="rect" href="http://mail.tapr.org" rel="nofollow" target="_blank">mail.tapr.org</a> [45.79.201.63],</div><div>"-all" (and this is important) means reject email with a sender address of <a shape="rect" href="http://TAPR.ORG" rel="nofollow" target="_blank">TAPR.ORG</a> from any other hostname or IP address,</div><div>"include:_<a shape="rect" href="http://spf.z2systems.com" rel="nofollow" target="_blank">spf.z2systems.com</a>" means lookup and include the SPF policies of "_<a shape="rect" href="http://spf.z2systems.com" rel="nofollow" target="_blank">spf.z2systems.com</a>." I have examined that record and it does not include "<a shape="rect" href="http://lists.tar.org" rel="nofollow" target="_blank">lists.tar.org</a>" or it's IP address.</div><div><br clear="none"></div><div>There are several approaches to fixing this SPF record. Here is my recommendation: add "mx:<a shape="rect" href="http://lists.tapr.org" rel="nofollow" target="_blank">lists.tapr.org</a>" to the <a shape="rect" href="http://TAPR.ORG" rel="nofollow" target="_blank">TAPR.ORG</a> SPF DNS TXT record. You could instead add "ip4:173.230.155.76" to the SPF record as well, but that would have to be updated everytime the IP address of '<a shape="rect" href="http://lists.tapr.org" rel="nofollow" target="_blank">lists.tapr.org</a>' changes. I would also change the hard reject in the SPF record from "-all" to a soft reject "~all". Additionally, the "all" specifier should be the last item listed in the SPF record and any "include" policies ahould precede it.</div><div><br clear="none"></div><div>Before I retired, I ran the email systems for a large corporation and have had to deal with these types of issues many times in the past. I won't guarantee that this will fix all the problems, but it is something that needs be corrected in order for email to flow smoothly.</div><div><br clear="none"></div><div>73,</div><div>Bob W9IZ</div><div><br clear="none"></div></div><br clear="none"><div class="ydp6ab0dc27yiv7291800408gmail_quote"><div id="ydp6ab0dc27yiv7291800408yqtfd92867" class="ydp6ab0dc27yiv7291800408yqt2913028843"><div dir="ltr" class="ydp6ab0dc27yiv7291800408gmail_attr">On Fri, Feb 18, 2022, 2:11 PM Randy Hall <<a shape="rect" href="mailto:aa6rh@socorad.io" rel="nofollow" target="_blank">aa6rh@socorad.io</a>> wrote:<br clear="none"></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;" class="ydp6ab0dc27yiv7291800408gmail_quote"><div dir="ltr"><a shape="rect" href="https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3alists.tapr.org&run=toolpage" rel="nofollow" target="_blank">https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3alists.tapr.org&run=toolpage</a><div><br clear="none"></div><div>Turns out, TAPR's maillist server is blacklisted. That is the thing that needs to be addressed first and foremost. Complaining to a mail receiver that they should disregard a blacklist is not going to get anything done.</div><div><br clear="none"></div><div>The fact that TAPR is hosting their own mail server on Linode is part of the problem. TAPR needs to have a person (staff or volunteer) who knows SMTP, sendmail and MX blacklist policies like the back of their hand, so that they can quickly address blacklist problems. Until and unless TAPR gets off the blacklist that the IP address is listed on, Microsoft is within their rights to disregard mail coming from <a shape="rect" href="http://lists.tapr.org" rel="nofollow" target="_blank">lists.tapr.org</a></div><div><br clear="none"></div><div>This is just the "hidden cost" of running your own mail server at work right here. You pay for it one way or another.</div><div><br clear="none"></div><div>--R<br clear="all"><div><div dir="ltr"><div dir="ltr"><div><i>--</i></div><i><b>Randy AA6RH</b></i><div><i><a shape="rect" href="mailto:aa6rh@socorad.io" rel="nofollow" target="_blank">aa6rh@socorad.io</a></i></div><div><i>Grid Square: CM88pl</i></div><div><i><a shape="rect" href="https://www.qrz.com/db/aa6rh" rel="nofollow" target="_blank">QRZ Profile</a><br clear="none"></i></div><div><i>Sonoma County DMR: <a shape="rect" href="https://brandmeister.network/?page=lh&jsonquery=%7B%22condition%22%3A%22AND%22%2C%22rules%22%3A%5B%7B%22id%22%3A%22DestinationID%22%2C%22field%22%3A%22DestinationID%22%2C%22type%22%3A%22integer%22%2C%22input%22%3A%22text%22%2C%22operator%22%3A%22equal%22%2C%22value%22%3A%2231707%22%7D%5D%7D" rel="nofollow" target="_blank">BrandMeister 31707</a></i></div></div></div></div><br clear="none"></div></div><br clear="none"><div class="ydp6ab0dc27yiv7291800408gmail_quote"><div dir="ltr" class="ydp6ab0dc27yiv7291800408gmail_attr">On Fri, Feb 18, 2022 at 10:56 AM Charles Gallo <<a shape="rect" href="mailto:charlie@thegallos.com" rel="nofollow" target="_blank">charlie@thegallos.com</a>> wrote:<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;" class="ydp6ab0dc27yiv7291800408gmail_quote">Usually, it is when someone else on the server is a spammer, so hey block the whole server<br clear="none">
<br clear="none">
-- <br clear="none">
73 de KG2V<br clear="none">
Charlie<br clear="none">
<br clear="none">
> On Feb 18, 2022, at 1:24 PM, John Ackermann N8UR <<a shape="rect" href="mailto:jra@febo.com" rel="nofollow" target="_blank">jra@febo.com</a>> wrote:<br clear="none">
> <br clear="none">
> On 2/18/22 12:00 PM, <a shape="rect" href="mailto:aprssig-request@lists.tapr.org" rel="nofollow" target="_blank">aprssig-request@lists.tapr.org</a> wrote:<br clear="none">
> <br clear="none">
> The issue we're dealing with has been affecting folks on the other <a shape="rect" href="http://lists.tapr.org" rel="nofollow" target="_blank">lists.tapr.org</a> lists; I don't know how many people on aprssig are affected by it.<br clear="none">
> <br clear="none">
> People who have Microsoft as their email service provider are being blocked from getting messages from <a shape="rect" href="http://lists.tapr.org" rel="nofollow" target="_blank">lists.tapr.org</a>. The bounce messages say:<br clear="none">
> <br clear="none">
> "Access denied, banned sender[173.230.155.76]. To request removal from this list please forward this message to <a shape="rect" href="mailto:delist@messaging.microsoft.com" rel="nofollow" target="_blank">delist@messaging.microsoft.com</a>. For more information please go to <a shape="rect" href="http://go.microsoft.com/fwlink/?LinkId=526653" rel="nofollow" target="_blank">http://go.microsoft.com/fwlink/?LinkId=526653</a>. AS(1410) [<a shape="rect" href="http://SY4AUS01FT004.eop-AUS01.prod.protection.outlook.com" rel="nofollow" target="_blank">SY4AUS01FT004.eop-AUS01.prod.protection.outlook.com</a>]"<br clear="none">
> <br clear="none">
> We have submitted several requests for delisting, and our ISP has been doing everything they can (we are not the only one of their customers having this problem), but so far nothing has gotten MSFT to unblock us. Changing IP addresses is one way to circumvent the problem.<br clear="none">
> <br clear="none">
> There may be other issues going on, but at the moment this is the one we can identify and hopefully do something about. Just for additional information, <a shape="rect" href="http://lists.tapr.org" rel="nofollow" target="_blank">lists.tapr.org</a> has been running on the same Mailman software and configuration since May, 2018. So there've been no recent changes at our end that could result in delivery issues, but there are plenty of things outside our control that can cause problems.<br clear="none">
> <br clear="none">
> 73,<br clear="none">
> John<br clear="none">
> <br clear="none">
>> ------------------------------<br clear="none">
>> Message: 8<br clear="none">
>> Date: Thu, 17 Feb 2022 20:37:02 -0500<br clear="none">
>> From: Steve Dimse <<a shape="rect" href="mailto:steve@dimse.com" rel="nofollow" target="_blank">steve@dimse.com</a>><br clear="none">
>> To: TAPR APRS Sig <<a shape="rect" href="mailto:aprssig@lists.tapr.org" rel="nofollow" target="_blank">aprssig@lists.tapr.org</a>><br clear="none">
>> Subject: Re: [aprssig] TAPR Mailing List Update<br clear="none">
>> Message-ID: <<a shape="rect" href="mailto:CA5ACD1C-DEA0-4505-9FC4-249B5001895E@dimse.com" rel="nofollow" target="_blank">CA5ACD1C-DEA0-4505-9FC4-249B5001895E@dimse.com</a>><br clear="none">
>> Content-Type: text/plain; charset=us-ascii<br clear="none">
>> I'm not sure how Microsoft is the issue. First, most of the posts are getting through to everyone, AFAIK. Lynn for example seems to see everyone but me. I seem to see everyone but Jeff. And we can email each other directly. It is just list messages from certain people to others that get lost.<br clear="none">
>> Steve<br clear="none">
> <br clear="none">
> _______________________________________________<br clear="none">
> aprssig mailing list<br clear="none">
> <a shape="rect" href="mailto:aprssig@lists.tapr.org" rel="nofollow" target="_blank">aprssig@lists.tapr.org</a><br clear="none">
> <a shape="rect" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="nofollow" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br clear="none">
<br clear="none">
<br clear="none">
_______________________________________________<br clear="none">
aprssig mailing list<br clear="none">
<a shape="rect" href="mailto:aprssig@lists.tapr.org" rel="nofollow" target="_blank">aprssig@lists.tapr.org</a><br clear="none">
<a shape="rect" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="nofollow" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br clear="none">
</blockquote></div>
_______________________________________________<br clear="none">
aprssig mailing list<br clear="none">
<a shape="rect" href="mailto:aprssig@lists.tapr.org" rel="nofollow" target="_blank">aprssig@lists.tapr.org</a><br clear="none">
<a shape="rect" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="nofollow" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br clear="none">
</blockquote></div></div><div id="ydp6ab0dc27yiv7291800408yqtfd27693" class="ydp6ab0dc27yiv7291800408yqt2913028843">
</div></div></div><div class="ydp6ab0dc27yqt2913028843" id="ydp6ab0dc27yqtfd12557">_______________________________________________<br clear="none">aprssig mailing list<br clear="none"><a shape="rect" href="mailto:aprssig@lists.tapr.org" rel="nofollow" target="_blank">aprssig@lists.tapr.org</a><br clear="none"><a shape="rect" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="nofollow" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br clear="none"></div></div>
</div>
</div></body></html>