
Hi, As discussed earlier, mailman2 is end-of-life and no longer supported. We are planning to upgrade the mailing lists from mailman2 to mailman3. This will be done in-place, importing the previous archives and user list into a mm3 instance hosted at the same URL lists.boost.org. An example staging instance can be viewed at https://lists.preview.boost.org Mailman3 is more complex than Mailman2 with multiple components including "web" and "core". After the upgrade your account should still exist in the core backend, which means you will continue to receive messages and be able to send emails. However, to interact with the web frontend (optional) you must register an account using the same email address at https://lists.boost.org. Registering in the web portal will require setting up a new password, and confirming the email address. Be sure to use your existing email from before. Any previous passwords will not be valid. If you don't create an account in the web UI, your email subscriptions to the lists continue. But you can't yet log in to configure the account. No action is needed right now. Wait until after the upgrade. All previous messages will be imported to the new system. Additionally, the earlier archives in the form of static plain html pages will be available at https://listarchives.boost.org/ The imported lists are Boost, Boost Announce, and Boost Users. Activity on any other lists is remarkably low such as 1-2 emails per year. Please migrate other discussions to Github Issues, Slack, or one of the main mailing lists. Let us know any concerns. Report issues in the github repository cppalliance/boost-mailman. The tentative schedule is Tuesday June 17. Plan on not using the list for one day, or perhaps a few days. Roll back to mailman2 if something unusual is discovered soon after going live. Chat out-of-band in cpplang slack boost channel.

On 04/06/2025 14:28, Sam Darwin via Boost wrote:
Hi,
As discussed earlier, mailman2 is end-of-life and no longer supported.
We are planning to upgrade the mailing lists from mailman2 to mailman3.
This will be done in-place, importing the previous archives and user list into a mm3 instance hosted at the same URL lists.boost.org. An example staging instance can be viewed at https://lists.preview.boost.org
Thanks for the heads up Sam, and good luck ;) Best, John.

On Wed, Jun 4, 2025 at 6:29 AM Sam Darwin via Boost <boost@lists.boost.org> wrote:
All previous messages will be imported to the new system. Additionally, the earlier archives in the form of static plain html pages will be available at https://listarchives.boost.org/
Are the historical posts going to render correctly in the archive after this change? Without the weird high-ascii characters? Thanks

On Wed, Jun 4, 2025 at 10:39 AM Vinnie Falco <vinnie.falco@gmail.com> wrote:
On Wed, Jun 4, 2025 at 6:29 AM Sam Darwin via Boost <boost@lists.boost.org> wrote:
All previous messages will be imported to the new system. Additionally, the earlier archives in the form of static plain html pages will be available at https://listarchives.boost.org/
Are the historical posts going to render correctly in the archive after this change? Without the weird high-ascii characters?
Thanks
The hosting of historical posts varies: 1. https://listarchives.boost.org/ are the "static plain html pages", copied via rsync from the old server to a new machine directly. They seem to exhibit the same problem about utf-8 characters as before. No better or worse. 2. The new production mailman3 instance (which will be the main server) fixes utf-8, so the weird characters are gone from previous posts. Notice how Dmitry's name is readable. https://lists.preview.boost.org/archives/list/boost-users@lists.preview.boos...

El 04/06/2025 a las 19:04, Sam Darwin via Boost escribió:
2. The new production mailman3 instance (which will be the main server) fixes utf-8, so the weird characters are gone from previous posts. Notice how Dmitry's name is readable. https://lists.preview.boost.org/archives/list/boost-users@lists.preview.boos...
Can lists.preview.boost.org be configured to provide per-date and per-author views like the old archive page? Joaquin M Lopez Munoz

Can lists.preview.boost.org be configured to provide per-date and per-author views like the old archive page?
By the way, all list owners and settings are imported. The configuration remains as similar as possible. However, there are limits. mm2 offers the choice of "by date" or "by thread" display. It looks like Hyperkitty defaults to a "Threads" view, where replies are included below the top-level one. That is the way mm3 works. There isn't a "by date" view (separate from a threads view).
Can these be fixed, or do the source files for those messages not contain the original data?
Consider this page that garbles grisumbras's name: https://listarchives.boost.org/boost-announce/2025/05/date.php The most "original content" available on wowbagger are the archive files. They contain something illegible: "Ð Ð ¼ Ð " Those characters are copied exactly verbatim to the listarchives machine, and it shows the same bad result as before. But the machine https://listarchives.boost.org shouldn't be a major focus. It's a sort of backup. The new real server will also have the imports, corrected/fixed, and they are searchable.

Or, wait.. if the "import" process is accessing "source content" which is are "mbox" files, those are a better original source of the problematic content (utf-8 characters). Ok. But reformatting those into a mailman2 type of webpage such as https://listarchives.boost.org/boost-announce/2025/05/0639.php would be a major effort with no benefit. Since the mailman3 import is doing the same thing, but it's formatting the emails into a searchable up-to-date Django interface on the new server.

