Oops ...
I should've turned off the notification before migration ...
from Mailman 2 to Mailman 3.
Yes, those migrated may have gotten a notification
even if/when already subscribed.
Did a "mass subscription" on Mailman 3,
notably hazardously non-trivial to rename existing list on Mailman 3,
so, on Mailman 3, created "new" (matching existing on Mailman 2) list
balug-test(a)lists.balug.org
But also merging (since hazardously non-trivial to rename) the
(temporary) balug-test3(a)lists.balug.org into balug-test(a)lists.balug.org
and for the existing members on balug-test3(a)lists.balug.org
did a "mass subscribe", for those on balug-test(a)lists.balug.org
that used Mailman's import21.
Shouldn't have that issue with the other list migrations (there's
no existing Mailman 3 target to rename or merge with the existing old
Mailman 2 lists to be migrated).
For the curious, there's also:
https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_3_…
See also:
https://lists.balug.org/pipermail/balug-talk/2024-August/000251.htmlhttps://lists.balug.org/pipermail/balug-announce/2024-August/000346.html
On Sat, Aug 17, 2024 at 9:57 PM <balug-test-request(a)lists.balug.org> wrote:
>
> Welcome to the "BALUG-Test" mailing list!
>
> To post to this list, send your email to:
>
> balug-test(a)lists.balug.org
>
> You can unsubscribe or make adjustments to your options via email by
> sending a message to:
>
> balug-test-request(a)lists.balug.org
>
> with the word 'help' in the subject or body (don't include the
> quotes), and you will get back a message with instructions. You will
> need your password to change your options, but for security purposes,
> this password is not included here. If you have forgotten your
> password you will need to reset it via the web UI.
Michael Paoli via BALUG-Test3 wrote on 2024-07-19 01:51:
> hyperkitty_import -lbalug-test3(a)lists.balug.org import.single.mbox)
That... should've been obvious as it's how one imports lists after all.
> $ (unset LC_ALL && LANG=en_US.UTF-8 export LANG &&
/usr/share/mailman3-web/manage.py
I set up user mailman's .bashrc file so I can just `sudo -u mailman
bash` and have everything set up so I can run mailman and mailman-web
commands.
Anyway, have you fully migrated the lists?
I'm still in a "I've migrated everything but not made MM3 live yet" some
number of months after starting.
Dunno why.
rb
Michael Paoli via BALUG-Test3 wrote on 2024-07-18 01:02:
> Then reimported the message (and reindexed) and it's back again fine.
How, pray tell, did you re-import the message?
I didn't know this could be done and have no idea how to go about it.
rb
A bit interesting b/c even before further adjusting BALUG-Test3 mailing-list subscriber settings, could already view prior archived postings directly via https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.or… by way of the [possibly] more private Tor browser.
Already able to view by Tor all of BALUG's mailing lists at https://lists.balug.org/ including the "older" specific Mailman 2
BALUG-Test list https://lists.balug.org/cgi-bin/mailman/listinfo/balug-test
While can similarly access via the Tor browser the Bay Area's technically-related Noisebridge Hackerspace (
https://www.noisebridge.net/wiki/Noisebridge ), and even that as a non-subscriber, cannot similarly access Oakland's NB-variant
and no doubt fluorishing SudoRoom ( https://sudoroom.org/ )
Its Tor browser 403 error msg consistently displayed as:
~~~~~~~~~~~~~~~~~~~~ quoting ~~~~~~~~~~~~~~~~~~~~
"403 - Forbidden. Note: Tor has been blocked from accessing this
website due to spammer abuse. Please connect without a proxy for
access. Contact sudo-discuss-owner AT sudoroom DOT org if you believe
this is a mistake."
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
One idea for Michael Or Other Possible BALUG.org Admins(*) pending
any possible BALUG-lists-targeting spammers, is similarly as
sudoroom.org to consider blocking Tor if that should prove necessary(?)
* the MOOPBA's is of course _not_ the pithy name of a leadoff band preluding
the Rolling Stones's big Wednesday concert at Levi's Stadium! ;-D
body 1721085516
<postmaster@localhost>
@example.com
postmaster(a)[127.0.0.1]
postmaster(a)example.com
postmaster@localhost
foo|bar|baz
last line of body