I appreciate all the reciprocity and the outreach. I can’t express my gratitude enough.
We hope Jared is well and I’m sure he would reach out if any help is needed.
More updates to follow
Thanks,
—
regards,
/vrode
> On Apr 18, 2025, at 13:53, Bruce Freshwater via Outages <outages(a)outages.org> wrote:
>
> Andy is right, we are IT people and this list is stellar.
>
> We also have a data center if you need free hosting for a mail server
>
> -bruce
> From: Outages <outages-bounces(a)outages.org> on behalf of Noah Orlando via Outages <outages(a)outages.org>
> Sent: Friday, April 18, 2025 2:39:14 PM
> To: Outages List <outages(a)outages.org>
> Subject: Re: [outages] All Outages list management broken?
>
> Surely not from you, Andy.
>
> Of all people, you referring someone to this list is almost funny—given how recently you trashed it as “kinda worthless” and demanded an after-action report like you were filing a formal complaint with AWS.
>
> Now you’re back, acting concerned because your colleague couldn’t subscribe? Spare us. If the list is so unreliable and broken, why are you bringing others to it? You don’t get to simultaneously undermine the value of a volunteer-run service and then act shocked when it doesn’t roll out a red carpet for your friend.
>
> Maybe instead of playing self-appointed auditor, you could try offering help, patience, or silence. Any of those would be a refreshing change.
>
> Noah
>
> > On Apr 18, 2025, at 2:05 PM, Andy Ringsmuth via Outages <outages(a)outages.org> wrote:
> >
> > Virenda,
> >
> > I suspect there are many on these lists who would gladly lend a hand for both resources and time/expertise.
> >
> > Is Jared open to receiving help?
> >
> > ----
> > Andy Ringsmuth
> > andy(a)andyring.com
> >
> >> On Apr 18, 2025, at 10:12 AM, virendra rode <virendra.rode(a)outages.org> wrote:
> >>
> >> Hi Andy et al,
> >>
> >> I apologize for the delayed response. Jared, who owns and manages PUCK,
> >> has been unavailable. We are aware that something has caused the
> >> mailman to malfunction, but unfortunately, I do not have a current
> >> timeline for resolution.
> >>
> >> While I continue to reach out to Jared, and in the meantime, we are
> >> working on establishing a backup server. This will take a couple weeks
> >> to complete, but it will significantly enhance our system's reliability
> >> going forward.
> >>
> >> I sincerely apologize for the inconvenience caused by the
> >> unavailability of the list.
> >>
> >> Thanks,
> >>
> >> —
> >> regards,
> >> /vrode
> >>
> >>> On Apr 18, 2025, at 07:14, Andy Ringsmuth via Outages
> >>> <outages(a)outages.org> wrote:
> >>>
> >>> Earlier this week I referred a colleague to the Outages lists. They
> >>> haven’t been able to subscribe to any of the lists. All of the links
> >>> below return with the “Bug in Mailman” page. My colleague would have
> >>> posted it but they can’t, because they can’t join.
> >>>
> >>> I suspect something went haywire on the back end perhaps and I wonder
> >>> if it was restored from an old backup config. I noticed all of the
> >>> messages about the Zoom outage on Wednesday went to an old address of
> >>> mine that had been unsubscribed from the lists for quite some time.
> >>>
> >>>
> >>> https://puck.nether.net/mailman/listinfo/outages
> >>>
> >>> https://puck.nether.net/mailman/listinfo/outages-announce
> >>>
> >>> https://puck.nether.net/mailman/listinfo/outages-discussion
> >>>
> >>> https://puck.nether.net/mailman/listinfo/
> >>>
> >>> Bug in Mailman version 2.1.34We're sorry, we hit a bug!
> >>> Please inform the webmaster for this site of this problem. Printing
> >>> of traceback and other system information has been explicitly
> >>> inhibited, but the webmaster can find this information in the Mailman
> >>> error logs or the web server logs.
> >>>
> >>> ----
> >>> Andy Ringsmuth
> >>> andy(a)andyring.com
> >>>
> >>> _______________________________________________
> >>> Outages mailing list
> >>> Outages(a)outages.org
> >>> https://puck.nether.net/mailman/listinfo/outages
> >>
> >
> > _______________________________________________
> > Outages mailing list
> > Outages(a)outages.org
> > https://puck.nether.net/mailman/listinfo/outages
>
> _______________________________________________
> Outages mailing list
> Outages(a)outages.org
> https://puck.nether.net/mailman/listinfo/outages
> _______________________________________________
> Outages mailing list
> Outages(a)outages.org
> https://puck.nether.net/mailman/listinfo/outages
Earlier this week I referred a colleague to the Outages lists. They haven’t been able to subscribe to any of the lists. All of the links below return with the “Bug in Mailman” page. My colleague would have posted it but they can’t, because they can’t join.
I suspect something went haywire on the back end perhaps and I wonder if it was restored from an old backup config. I noticed all of the messages about the Zoom outage on Wednesday went to an old address of mine that had been unsubscribed from the lists for quite some time.
https://puck.nether.net/mailman/listinfo/outageshttps://puck.nether.net/mailman/listinfo/outages-announcehttps://puck.nether.net/mailman/listinfo/outages-discussionhttps://puck.nether.net/mailman/listinfo/
Bug in Mailman version 2.1.34We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs.
----
Andy Ringsmuth
andy(a)andyring.com
