infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Resolved] (INFRA-16124) Strategy for renamed mailing lists
Date Fri, 01 Feb 2019 05:22:00 GMT


Chris Lambertus resolved INFRA-16124.
    Resolution: Won't Fix

Gonna leave the "random people searching for retired podling emails" to google and take a
pass on maintaining a translation table. Nice to have, but absolutely not worth the effort
on the Infra side. Closing as won't fix, but if it's important to you, we'll evaluate patches
as long as they do not affect the base mod_mbox code.

> Strategy for renamed mailing lists
> ----------------------------------
>                 Key: INFRA-16124
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Mail Archives
>            Reporter: Sebb
>            Priority: Major
> Mailing lists are sometimes renamed.
> For example, is now
> On minotaur, where the mboxes are initially stored, the mbox files have been renamed
to agree with the new list name.
> However the mail archives are served from eos (
> This has a synched copy of the mboxes from minotaur, and a separate area where the mboxes
are indexed for display by mod_mbox. The files in this area are not only ever updated, so
there are now copies of all the original files in the new area as well. There are mails shown
> up to Oct 2016 (when the list was renamed).
> The mails from Oct 2016 are shown here:
> Earlier mails from the original list are not currently shown because they have not been
> It's difficult to follow the history across the rename.

This message was sent by Atlassian JIRA

View raw message