[aprssig] aprssig Digest, Vol 212, Issue 21 (List email problems)

Randy Hall aa6rh at socorad.io
Fri Feb 18 14:10:46 EST 2022


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.

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 lists.tapr.org

This is just the "hidden cost" of running your own mail server at work
right here. You pay for it one way or another.

*Randy AA6RH*
*aa6rh at socorad.io <aa6rh at socorad.io>*
*Grid Square: CM88pl*

*QRZ Profile <https://www.qrz.com/db/aa6rh>*
*Sonoma County DMR: BrandMeister 31707

On Fri, Feb 18, 2022 at 10:56 AM Charles Gallo <charlie at thegallos.com>

> Usually, it is when someone else on the server is a spammer,  so hey block
> the whole server
> --
> 73 de KG2V
> Charlie
> > On Feb 18, 2022, at 1:24 PM, John Ackermann N8UR <jra at febo.com> wrote:
> >
> > On 2/18/22 12:00 PM, aprssig-request at lists.tapr.org wrote:
> >
> > The issue we're dealing with has been affecting folks on the other
> lists.tapr.org lists; I don't know how many people on aprssig are
> affected by it.
> >
> > People who have Microsoft as their email service provider are being
> blocked from getting messages from lists.tapr.org.  The bounce messages
> say:
> >
> > "Access denied, banned sender[]. To request removal from
> this list please forward this message to delist at messaging.microsoft.com.
> For more information please go to
> http://go.microsoft.com/fwlink/?LinkId=526653. AS(1410) [
> SY4AUS01FT004.eop-AUS01.prod.protection.outlook.com]"
> >
> > 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.
> >
> > 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, lists.tapr.org 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.
> >
> > 73,
> > John
> >
> >> ------------------------------
> >> Message: 8
> >> Date: Thu, 17 Feb 2022 20:37:02 -0500
> >> From: Steve Dimse <steve at dimse.com>
> >> To: TAPR APRS Sig <aprssig at lists.tapr.org>
> >> Subject: Re: [aprssig] TAPR Mailing List Update
> >> Message-ID: <CA5ACD1C-DEA0-4505-9FC4-249B5001895E at dimse.com>
> >> Content-Type: text/plain;    charset=us-ascii
> >> 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.
> >> Steve
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at lists.tapr.org
> > http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20220218/fe7ff0cf/attachment.html>

More information about the aprssig mailing list