Hi!
Thanks for the kind words. It's a team effort and I'm lucky to have a
magician (Legoktm) in my team. Like, I told you we can't upgrade private
mailing lists until next or the week after? He fixed it! I'm already
upgrading private mailing lists now.
Responses to issues below.
On Fri, May 7, 2021 at 4:59 AM Risker <risker.wp(a)gmail.com> wrote:
Thank you, Amir and Kunal, for all of your work on
this. It really is
appreciated, and the lists I am on that have been transferred so far seem
to be mostly okay.
I did note that for one of these lists, the "Information" setting somehow
got truncated. As luck has it, we had that fully formatted information on
a page onwiki so I was able to "repair" it quickly.
Yes. I kept a copy of all info fields from the old mailman, so if anyone
lost it, let me know and I can provide it.
I also note that a non-archiving list of which I am one of the owners
shows that it is being actively archived by "hyperkitty". What is that,
and why is anything or anyone archiving a deliberately non-archiving list?
So, as long as the archive policy is set to "Do not archive this list", the
hyperkitty will be noop. (Hyperkitty is the archiver of mailman3 that
provides options like searching). For example for the case of checkuser-l
that doesn't store any archive (~forty mailing lists have this option:
https://phabricator.wikimedia.org/P15505). You can find its page in
hyperkitty, but it's empty
https://lists.wikimedia.org/hyperkitty/list/checkuser-l@lists.wikimedia.org…
Risker/Anne
On Thu, 6 May 2021 at 13:17, Andre Koopal <andre(a)molens.org> wrote:
Hi Amir,
Thanks indeed for the upgrade, something I also think that was highly
needed from a security perspective, so a good thing.
One thing I did notice with my list being migrated is that we had some
lists of non-members being able to post and also some blocked users. I
don't find them back in the settings under message acceptance, but I find
them in the users section under non members. I find this a bit strange.
First of all you really need to go into the user itself before you see if
it is a user you allow as non-member, or that it is a user marked to
automatically discard. Secondly due to that when an account is created on
that e-mail, you see the lists you are a non-member of. You fortunately
can't see why you are a non-member, but it seems a small data-leak to me.
The non-member option in mailman3 is a bit weird. I agree. Non-member can
also mean "accept emails from these address right away" so it's not
negative meaning all the time but as you said, I agree.
Will the old fields to filter users under
settings/message acceptance
still work, or will those users automatically converted to non-members? As
an admin that will be difficult to manage, and it would be at least needed
to be able to filter on the set action so you can see what is what. Also I
don't think the interface should show you the lists you are a non-member of.
Have you tried turning them back to the setting? I haven't tried it yet
and
it might work. For the issues, you can file a bug in phabricator/upstream.
I personally don't see it as a big deal.
Any thoughts from others on this?
Regards,
André Koopal
On Thu, 6 May 2021 at 18:32, Amir Sarabadani <ladsgroup(a)gmail.com> wrote:
Hello,
Two updates:
- We have been upgrading mailing lists to mailman3, now more than 1/4th
of mailing lists have been migrated, more follow today and next week. Some
actions needed (see below)
- We created a new mailing list called listadmins-announce and we are
turning listadmins to a discussion mailing list. So If you don't wish to be
involved in mailing list administration discussions, you can unsubscribe
from listadmins [1] [2]. But being a member of listadmins-announce is not
optional (you can unsubscribe, but you'll be automatically added back in
the next update).
*More on upgrade to mm3:*
Upgrading +700 mailing lists and more than 17 years of digital archive
is... challenging and Mailman3, while being much better than mailman2, is
not perfect.
One known issue is that the upgrade script sometimes truncates the info
field. We have made changes and reported it to upstream to mitigate it but
some mailing lists might not be easily fixable (python version
incompatibilities, etc.). So If your mailing list has been upgraded, please
check and fix that if it happens. Sorry for any inconvenience.
Private mailing lists won't be upgraded for now (possibly later next
week or the week after).
I recommend creating a central account [3] so you can have better
control over mailing lists you are a member of or you are an admin.
Please report any issues to us.
Happy emailing
[1]
https://lists.wikimedia.org/postorius/lists/listadmins.lists.wikimedia.org/
[2]
https://lists.wikimedia.org/postorius/lists/listadmins-announce.lists.wikim…
[3]
https://lists.wikimedia.org/accounts/signup/
--
Amir (he/him)
_______________________________________________
Listadmins mailing list -- listadmins(a)lists.wikimedia.org
To unsubscribe send an email to listadmins-leave(a)lists.wikimedia.org
By sending a message to this list, you email all admins of all lists. To
request technical changes for a specific list, instead create a task in
Phabricator. See
https://meta.wikimedia.org/wiki/Mailing_lists
_______________________________________________
Listadmins mailing list -- listadmins(a)lists.wikimedia.org
To unsubscribe send an email to listadmins-leave(a)lists.wikimedia.org
By sending a message to this list, you email all admins of all lists. To
request technical changes for a specific list, instead create a task in
Phabricator. See
https://meta.wikimedia.org/wiki/Mailing_lists
_______________________________________________
Listadmins mailing list -- listadmins(a)lists.wikimedia.org
To unsubscribe send an email to listadmins-leave(a)lists.wikimedia.org
By sending a message to this list, you email all admins of all lists. To
request technical changes for a specific list, instead create a task in
Phabricator. See
https://meta.wikimedia.org/wiki/Mailing_lists
--
Amir (he/him)