Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65050 - [mailman] add systemd hardening options

Attached to Project: Community Packages
Opened by Jelle van der Waa (jelly) - Saturday, 04 January 2020, 21:07 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 09 November 2020, 09:24 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Since python2 is going away and we still require mailman for our infrastructure I think it would be nice to apply at least some hardenings.

Note: this patch has not been tested extensively.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Monday, 09 November 2020, 09:24 GMT
Reason for closing:  Implemented
Comment by loqs (loqs) - Saturday, 04 January 2020, 23:59 GMT Comment by Jelle van der Waa (jelly) - Sunday, 05 January 2020, 18:41 GMT
No, since it doesn't handle bounce handling yet https://gitlab.com/mailman/mailman/issues/343
Comment by Sébastien Luttringer (seblu) - Monday, 06 January 2020, 12:42 GMT
The patch looks good. Works well on my mailman setup. It's in mailman-2.1.29-2.

@loqs: Given that migration must be done ingesting old data into the new mailan following a step by step guide[1] and there is no packet name conflict, I would rather suggest to leave the package mailman die without replace or renaming.

I remember David Runge was interested in working on Mailman3 suite.

[1] https://docs.mailman3.org/en/latest/migration.html
Comment by David Runge (dvzrv) - Thursday, 06 February 2020, 11:49 GMT

Loading...