Add archival options

Bug #987100 reported by Jeff Breidenbach
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Florian Fuchs

Bug Description

Expose mailmans archival booleans as a tristate, either none/private/public or none/local/cloud.

Related branches

tags: added: mailman3
Changed in postorius:
status: New → Confirmed
Revision history for this message
Richard Wackerbarth (wacky) wrote :

"none/private/public" is an access control policy selector. It does need to be exposed.

"none/local/cloud" is more of a designation of the archive location.
Since there is more "configuration" associated with the archive access, I don't think that this is a useful distinction.
Also, one server might be archiving various lists to a number of different locations.
And, do we allow for one list to be archived in more than one place at the same time?

Revision history for this message
Jeff Breidenbach (jeff-jab) wrote :

The default mailman will allow, on a per list basis, configurable from posterius:

1) no archive
2) local archiving (e.g. pipermail or whatever replaces it, for example hyperkitty)
3) cloud archiving (e.g.,, or similar)

These options are expected to be available even on a default installation of mailman. Exactly what #2 and #3 will have some sort of default, which will be adjustable as a mailman configuration option. The is outside the job of Posterius.

To be clear, this bug is simply asking for the existing mailman tri-state to be exposed to Posterius, and suggests some possible names for the states.

Revision history for this message
Terri (terriko) wrote :

Actually making archives work is going to require some work with postorius + hyperkitty + mail-archive, etc. but putting in the option (and perhaps a note saying that it doesn't currently work) is sufficiently beginner-friendly that I'm putting a tag on this and I'll try to find someone who can work on making sure the options are visible in the interafce.

Changed in postorius:
importance: Undecided → High
summary: - enable archival
+ Add archival options
tags: added: beginner-friendly hyperkitty
tags: added: mailman3-suite-blocker
Revision history for this message
Saprative (saprativejana) wrote :

Florian Fuchs i am tryng to solve this bug. Please explain this bug to me.

Changed in postorius:
assignee: nobody → Yash (yashmehrotra95)
Revision history for this message
Yash (yashmehrotra95-deactivatedaccount) wrote :

I have submitted a patch for this bug. Basically I added the three options that were being discussed in the thread. I could not comprehend where the options should be shown, so I added them in the list settings page.

Please suggest any other changes that I may need to make.

Changed in postorius:
status: Confirmed → In Progress
Revision history for this message
Florian Fuchs (flo-fuchs) wrote :

Hi Yash, thank you for your patch.

However, the way archivers are implemented in the core is a little different. Archivers are added by configuration and exposed by the REST API, not by category ("cloud", "local", ...), but specifically by name.

I have a long running branch that I have linked to this bug report.


Changed in postorius:
assignee: Yash (yashmehrotra95) → Florian Fuchs (flo-fuchs)
Revision history for this message
Florian Fuchs (flo-fuchs) wrote :

The built-in archivers are:

- mhonarc
- prototype

They can be enabled/disabled globally in the mailman.cfg, and on a per-list basis through the REST API.

The branch linked to this bug report implements the per-list (de)activation in the web UI.

Revision history for this message
Florian Fuchs (flo-fuchs) wrote :

Implemented in Rev. #222

Changed in postorius:
status: In Progress → Fix Committed
Changed in postorius:
milestone: none → 1.0.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers