Archives were deleted as there was nothing of value to keep besides two spam emails and Nemo saying to delete the list.

because it was re-created in T99443.

Done. Please check your email.

All blockers closed.

Disabled.

Disabled.

No response at all. As such, I am going to close the list [really unfortunate as it is a project mailing list] and if any one wants to administrate it, they can after requesting it be reopened.

Looking at the issue, @KuboF seems to suggests [gtranslate] the list is not in active use and that he also has no time to manage the list if he was given it. As such, given no real community interest - I'm going to close the list. It can be reopened at any time if someone is interested in managing the list however.

Closing as declined for several reasons:

https://wikitech.wikimedia.org/wiki/Mailman#Fighting_spam_in_mailman should be the aggregated source for this information. Really we should collectively work on improving it and as when I cleared up docs, that information was valid as best as could be.

Adapted message from wiktionary-l also posted to local wiki here. Same applies, if no response by Friday (at all, even a 'can't read English' response as this is not a English wiki), will close too.

I've repoked the IRC channel and asked onwiki (link). If there is no interest by Friday, I'll close the list.

Sent to the email listed in the request, created as a private list.

After reviewing this and the comments about the existing list, seems valid. The description has all the info necessary. Will follow up in a few.

Since this ticket is about a mailing list which seems there is consensus that wikitech-l would be sufficient (for now at least!), I'm going to close this as declined.

There was a suggestion by (I think) @hashar about moving the catch point alerts to a new list like ops-infrastructure (or otherwise named list). I do find these annoying either way (so thanks Yuvi :D).

In T117034#1765164, @jcrespo wrote:

It handles *very private data*, it should be part of the production network. I think there is not infrastructure there yet handling VMs. Because of firewall and network restrictions, it could not even possible now. If there is something that will be implemented on production, it will be containers, not VMs.

Production already has virtualisation with VMs, it's Ganeti. To put it into perspective it runs several production sites and 'key' infrastructure as well like the mail servers (mx*). They're treated like production hardware in theory so firewall is not an issue at all.

Resolved now with the above fix. Re-closed the list and subscriptions should be rejected.

In T59246#1763733, @Nemo_bis wrote:

I question the original introduction of it honestly.

You are free to open a discussion to change the policy.

I don't see why I need to open a discussion to change a line that was only listed on the guideline creation instructions followed only by Ryan? They were changed to reflect reality today anyway.

Please find consensus or request this for individual lists instead of re-opening this one. The overall objective of this ticket has been declined and will not be done. The continuous dispute over it is not useful either.

The point still stands however that forcing an opt-in is inappropriate. We're not in a place to judge whether or not a lists archives should (at this stage now) forcibly put into Gmane. Plus considering the number of lists being 100, it is neither worth the time unless a list individually requests it.

Hm? Interesting!

T110586 seems pretty related which is also under no consensus or clear reasoning behind needing a list.

I can find no request or evidence of the list being requested or created. Likely I shall assume it was an out-of-band request directly to Ryan or someone else who had the list creator password/master password.

@Krenair yes this is Mailman related it seems, a list exists at least.

This is now done, enjoy the correct list situation :)

Ah! I see, thanks for pointing this out to me. I copied the full configuration over from the private list to the public list to ensure all members are subscribed, passwords are the same and so on, to make the change more easily integratable into any workflows.

If the list should be closed, I can close it the correct way and thus avoid an emails being generated at all, if that's what you want rather than resetting and dealing with the queue?

See P2224 which is a full list of all lists that don't exist in Gmane but should.

I have actually just received an email from a Gmane administrator. They've provided me a list of all lists that are currently being monitored and clarity on how they want the mboxes. I will follow up from there.

Even the instructions are unclear and seem fairly directed at '1 or 2' lists. When you get into the boundaries of near a hundred, just emailing gets complicated, length and annoying for everyone involved.

I have:

Archives have stopped? Interesting, I'll look into that now.

@Selsharbaty-WMF This sort of went under radar lately with me so:

Please check your email.

I've looked at the info page and it seems the code is pure HTML. Please see the example above and convert the subscription page to mailman.

Is the form pure HTML or the Mailman form itself? If it is pure HTML, they no longer work after spam improvements in 2.1.16 and must use the mailman form.

In T116288#1745660, @Krenair wrote:

Is this part of the version of mailman we're using?

Yes. It is built for the 2.1.x branch and I have it working in labs [which is, finally, a production clone].

What do you want to achieve by this? I've set this up on labs to look at it and currently it seems you can only list subscribers to lists, (un)sub an address and send emails to lists through the API. More clarify would be essential here.

Set the current listadmin to a listmoderator (standard practise, feel free to remove them however) and the new password has been sent to the -owner address (and thus the email noted).

Yeah sure. I'll do this now.

Mailman has no concept of -owner emails being moderated, which is a major issue with 2.1.x. [basic]

Above commit will resolve this. Unsilenced icinga check.

Stealing assign.

Sent an email to Lars.

I think this is a forwarded email from a subscriber of WikimediaMobile to the WMF All list. Nothing really from this side needed. Since the listadmin for the wmfall list is set to techsupport@wikimedia.org, all these emails are sent to you.

Will look into this with consideration comments from @Dzahn

Is there any progress on this regarding whether a mailing list should be created or not?

In T115300#1733540, @Ariconte wrote:

Would someone with the appropriate rights please add wikimedia-l to the regular_include_lists

I did that above in my closure. Please monitor and report back if it doesn't solve the issue :)

What is the email address that should be used for the list administrator?

The reason is the list is not set to forward at all.

Accidental close?

Done.

Confirmed but is upstream mailman. Could you report a bug there instead please?

Just to clarify - this is beta not production. CheckUser is *not* enabled on beta for more or less this reason and oversight is neither (revdel'd thing also should not be sensitive).

Tried to test this by un silencing the mailman queue check (permissions noted above are correct) yet I get that I am not authorised to do so.

In T107445#1711531, @Selsharbaty-WMF wrote:

At this point we will have one list only, right? education-collab-private. And the archives will not be on it nor on anywhere, right? The archives will be lost.

Archives will remain at the location of the private list.

In T111243#1712951, @Deskana wrote:

We believe this is blocked by Ops, who are currently attending their offsite. This task isn't urgent and can wait until the offsite has concluded.

vbaranetsky is associated with the @wikimedia.org address. Seems connected to me.

Needs per queue levels.

Disabled. Archives are still public.

With https://lists.wikimedia.org/pipermail/ee/2015-October/001549.html being sent, disabling.

With the new naming scheme, 'affiliates' seems fine with me. Can I have an email(s) for the listadmins?