Date: Thu, 2 Jan 2020 14:03:58 -0700
Reply-To: "Michael A. Radtke" <wa7zpu@5BY9.NET>
Sender: Vanagon Mailing List <vanagon@gerry.vanagon.com>
From: "Michael A. Radtke" <wa7zpu@5BY9.NET>
Subject: Re: Missing Posts
In-Reply-To: <741C2ABE-4E61-4462-B48F-66C696154C05@klatsch.org>
Content-Type: text/plain; charset=UTF-8
Eric, Ryan, and Ben,
Thank you for your comments.
I think that Ben summarized the situation quite well, but I am certain
that some email providers do reject incoming email because of missing MX
records. It is part of their spam test.
Another thing is that the gerry.vanagon.com server logs will not show
messages discarded by list recipients providers, only mail bounced by
those providers. However, if just one list recipient bounces the
defective message, the fix may resolve the problem for all those
recipients who's provider discarded the message.
I agree that the admin for the gerry.vanagon.com server has to own this
problem. But, we can help too. Perhaps some list members who end up
with messages in their spam folder can drill down and see why.
Thanks,
Mike
------------------------ Original Message ------------------------
Date: Thu, 2 Jan 2020 14:28:01 -0600
From: Ben Eisenbraun <bene@KLATSCH.ORG>
To: vanagon@GERRY.VANAGON.COM
Subject: Re: Missing Posts
The MX record is not a requirement for mail delivery. RFC compliant
mailers will fallback to the A record. Since the non-delivery issues
seem to be intermittent for most people, I don’t think the missing MX
record is really the root problem.
The DNS configuration for gerry.vanagon.com is definitely not up to
modern standards (no SPF/DKIM as you note), but the server is also
running Listserv 1.8d, which came out in 1999, so it’s just one of many
things that are not up to modern standards.
In any case, the only person who can really diagnose this problem is
the admin for the gerry.vanagon.com server. The mail server and mailing
list software should both be generating log files with success/failures
for all messages sent to the list, and you really need access to those
logs to figure out what’s going on. I think troubleshooting this from
only the client side is going to be almost impossible.
-ben
> On Jan 2, 2020, at 2:00 PM, Ryan Cresawn <jrcresawn@GMAIL.COM> wrote:
>
> The absence of an MX record is an excellent observation Mike. Furthermore,
> no TXT record exists for gerry.vanagon.com. TXT records are used to store
> SPF and DKIM records that are used by other email service providers to
> determine the trustworthiness of gerry.vanagon.com. I am happy to help
> improve the DNS records for gerry.vanagon.com.
>
> Ryan
>
> On Thu, Jan 2, 2020 at 10:49 AM Michael A. Radtke <wa7zpu@5by9.net> wrote:
>
>> Hello,
>>
>> No one commented on my earlier post, so maybe no one is getting my
>> posts as well.
>>
>> GERRY.VANAGON.COM does not appear to have a DNS MX record. Since mail
>> is coming from GERRY.VANAGON.COM some email providers may simply delete
>> messages without valid MX records.
>>
>> Or put another way, mail from GERRY.VANAGON.COM has a trust level of
>> 0.1 on a scale of 0-10 according to https://tools.verifyemailaddress.io.
>>
>> Mike
>>
>
|