I'm going to bet it was a DNS resolution issue, both mgm51.com and
mgm51.net were not resolving at all around the time he sent that message.
On 3/27/22 10:19 AM, Gary Gapinski via mailop wrote:
Your message to the list has the header
Received: from oneyou.mgm51.net (*unknown* [174.136.99.202])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
(No client certificate requested)
by mx.mailop.org (Postfix) with ESMTPS id 4KR1t64s9yz8sqQ
for<mailop@mailop.org>; Sun, 27 Mar 2022 05:44:46 +0200 (CEST)
which implies a DNS resolution failure for 174.136.99.202 which could
have caused the reject by an MTA that requires a correspondent MTA to
have good DNS.
As of this writing, but perhaps not earlier, 174.136.99.202 has
correct FCrDNS.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