On Wed, Jun 4, 2025 at 10:44 AM Sam Darwin via Boost <boost@lists.boost.org> wrote:
The most "original content" available on wowbagger are the archive files. They contain something illegible:
"Ð Ð ¼ Ð "
That's actually good news I think, as those are the original utf-8 encoded code points which can be translated by a script if we choose to write it. They are just not encoded properly for HTML.
The new real server will also have the imports, corrected/fixed, and they are searchable.
Oh, so we have a new archive alongside the old one, and the new archive goes as far back as the old one, and the messages are corrected and searchable? That's great! Thanks

ср, 4 июн. 2025 г. в 21:09, Vinnie Falco via Boost <boost@lists.boost.org>:
Oh, so we have a new archive alongside the old one, and the new archive goes as far back as the old one, and the messages are corrected and searchable? That's great!
The current (old) archive goes back to November 1998 https://lists.boost.org/Archives/boost/1998/11/date.php The new one goes back to March 2013 https://lists.preview.boost.org/archives/list/boost@lists.preview.boost.org/...

On Wed, Jun 4, 2025 at 12:16 PM Дмитрий Архипов via Boost < boost@lists.boost.org> wrote:
ср, 4 июн. 2025 г. в 21:09, Vinnie Falco via Boost <boost@lists.boost.org
: Oh, so we have a new archive alongside the old one, and the new archive goes as far back as the old one, and the messages are corrected and searchable? That's great!
The current (old) archive goes back to November 1998 https://lists.boost.org/Archives/boost/1998/11/date.php The new one goes back to March 2013
https://lists.preview.boost.org/archives/list/boost@lists.preview.boost.org/...
Interesting. So the mbox files on wowbagger used by the mailman3 import process go back to 2013. The archive php files date back further.

On Wed, Jun 4, 2025 at 11:26 AM Sam Darwin via Boost <boost@lists.boost.org> wrote:
...
It is not a high priority, and eventually I would like to see: * A single archive of all posts going back to 1998 * All utf-encoding glitches fixed * Fully indexed by thread, by date, by month, and so on * Using the new Postorius style sheets Thanks

El 04/06/2025 a las 15:28, Sam Darwin via Boost escribió:
Hi,
As discussed earlier, mailman2 is end-of-life and no longer supported.
We are planning to upgrade the mailing lists from mailman2 to mailman3.
[...]
All previous messages will be imported to the new system. Additionally, the earlier archives in the form of static plain html pages will be available at https://listarchives.boost.org/
It'd be nice if a redirect were put in place so that, for instance, https://lists.boost.org/Archives/boost/2025/06/259640.php gets automatically routed to https://listarchives.boost.org/Archives/boost/2025/06/259640.php Lots of such URLs are scattered through the Internet, in code comments, etc., so we want to preserve them. Hopefully old archive URLs don't clash with URLs to the new archive --from a cursory look seems to me we're good in this respect. Thank you, Joaquin M Lopez Munoz

El 04/06/2025 a las 15:28, Sam Darwin via Boost escribió:
Hi,
As discussed earlier, mailman2 is end-of-life and no longer supported.
We are planning to upgrade the mailing lists from mailman2 to mailman3.
[...]
All previous messages will be imported to the new system. Additionally, the earlier archives in the form of static plain html pages will be available at https://listarchives.boost.org/
It'd be nice if a redirect were put in place so that, for instance, https://lists.boost.org/Archives/boost/2025/06/259640.php gets automatically routed to https://listarchives.boost.org/Archives/boost/2025/06/259640.php Lots of such URLs are scattered through the Internet, in code comments, etc., so we want to preserve them. Hopefully old archive URLs don't clash with URLs to the new archive --from a cursory look seems to me we're good in this respect. Thank you, Joaquin M Lopez Munoz

Joaquin M López Muñoz wrote:
It'd be nice if a redirect were put in place so that, for instance, https://lists.boost.org/Archives/boost/2025/06/259640.php gets automatically routed
@Joaquin, the redirects to https://listarchives.boost.org are in place. And, this is a message from the new server. Testing.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
The "Unsubscribe & other changes" link at the bottom of each email directs you to Page not found now. Matt

Matt Borland wrote:
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost The "Unsubscribe & other changes" link at the bottom of each email directs you to Page not found now.
Matt
Testing the footer links.

On Tue, Jun 17, 2025 at 12:11 PM Matt Borland via Boost < boost@lists.boost.org> wrote:
Testing the footer links. _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org
Footer links look good.
They don't look good to me. I don't see a link to the archives. Or more importantly, IMO, a link to the message itself on the archive. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supongas Nada -- Robot Dreams - http://robot-dreams.net
participants (8)
-
Joaquin M López Muñoz
-
John Maddock
-
Matt Borland
-
René Ferdinand Rivera Morell
-
Sam Darwin
-
samuel.d.darwin@gmail.com
-
Vinnie Falco
-
Дмитрий Архипов