NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
The following lists are inactive:
https://lists.fedoraproject.org/archives/list/security-team@lists.fedoraproject.org/ https://lists.fedoraproject.org/archives/list/security@lists.fedoraproject.org/
Please disable them and mark them as a archived. Thank you.
There is also https://lists.fedoraproject.org/archives/list/security-private@lists.fedoraproject.org/ -- I don't have access, so I don't know if there is activity or important stuff in the archives. I think this should be disabled too... and possibly archives removed to make sure what was meant to be private stays that way.
It's not really a rush, since they've been sitting there doing nothing and could continue. But I think the dead lists are kind of harmful in appearance, and may send people in the wrong direction. So, I dunno, 2024/05/11?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
It doesn't seem we have a documentation in place for how to archive mailing list. At least I wasn't able to find any.
@zlopez Those docs would probably be good to have.
In the past, I think what we've done is just go into mailman and set it to drop or bounce incoming posts, and then change the description to include MOVED or ARCHIVED or CLOSED.
Yeah, should make a howto?
should be in web interface:
set settings -> list identity -> to have [ARCHIVED] at the end of the display name set settings-> message acceptance -> reject with notification set settings -> subscription policy -> confirm then moderate
There may be a better way in newer mailman3...
I think we do want to keep the archives at least in almost all cases.
Metadata Update from @zlopez: - Issue assigned to zlopez
Let me do that and write a how to.
I'm not sure if there will be better way in mailman3.
All of the lists are archived and here is the PR for the guide
Metadata Update from @zlopez: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.