infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Resolved] (INFRA-18153) mbox-vm handling of podling mailing lists
Date Fri, 26 Apr 2019 19:05:00 GMT


Sebb resolved INFRA-18153.
    Resolution: Fixed

The new script appears to be working OK.

> mbox-vm handling of podling mailing lists
> -----------------------------------------
>                 Key: INFRA-18153
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Assignee: Chris Lambertus
>            Priority: Major
>              Labels: mbox-vm
>         Attachments: mbox2_prvdup.txt, mbox2_pubdup.txt
> AFAICT, all the current podling mailing lists are archived on minotaur under their own
domains, e.g.
> However, mbox-vm stores podling mail lists under <podling>
> This will cause issues for mail-archive/mail-private, and also means that additional
work will be needed when a podling graduates.
> I think it was to avoid such work that the bin/.archives now routes podlings to their
own domain (for public archives). Also to make it easier to find the archives when a podling
> It is likely to be much easier to fix this before mbox-vm becomes the source for mail-archives.
> Note that there are some historic archives for retired podlings under public-archives/
The last two such podlings were Wave and ODF, which do have some archives on mbox-vm. Earlier
retirements were before mbox-vm started accepting e-mails.
> I think the best approach would be to mirror the current minotaur layout for public archives.
> This means changing the way podling emails are stored by mbox-vm, and fixing up historic
directories for graduated/current podlings. Where a podling graduated mid-month, this will
mean merging mbox files.

This message was sent by Atlassian JIRA

View raw message