Well, I don't know that there's a whole lot to do quite at this point - notably as it's not yet fully stabilized and configured (most notably still have to get hyperkitty/archiving working properly, then there's still quite a bit more testing to do), but if you note anything amiss ... particularly if consistently so, may want to point it out.
I'm thinking/hoping that the other pieces of Mailman3 are at least meta-stable at this point.
On Fri, Jul 5, 2024 at 10:39 AM aaronco36@sdf.org wrote:
Hi, Thanks for the ongoing status of the Mailman3 testing. Here's hoping that the Mailman 2 --> Mailman 3 migrations continue to proceed successfully and smoothly :-) Further workable/practical/realistic ways to help out in the migration(s), other than _not_ being a potential prodding nuisance about it ? -A
Message: 1 Date: Thu, 4 Jul 2024 19:34:08 -0700 From: Michael Paoli michael.paoli@berkeley.edu To: BALUG-test balug-test@lists.balug.org Subject: Re: [BALUG-Test] Mailman3 testing Message-ID: CAPU_E+ds6dcKZm8rUU_gw8R9OEh5FP-7pMCRKtYhthvoJK3JgQ@mail.gmail.com Content-Type: text/plain; charset="UTF-8"
Still far from even being completely set up, let alone well tested, and Mailman 2 --> Mailman 3 migrations.
But a bit further along, most notably: https://lists.balug.org/mailman3/ So, at least some of the web stuff is working properly, but much of it still has to be properly configured, tested, etc.
On Wed, Jun 19, 2024 at 9:55?PM Michael Paoli michael.paoli@berkeley.edu wrote:
Have some very preliminary Mailman version 3 testing started on the BALUG VM, notably for lists.balug.org General plan (at least shorter term) is to replace the existing soon to be unsupported Mailman 2 with Mailman 3.
So, testing on Mailman3 - presently have one list set up: balug-test3@lists.balug.org Note that it might possibly wink in and out of existence, and/or get reloaded, etc., but general intent is for it to mostly persist and have continuity through testing, And around/after completion of Mailman 2 to Mailman 3 migration, will probably fold it into existing balug-test@lists.balug.org list (which will then be Mailman 3).
At the moment, so far (probably) just email interface, with other bits to come.
So, subscribe, unsubscribe, etc. balug-test3-subscribe@lists.balug.org balug-test3-unsubscribe@lists.balug.org balug-test3-request@lists.balug.org
Note due to some limitations in how the MTA is configured with anti-spam, it will generally filter/reject/drop messages with empty bodies (presumed to be spam), so, to work around that, don't have an empty body. E.g. -request address, to send a command of help, put it in the body, or if in the subject, include a body of: end so it makes it past the anti-spam and gets properly processed. The existing Mailman 2 configuration has these MTA anti-spam configuration limitations noted on the relevant web pages, and the relevant help text, etc. ... but I haven't yet done any such customization on Mailman3.