All “Archives” links on Mailing Lists give a “403 Forbidden” at the time of writing. Who can fix that?
–Bence
2 Likes
Thanks for reporting. @gbaz will know what should be done, or alterntatively any of the Haskell admins: GitHub - haskell-infra/haskell-admins: Information and resources regarding Haskell infrastructure admin team
I have pestered them through IRC, hopefully the archive is not lost.
1 Like
I think @gbaz is called @sclv here.
1 Like
Thanks for the report – fixed! Some permission changes went funny on a server upgrade. By the way – if anyone is or knows someone who is capable of performing a reliable mailman2 → mailman3 migration, we could really use a hand. Its been a long term project and finishing the last mile on it would greatly improve our infrastructure!
8 Likes
Thank you! And thank you for all that behind-the-scenes work that we only notice when something goes wrong.
5 Likes
Thanks a lot for the fix!
1 Like
Something seems to be mucked up again. I’m getting ‘403 Forbidden’ or some unfamiliar formatting/threading. Like the whole of mailman is being rejigged. (And I can’t seem to sign on or post anything, otherwise i’d report it there.)
If this is deliberate upgrade, I’m happy to stay away for a while. But where was the advance notice?
Indeed, we’re mid-migration of the long-awaited upgrade to a new mailinglist box, and to use mailman 3. This is something we’ve needed to do for approximately seven years, and hopefully will be completed soon!
(While things may have been running smoothly on the surface, the box we were using was roughly 15 years out of date – three system migrations ago compared to all our other boxes. The software was approximately 20 years out of date. the new interface is what the new version of mailman [i.e. the only modern and supported version] provides.)
2 Likes
We’re going to be restoring old links, but in the meantime you can, for example, access the haskell-cafe archives at Haskell-Cafe - Haskell.org
1 Like
Thanks very much to everyone contributing to keeping this infrastructure running!
4 Likes
As a reminder, the infrastructure that powers the Haskell community is maintained by a group of volunteers who generously give their own time to keep things running. In some cases these volunteers have been helping out for decades and have significant experience in the best way to maintain Haskell resources. I for one am very grateful to them, and I think my view is shared by the vast majority of the community.
13 Likes
Just a friendly reminder that it would be of utmost importance to redirect from old links such as https://mail.haskell.org/pipermail/haskell-cafe/2025-August/137193.html. Otherwise lots and lots of links remain broken.
1 Like
Yep, that’s still going to happen – just one step at a time. We just finished troubleshooting getting mail delivery cut over, I believe archives are next.
2 Likes
Indeed there was a window of archived mail which didn’t make the initial migration. I have transferred this and believe that we should now have full archives. I’d urge anyone who sees any further broken links to reach out.
“needed” in the sense that the software configuration was previously unmaintainable, the software itself was well beyond its end-of-life and an active security liability, and the hardware was costing us money to keep alive. I completely agree with @sclv; this migration was long overdue.
Sadly, mail infrastructure is among the hardest of services to migrate.
Yes, I agree that while mailman3 may be prettier, it is also less usable. If someone wants a project, it would be great to improve this upstream (Thread overiew by month (#335) · Issues · GNU Mailman / HyperKitty · GitLab would be a great starting point).
Sadly, it does seem that mailman is seeing relatively little development at this point so I doubt this will improve unless someone steps up.
I can confirm that I also observe this. The cause is not immediately clear. I’ll need to investigate further.
4 Likes
Is there an easy way to volunteer to archive the mailing list (and other things)? Text is almost free and I have plenty of room to archive the entirety of the mailing list at no cost to myself.
Just to be clear, the problem here is not the size of the archive. We took great pains to ensure not only that older messages are imported into the Mailman 3 archive but also that older pipermail archive links continue to work.
Rather, the problem pointed out by @AntC2 above is that at least one message from hugs-bugs is malformed (specifically, bearing a date from year 999), causing mailman 3’s archive application to choke.
Nevertheless, if you do wish to preserve the mailing list the full archives can be downloaded in mbox form from mail.haskell.org.
Thanks Ben. You mean Æthelred the Unready was posting a Hugs Bug??
Not that old, but if I look in the old archive: The Hugs-Bugs Archives , there’s a message dated 1970. That can’t be right, but at least in my browser it’s showing a legit date/time.
Thank you for getting Hugs-Bugs at least visible in mailman. It’s not all that happy, though: that spurious 1970 message (titled OSX) is now repeated in every month and every year from March 1970 up through the 70s, 80s, 90s to early 2000s. From October 2000 on, it appears mixed in with genuine historic posts. (Also historic posts Aug-Sep 2000 seem absent.) OSX makes its last appearance 2002 October. Not to be confused with the genuine 2002 November thread titled ‘Mac OSX’.
I guess it’s not worth the effort of trying to fix this. (There also seems quite a bit of spam in those early years.) When you declare ‘done’, perhaps post this message to the list?
Edit: Or perhaps this is some sort of display behaviour? In the pipermail archive, if there’s no posting in a month, that month doesn’t appear in the dropdown. In mailman, every month appears in the dropdown, but the threads shown might be from (much) earlier.
Edit 2: No, it’s more yeuchy than that. Compare, for example, list ‘jhc’: the earliest post is 2006 October. No posts in Nov-Dec, and mailman says so.