Page MenuHomePhabricator

Old pending actions in migrated ML were not imported
Open, LowPublicBUG REPORT

Description

Since at least October 2019, I have lost my password to gain access to wiki-bncf(at)lists.wikimedia.org control panel. This created a particularly frustrating situation, where every day I get a periodical reminder of moderation actions to be taken (namely, two people to add and six spam messages to rebuke).

I have tried to recover my password, but never succeeded. In the end, I gave up trying - also because the list is particularly dormant.

On May 6, 2021, wiki-bncf was eventually migrated to Mailman3. I proceeded to create an account on Mailman3 the next day, with the secondary intention of finally get rid of those actions. I found no pending moderation actions in my new panel control, and I thought the system had automatically discarded them during the migration.

I was wrong. Both yesterday and today, I received again the same reminder I keep receiving since a year and a half.

As of this moment, I am still unable to access the Mailman2 control panel (since I cannot reset my password) AND to take care of those mod actions, since they don't appear in the Mailman3 control panel.

What I would like to happen is to be finally able to take care of those actions on Mailman3. If this isn't possible, I would like to know:

  • if I have to still take care of them through the Mailman2 control panel
  • how can I reset my old Mailman2 password, in order to access the old control panel

Edit (2021-05-08): since from the comments it seems that the old description was not clear, I extensively rewrote it.

Event Timeline

@Sannita: The summary says "Old pending actions were not imported" but the text says that pending actions were not discarded which sounds like a contradiction?
For the records, it's always been possible to request resetting a mailing list password (which isn't needed anymore in Mailman3 as there are user accounts now). Have you registered an account yet ? What exactly makes you think that you cannot take care of those moderation actions?
It's basically unclear to me what this task is asking for. Please also see the scheme on https://www.mediawiki.org/wiki/How_to_report_a_bug - thanks! :)

I rewrote the description, adding more clarifications. HTH.

You don't need to use mailman2. You can simply create an account using the new mailman3 interface. There's no shared account for all list admins anymore.

I think I understand the problem. I had some similar issues too (in some of my mailing lists). I feel it's basically a bunch of small issues feeding each other.

You basically have a mailing list that has pending work to tend to when the upgrade happens. The upgrade doesn't bring them to mm3 (a problem). The upgrade marks the mailing list in mm2 as a disabled list[*] but mm2 happily ignores it and sends "pending work left" to owners while actually being disabled (another problem).

  • I don't know how big of a problem is that it doesn't cross over the pending work. For me it wasn't a big deal. Everything was spam.
  • The problem with mailman in general is the lack of clear definition of "disabled list". We have a hack for it in mm2 (made by WMF SRE long time ago) that basically bans everyone and we apply that in upgraded mailing lists + exim4 won't route emails to it) but it doesn't make the list fully disabled as you can see. I'm working on improving it (like this patch) but that's more complicated than it looks.
  • We do have "rmlist" in both mailmans but we didn't run that (even while the upgrade documentation says we should use that on the old mailing list). The reason is rather obvious, there have been cases that upgrade has failed and we need to revert an upgrade (disabling a list is reversible and rm is not). We had one just yesterday (T282271) but that's quite rare and happens on really old, really complex mailing lists.
  • For me, the solution was simple, I was confident we are not going to revert those upgrades, I just rm'ed those lists. I can do that for this mailing list too if you think that's fine. Otherwise, just wait a week or two and we will pull the plug of mm2 and it won't be sending you emails afterwards.
  • I can reset the password for you if there are emails you want to accept but if you want to just discard them, I can either: rmlist it or wait until mm2 is gone. Whatever works for you. Let me know.

You basically have a mailing list that has pending work to tend to when the upgrade happens. The upgrade doesn't bring them to mm3 (a problem). The upgrade marks the mailing list in mm2 as a disabled list[*] but mm2 happily ignores it and sends "pending work left" to owners while actually being disabled (another problem).

100% accurate.

  • I don't know how big of a problem is that it doesn't cross over the pending work. For me it wasn't a big deal. Everything was spam.

[...]

  • I can reset the password for you if there are emails you want to accept but if you want to just discard them, I can either: rmlist it or wait until mm2 is gone. Whatever works for you. Let me know.

On a personal level, I think I can wait until the whole migration is over, it's not a big problem. I waited a year and a half to get rid of it, I can wait some more time. :)

I don't have any knowledge of other lists having the same problem, but I wanted nonetheless to be sure you were aware of it, before it becomes too late to fix it.