I don't know who's hosting what at this point, but Received header parsing shows that fnfmail.pch.net is the mailing list receiver, which appears (per ARIN) to be hosted by a provider called WoodyNet. Technical details: $ dig mx outages.org +short 10 fnfmail.pch.net. $ host fnfmail.pch.net fnfmail.pch.net has address 69.166.14.18 Host fnfmail.pch.net not found: 2(SERVFAIL) $ whois 69.166.14.18 ... NetRange: 69.166.12.0 - 69.166.15.255 CIDR: 69.166.12.0/22 NetName: WOODYN NetHandle: NET-69-166-12-0-1 Parent: NET69 (NET-69-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: WoodyNet, Inc. (WOODYN) RegDate: 2009-03-25 Updated: 2021-12-14 Ref: https://rdap.arin.net/registry/ip/69.166.12.0 ... Also, to whoever is running the actual SMTP servers now: be aware that amavisd-new on your systems may need some reconfiguration -- in particular, possibly disabling DKIM verification and/or signing (do this at a different layer). I think this is a known problem/complication with mailing list hosting. Two examples from recent mails:
X-Virus-Scanned: amavisd-new at fnfmail.pch.net Authentication-Results: fnfmail.pch.net (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=bway.net
X-Virus-Scanned: amavisd-new at fnfmail.pch.net Authentication-Results: fnfmail.pch.net (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=inet-ops.com
Reading material: https://lists.apache.org/thread/f14lbwd6cxsnmdocj9lkwoppkgm8pkdf -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator PGP 0x2A389531 | | Making life hard for others since 1977. | On Wed, May 28, 2025 at 09:48:10AM -0500, Joseph Anders via Outages-discussion wrote:
Thank you again to all involved with this transition! I get the sense that this was no small feat.
Might we be able to learn what happened with the Puck list? Lots of us here, myself included, manage or maintain Mailman lists/infrastructure. I imagine it would be helpful for us to learn from this so others aren’t stuck in a similar place.
Honestly, I’m fearful of the lists I maintain, that something/some big bug is lurking in the background and could rear its ugly head when I’m least expecting it.
Joseph Anders joe@inet-ops.com
On May 28, 2025, at 12:47 AM, virendra rode via Outages <outages@outages.org> wrote:
Hi all,
Thanks to the efforts of Bryan Fields, Robin McNeill, and Jared Mauch, we were able to successfully import membership lists and archives from PUCK. While we believe we have the most recent list, we sincerely regret to anybody who were re-subscribed despite having unsubscribed.
Please contact outages-owner@outages.org, and we will gladly assist
thanks, /vrode ______________________________________________ Outages mailing list outages@outages.org Sign up for an account https://lists.outages.org/accounts/signup/ To subscribe send an email to outages-join@outages.org To unsubscribe send an email to outages-leave@outages.org To contact the list owners outages-owner@outages.org Archives https://lists.outages.org/archives/list/outages@outages.org/
Thank you for using Outages Lists! For post outage discussion, please redirect to outages-discussion@outages.org
______________________________________________ Outages-discussion mailing list outages-discussion@outages.org Sign up for an account https://lists.outages.org/accounts/signup/ To subscribe send an email to outages-discussion-join@outages.org To unsubscribe send an email to outages-discussion-leave@outages.org To contact the list owners outages-owner@outages.org Archives https://lists.outages.org/archives/list/outages-discussion@outages.org/
Thank you for using outages-discussion Lists!