- BALUG-Test - lists.balug.org

test ignore 1737494832
by Michael Paoli 21 Jan '25

21 Jan '25

test ignore 1737494832

1 0

test - ignore 2025
by Michael Paoli 21 Jan '25

21 Jan '25

test - ignore 2025

1 0

Re: test - ignore
by admin＠bclug.ca 14 Sep '24

14 Sep '24

Michael Paoli via BALUG-Test wrote on 2024-09-07 21:04: > Yet another footer test. Hopefully this one's looking pretty good. Can I suggest putting a link to the archives in the footer? I find them handy on the MM3 mailing list to sometimes load a thread in a browser, or even up-voting a particularly informative post to raise its visibility.

2 2

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-zonccynfajjfpfhzsray＠balug.org 10 Sep '24

10 Sep '24

From: <test-zonccynfajjfpfhzsray(a)balug.org>

2 2

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-yfeocxibuiqwpqrazjjb＠balug.org 10 Sep '24

10 Sep '24

From: <test-yfeocxibuiqwpqrazjjb(a)balug.org>

1 0

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-xtxqganorxlaqoseeqot＠balug.org 10 Sep '24

10 Sep '24

From: <test-xtxqganorxlaqoseeqot(a)balug.org>

1 0

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-wdmtkiebfgonncqvovui＠balug.org 10 Sep '24

10 Sep '24

From: <test-wdmtkiebfgonncqvovui(a)balug.org>

1 0

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-wahircvyromigwipnavk＠balug.org 10 Sep '24

10 Sep '24

From: <test-wahircvyromigwipnavk(a)balug.org>

1 0

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-vqvdnjhxiaksewzlgynp＠balug.org 10 Sep '24

10 Sep '24

From: <test-vqvdnjhxiaksewzlgynp(a)balug.org>

1 0

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-vliprfedvkvrjsbgqnhj＠balug.org 10 Sep '24

10 Sep '24

From: <test-vliprfedvkvrjsbgqnhj(a)balug.org>

1 0

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-upygpupsyaelwgnakcpf＠balug.org 10 Sep '24

10 Sep '24

From: <test-upygpupsyaelwgnakcpf(a)balug.org>

1 0

test - ignore (additional email addresses on same member - additional nut susscribed but member is)
by test-tslkosojfvkdgwyebpia＠balug.org 10 Sep '24

10 Sep '24

From: <test-tslkosojfvkdgwyebpia(a)balug.org>

1 0

Fwd: list acceptance/moderation and balug-announc@lists.balug.org hold --> discard for most users
by Michael Paoli 09 Sep '24

09 Sep '24

And, for those that may not have seen it and may be interested, also archived at: https://lists.balug.org/mailman3/hyperkitty/list/balug-admin@lists.balug.or… ---------- Forwarded message --------- From: Michael Paoli <michael.paoli(a)berkeley.edu> Date: Sat, Sep 7, 2024 at 6:17 AM Subject: list acceptance/moderation and balug-announc(a)lists.balug.org hold --> discard for most users To: BALUG-Admin <balug-admin(a)lists.balug.org> One thing I do like about Mailman 3 is all the available message acceptance settings, both for list default, and per user. Those include: List default -- follow the list's default member action. Hold -- This holds the message for approval by the list moderators. Reject -- this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. Discard -- this simply discards the message, with no notice sent to the post's author. Accept -- accepts any postings without any further checks. Default Processing -- run additional checks and accept the message. Most notably - Discard highly useful to set non-members to Discard. Likewise for moderated list(s) where few are allowed to post (e.g. balug-announce(a)lists.balug.org). Makes listadmin life fair bit easier, as most all such posting attempts, that would otherwise be held for moderation on Mailman 2, can be simply discarded, as almost all of them are junk/garbage/spam and the like - maybe only about once a year or so does a legitimate message come in that way. And Reject really isn't that useful, as that happens after the email has already been received, rather than at SMTP time, so there would be backscatter issues with that (the overwhelming number of such mail is spam, and those are typically rather to quite forged senders, victim compromised accounts, etc.). And ... not sure exactly how much I (dis)like it on Mailman 3, but Mailman 2 data was mostly in python 2 pickle (.pck) format files, with data/configuration bits also being in flat (and also html) files. Well, Mailman 3, while some configuration bits are stored in flat configuration files, for better and/or worse, most of the data is stored in an actual relatively proper database (e.g. sqlite). So, balug-announce(a)lists.balug.org e.g. imported from Mailman 2, most all users had the moderation set to hold (Mailman 2 didn't have a discard option). On Mailman 3 I set the list default to discard for that list. But almost all users were imported from Mailman 2 and that import preserved their hold setting. I wanted to change it for those users to the list default (discard). A bit to chase it down in the database, but once found and reasonably tested, one SQL statement to do the needed: UPDATE member SET moderation_action = NULL WHERE list_id = 'balug-announce.lists.balug.org' and moderation_action = 0; ... and with that done for 492 users. Yay!(?) Not super easy/pleasant but ... well, compared to Mailman 2, yeah I think it's at least fair bit better than Mailman 2, at least on that point/feature/capability.

1 0

Re: Testing: mailing list aliases
by Michael Paoli 09 Sep '24

09 Sep '24

Well ... I see this one, looks to be direct, not via list. I'm guessing a BCC: michael.paoli(a)berkeley.edu or the like, as I'm not otherwise seeing one of my addresses in the headers. And did land in the "Spam" folder for that mailbox (which is hosted by gmail ... it's only semi-smart about these things). Gmail mostly accepts (almost) everything ... fairly permissive ... though it will SMTP reject some things. And what it does accept, much is place in user's Spam rather than Inbox, and probably some fair bit is also silently discarded. I don't think it made it to balug-test(a)lists.balug.org list. Mailman may likely have silently dropped it with or the like. If it was hard bounced, you should be able to see that. # grep -A 2 -a -e 'f5e9353b-1a90-49a3-9239-d9acd4787b39(a)ronaldbarnes.ca' /var/log/exim4/mainlog 2024-09-09 10:47:54 1snbvv-001iPM-0J <= ron(a)ronaldbarnes.ca H=mail.ronaldbarnes.ca [2607:5300:203:b716::1:2] P=esmtps X=TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=no S=1820 id=f5e9353b-1a90-49a3-9239-d9acd4787b39(a)ronaldbarnes.ca 2024-09-09 10:47:54 1snbvv-001iPM-0J => balug-test(a)lists.balug.org R=lman3_router T=mailman3_transport H=localhost [127.0.0.1] C="250 Ok" 2024-09-09 10:47:54 1snbvv-001iPM-0J Completed # Looks like it was accepted, then probably silently discarded by Mailman 3, per its (default) configuration on that for that list. It will also silently discard if the email attempting the post isn't subscribed. Yup: # grep -a -F -e 'f5e9353b-1a90-49a3-9239-d9acd4787b39(a)ronaldbarnes.ca' /var/log/mailman3/mailman.log Sep 09 10:47:55 2024 (1928) DISCARD: <f5e9353b-1a90-49a3-9239-d9acd4787b39(a)ronaldbarnes.ca>; ['The message is not from a list member'] # By the way, Mailman 3, can actually have multiple email addresses associated with a web UI login account. I think if you do that and the account is subscribed, then it will handle post from any of them as if it was from that same account. Not sure if I've (fully) tested that, though. Can also be done the "old fashioned" Mailman 2 way too. E.g. subscribe multiple email addresses. Then just configure to disable delivery on those one doesn't want it to (also) send to. Anyway, full headers: Delivered-To: michael.paoli(a)berkeley.edu Received: by 2002:a50:d69b:0:b0:5c2:524b:7173 with SMTP id r27csp1432752edi; Mon, 9 Sep 2024 03:47:52 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCVmb60v7myMeyIPUrpCLNA2WLEQ3aRi/2QbEFDiKH/JsiC017t3nEDPTdyH+DxURn2lvovKmRo55uLOrg8t(a)berkeley.edu X-Google-Smtp-Source: AGHT+IG/DdCBvm/o4lvbpt8OWjOSned6JSGVWWirrDC+NaIqPCsLd/AhavxaRQplTtCmUdgl89cq X-Received: by 2002:a05:690c:2f0e:b0:6a9:4fdd:94e5 with SMTP id 00721157ae682-6db44dc3925mr80625247b3.13.1725878871891; Mon, 09 Sep 2024 03:47:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1725878871; cv=none; d=google.com; s=arc-20240605; b=YrlvlQXadXYWFmSParbxeRcrZ/YX8RZdbWJVEJ+Q1IGl1QTvKpZ19JjUoGfvVFHjuo GctzmhW+mumbcgDE58OajfiSWNw4pWuq1RY8nJl/SnD51/DcAYiFG5KhR3kcMOpyxR7Y hpbUuXrUpPws5MjvSVYXaYv+72Qvr+QF6Oa5sAAVxCgevuFWY0o/KWtLSej8YTJhuGo4 BXoPZbq+VF50kYIqXRnGDMZb7HvofX/k9yxx7WC+pMKqbB+yy/UNj0NB3sz8D0jum8mw +z4rHtivArcAzvkhdoaOQBos9Hk6J21feF9U4vRG2hD7cCuzExn8iWPsAiSDA0GfSBX/ llFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:content-language:to:subject:from :user-agent:mime-version:date:message-id; bh=j4IBpWb0VumAfR52wFNzlrA/c//61nKypSkWi2h64SE=; fh=FYc1kiEE0oWkC6PFsL7NyqIq6QFuEUeU9nltPQzM5SI=; b=hIi/Rw5P/Xev63ZZlqbT8Nu8ylueZShtw7w3X6Z09bxYQNykyD43mr8T/jSEMOX/go mlf/oCDfrUytTSf1cMU1J5MhzyM1IuLg7tifznoLQ5aXcEmDatX9IZ+uPC0YoXAMM9No 6hMVoUNvOg8zkvQho9REUB/toj5/St8w410rVz8b1peePH+AmutmUImFl/vjYfqwdc6y fLAMuHX0knXZP2EKLwi6ZE2Ve82HRHfapUk0fLQ2Utg2aWgC/Q50XBbKh8b7jiyqwnEh DQhil7hnHvGi3uk67kM+oA47HdnfkYx4lzNYotE+FlcabAAHvEUX7uKFxXMC9IRQnpJT SFqQ==; dara=google.com ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of ron(a)ronaldbarnes.ca designates 144.217.187.82 as permitted sender) smtp.mailfrom=ron(a)ronaldbarnes.ca; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=ronaldbarnes.ca Return-Path: <ron(a)ronaldbarnes.ca> Received: from mail.ronaldbarnes.ca (mail.ronaldbarnes.ca. [144.217.187.82]) by mx.google.com with ESMTPS id af79cd13be357-7a9a7a53444si509352385a.539.2024.09.09.03.47.51 for <michael.paoli(a)berkeley.edu> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Sep 2024 03:47:51 -0700 (PDT) Received-SPF: pass (google.com: domain of ron(a)ronaldbarnes.ca designates 144.217.187.82 as permitted sender) client-ip=144.217.187.82; Authentication-Results: mx.google.com; spf=pass (google.com: domain of ron(a)ronaldbarnes.ca designates 144.217.187.82 as permitted sender) smtp.mailfrom=ron(a)ronaldbarnes.ca; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=ronaldbarnes.ca Received: from [10.60.42.104] (69-172-190-161.cable.teksavvy.com [69.172.190.161]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.ronaldbarnes.ca (Postfix) with ESMTPSA id C94FA81C5E for <balug(a)ronaldbarnes.ca>; Mon, 9 Sep 2024 03:47:50 -0700 (PDT) Message-ID: <f5e9353b-1a90-49a3-9239-d9acd4787b39(a)ronaldbarnes.ca> Date: Mon, 9 Sep 2024 03:47:50 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Ronald Barnes <ron(a)ronaldbarnes.ca> Subject: Testing: mailing list aliases To: balug(a)ronaldbarnes.ca Content-Language: en-CA Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Spam: 1 X-Gm-Phishy: 0 On Mon, Sep 9, 2024 at 3:47 AM Ronald Barnes <ron(a)ronaldbarnes.ca> wrote: > > > (RESENT - cannot spell Berkeley at this late hour, BAlug, not SFlug) > > > > the sending to off-site ... yeah, that'd be a general no-no. > > I thought I'd do one last test before bed: > > I've set up a virtual_alias (virtual transport on postfix) to test this. > > > If I send to balug(a)ronaldbarnes.ca, that address is aliased to Michael, > balug-test(a)lists.balug.org, and my bclug.ca address. > > > Let's see what happens... can't hurt. > > > Let me know if this goes through. I imagine BerkelEy.edu would be the > most restrictive in accepting my goofy experiment. > > > rb

1 0

Re: test - ignore suggest putting a link to the archives in the footer?
by Ron / BCLUG 09 Sep '24

09 Sep '24

Michael Paoli via BALUG-Test wrote on 2024-09-08 14:31: > I do really want to keep the footer short, like 3 lines maximum, per > various best practices, etc. Alas, folks mostly tend to ignore what's > there anyway. For what it's worth, the MM3 mailing list has these 4 lines of footer (plus a "sent to ...@..."): _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to admin(a)bclug.ca Works okay, IMHO. Helps legibility when URLs are converted to hyperlinks by the MUA. Anyway, looks like you've been doing a real deep dive into MM3, so now I know who to ask when I have issues... Or when I'm asked questions, I can refer 'em to you. Ha. rb

2 1

test - ignore ($hyperkitty_url testing results from in footer when not archived (X-Archive: no))
by test-dllsepcqvxv2vr5idrgh＠balug.org 08 Sep '24

08 Sep '24

Yeah, if $hyperkitty_url is expanded, e.g. in footer when message isn't archived, e.g. header has: X-Archive: no then $hyperkitty_url is still substituted, e.g.: https://lists.balug.org/mailman3/hyperkitty/list/balug-test@lists.balug.org… Even though not archived and that URL gives 404 Not Found $ curl -s -I \ > 'https://lists.balug.org/mailman3/hyperkitty/list/balug-test@lists.balug.org…' | > head -n 1 | tr -d '\015' HTTP/1.1 404 Not Found $ So, it essentially gives the URL of where it would be archived if it were archived, even when it's not archived at all.

1 0

test - ignore (trigger digest send?)
by test-dllsepcqvxv2vr5idrgh＠balug.org 08 Sep '24

08 Sep '24

1725828607

1 0

test - ignore
by Michael Paoli 08 Sep '24

08 Sep '24

footer test ...

1 2

test - ignore (DMARC, etc.)
by test-dllsepcqvxv2vr5idrgh＠balug.org 01 Sep '24

01 Sep '24

test - ignore Subject: test - ignore (DMARC, etc.) From: test-dllsepcqvxv2vr5idrgh(a)balug.org 1725232485

1 0

test - ignore (DMARC, etc.)
by postmaster＠balug.org 01 Sep '24

01 Sep '24

test - ignore Subject: test - ignore (DMARC, etc.) From: postmaster(a)balug.org 1725232465

1 0

test - ignore (DMARC, etc.)
by Michael.Paoli＠cal.berkeley.edu 01 Sep '24

01 Sep '24

test - ignore Subject: test - ignore (DMARC, etc.) From: Michael.Paoli(a)cal.berkeley.edu 1725232431

1 0

test - ignore (DMARC, etc.)
by Michael.Paoli＠berkeley.edu 01 Sep '24

01 Sep '24

test - ignore Subject: test - ignore (DMARC, etc.) From: Michael.Paoli(a)berkeley.edu 1725232411

1 0

HyperKitty archiver (or web interface thereof) up ...
by Michael Paoli 31 Aug '24

31 Aug '24

So, looks like the web interface is back up again (reinstalled the mailman3-web python3-mailman-hyperkitty packages even though they were already installed, that seemed to suffice) ... but ... was that earlier message archived, and will this one be archived? On Sat, Aug 31, 2024 at 6:12 AM Michael Paoli via BALUG-Test <balug-test(a)lists.balug.org> wrote: > HyperKitty archiver (or web interface thereof) is down, > presumably a configuration issue/glitch and > presumably mail interface is fine and Django and remainder of web > interface looks okay.

1 2

HyperKitty archiver (or web interface thereof) down
by Michael Paoli 31 Aug '24

31 Aug '24

Did Debian 11 Bullseye --> 12 Bookworm upgrade HyperKitty archiver (or web interface thereof) is down, presumably a configuration issue/glitch and presumably mail interface is fine and Django and remainder of web interface looks okay.

1 0

Re: test - ignore - Debian Buster 10.13 --> 11.10 Bullseye
by Michael Paoli 25 Aug '24

25 Aug '24

And testing via SMTP from The Internet.

1 1

test - ignore - Debian Buster 10.13 --> 11.10 Bullseye
by Michael Paoli 25 Aug '24

25 Aug '24

test - ignore - Debian Buster 10.13 --> 11.10 Bullseye pre-reboot test (apt-get -y full-upgrade completed) # uptime; uname -a; ls -A1 /boot 13:21:59 up 4 days, 4:25, 2 users, load average: 0.13, 0.17, 0.28 Linux balug-sf-lug-v2.balug.org 4.19.0-27-amd64 #1 SMP Debian 4.19.316-1 (2024-06-25) x86_64 GNU/Linux System.map-4.19.0-27-amd64 System.map-5.10.0-32-amd64 boot config-4.19.0-27-amd64 config-5.10.0-32-amd64 grub initrd.img-4.19.0-27-amd64 initrd.img-5.10.0-32-amd64 lost+found vmlinuz-4.19.0-27-amd64 vmlinuz-5.10.0-32-amd64 #

1 4

Re: systemd unit file mod, nntp removal, ...
by Ron / BCLUG 25 Aug '24

25 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-23 05:29: > restarted the relevant service: > # systemctl stop mailman3-web.service > # systemctl start mailman3-web.service This reminded me - I've modified my unit files so that only one service needs be started - same for re-starting or stopping: Create a file at /etc/systemd/system/mailman3.service.d/override.conf with these contents: [Unit] Upholds = mailman3-web.service Before = mailman3-web.service Probably need a `systemctl daemon-reload` for systemd to read it. Now, starting mailman3.service will *also* start mailman3-web.service. Now, restarting mailman3.service will *also* restart mailman3-web.service. Now, stopping mailman3.service will *also* stop mailman3-web.service. Also, there's really no need for nntp bridging IMHO, but it's enabled by default. Which causes an extra entire Python interpreter to be loaded in to memory. Disable this via: /etc/mailman3/mailman.cfg [runner.nntp] start: no Save some RAM... I believe this nntp support will be removed from default settings in the future, since I called attention to it on MM3 mailing list. rb

2 1

test - ignore (post config change sanity check)
by test-dllsepcqvxv2vr5idrgh＠balug.org 25 Aug '24

25 Aug '24

1724551789

1 0

Fwd: And the crash and the issue and image attachment test - test - ignore
by Michael Paoli 23 Aug '24

23 Aug '24

Okay, good actually, that "failed", held for moderator approval, because, with attachment, too large. So, now, forwarded below, without attachment, and there's link in body if one wants to view the attachment. And here's at least part of the bounce bit that let me know it "failed": From: <balug-test-owner(a)lists.balug.org> Date: Thu, Aug 22, 2024 at 11:27 PM Subject: balug-test(a)lists.balug.org post from michael.paoli(a)berkeley.edu requires approval To: <balug-test-owner(a)lists.balug.org> As list administrator, your authorization is requested for the following mailing list posting: List: balug-test(a)lists.balug.org From: michael.paoli(a)berkeley.edu Subject: And the crash and the issue and image attachment test - test - ignore The message is being held because: The message is larger than the 40 KB maximum size At your convenience, visit your dashboard to approve or deny the request. ---------- Forwarded message --------- From: Michael Paoli <michael.paoli(a)berkeley.edu> Date: Thu, Aug 22, 2024 at 11:26 PM Subject: And the crash and the issue and image attachment test - test - ignore To: BALUG-Test <balug-test(a)lists.balug.org> So, All was working fine until ... There was crash(/lockup) ... see "attached" image (if it makes it through to list?). And ... if you really want to see that image and it's not (or no longer attached or not or no longer in the archive), I've also, at least temporarily located it here: https://www.balug.org/tmp.lists/crash.jpg That's from physical host "vicki", upon which sometimes the BALUG VM runs. It was running on there this past Tuesday (US/Pacific) evening, and then fairly late evening - a crash - relatively rare short of having a power glitch/outage (do have a moderate bit of those, don't have UPS, and when running on laptop (with battery that holds no charge), if I manage to accidentally pull/nuge wiggle cord connection out - it drops hard). Anyway, the image - that's photo I took of the console screen of the physical vicki host (powered on ye olde CRT - relatively rare I do that), and took picture from "smart" phone (and then trimmed excess bits out of the image ... also dropped the quality a bit to reduce image file size while not losing much, if anything in readability of the text on the screen). So, before that, all was working fine. After that all seems to be working fine except for the web interface to archives and such (postorius / hyperkitty). And thus far all my testing and troubleshooting and isolating, it actually looks like the Mailman 3 parts of it (all, or almost all) are working properly. The mail interface still appears to be working fine. The django portion of web interface works fine. But on the Apache server, the postorius portion (mostly*) fails ... however, when I did (most notably with strace) on the communication between the two, it appears postorius is responding perfectly fine with good content, yet somehow Apache has issues or doesn't get that content, and ends up giving a 500 error page. *mosty ... I did the other day, stumble across a bit that still works. List membership roster ... with cookie ... can't login now, but still having older valid authentication cookie, I'm able to load up that page fine: https://lists.balug.org/mailman3/postorius/lists/balug-test.lists.balug.org… ... well, it actually wants to download it, and downloads it fine with the correct data. So, yeah, odd, that bit of postorius works all the way through Apache and to client ... haven't, however, found other parts that make it through successfully like that while this issue is otherwise still present. And yes, did also do strace(1) data gathering on that too ... haven't yet isolated why that works and (most of the rest) doesn't - but may use significantly different interface/component(s) under the covers. Anyway, that's where things presently stand. Still working to (isolate and) fix the issue. Meantime, did also do some updates on the main page, notably: https://www.balug.org/#Lists So folks at least have a clue/information about that (and workarounds as feasible). I'm guestimating there's like maybe some lock or state file that didn't get properly cleared or reset, or some subtle corruption or the like - and something along those lines is what's causing the issue. Don't know for sure, but given circumstances, that seems possible/probable. Also possible (but perhaps not as likely) there was some subtle latent defect, as I'd not rebooted in some moderate while, and the (crash and) reboot exposed that issue, where it wasn't seen before that. But looking over the (re)boot history, that doesn't seem most probable. Let's see, peeking at that again ... (and times UTC / GMT0), let's see, the not quite latest (Aug 21 06:20) was the crash and subsequent boot, and at least all of quite a number immediately before that were regular normal reboots. And the one I did after that was another reboot just to see if that might happen to clear the issue/error (no luck on that). $ { who -H | head -n 1; who -r /var/log/wtmp | tac; } | head -n 20 NAME LINE TIME COMMENT run-level 5 Aug 21 08:57 run-level Aug 21 08:56 run-level 5 Aug 21 06:20 run-level 5 Aug 19 07:23 run-level Aug 19 07:22 run-level 5 Jul 30 15:13 run-level Jul 30 14:50 run-level 5 Jul 28 00:10 run-level 5 Jul 6 14:45 run-level 5 Jul 5 09:02 run-level Jul 5 09:01 run-level 5 Jul 5 03:31 run-level Jul 5 03:30 run-level 5 Jun 23 00:03 run-level 5 Jun 18 15:44 run-level 5 Jun 17 08:16 run-level 5 Jun 17 05:53 run-level 5 May 26 22:58 run-level 5 May 26 19:44

1 2

Fwd: [sf-lug] BALUG: meeting Tuesday 2024-08-20 Supporting Older Systems, etc. & other BALUG News: Mailman 2 --> Mailman 3 & other upgrades
by Michael Paoli 22 Aug '24

22 Aug '24

---------- Forwarded message --------- From: Michael Paoli <michael.paoli(a)berkeley.edu> Date: Wed, Aug 21, 2024 at 6:14 PM Subject: Re: [sf-lug] BALUG: meeting Tuesday 2024-08-20 Supporting Older Systems, etc. & other BALUG News: Mailman 2 --> Mailman 3 & other upgrades To: Ronald Barnes <ron(a)ronaldbarnes.ca> Cc: SF-LUG <sf-lug(a)linuxmafia.com> Ah, well, the Mailman 2 --> Mailman 3 migration was mostly going quite well ... until it wasn't. 8-O Bumped into a significant glitch yesterday evening, still haven't got that sorted out yet, but about to start looking into it again. Fair bit of detail on the balug-test(a)lists.balug.org list. And appears the mail interfaces are working, so can post (if otherwise permitted to), subscribe, unsubscribe, etc. via email, but fair bit of web interfaces isn't working currently. So, for the curious: at least in part, email interface: subscribe: balug-test-subscribe(a)lists.balug.org unsubscribe: balug-test-unsubscribe(a)lists.balug.org post: balug-test(a)lists.balug.org help: balug-test-request(a)lists.balug.org with Subject: (or body) of: help As for web, postorious/hyperkitty (archive, etc.) portion isn't working, but the Django portion is working. On Wed, Aug 21, 2024 at 5:26 PM Ronald Barnes <ron(a)ronaldbarnes.ca> wrote: > > Michael Paoli wrote on 2024-08-15 22:04: > > > Mailman 2 --> Mailman 3 > > Oops, went out for bike ride, forgot about meeting. > > Was interested in this topic especially.

1 0

Re: "Oops" ... lists web interface issues ...
by Michael Paoli 21 Aug '24

21 Aug '24

Well ... getting closer ... So, Apache communicates with srwxr-xr-x 1 www-data www-data 0 Aug 21 08:56 /run/mailman3-web/uwsgi.sock and apparently writes that socket fine, but when reading it ... HTTP/1.1 500 Internal Server Error So, looks like somehow some kind of error between there and postorius. Looks like postorius is successfully writing lots of: HTTP/1.0 200 OK responses ... but (presumably) those somehow aren't making it to Apache? On Wed, Aug 21, 2024 at 3:50 AM Michael Paoli via BALUG-Test <balug-test(a)lists.balug.org> wrote: > > > > > ---------- Forwarded message ---------- > From: Michael Paoli <michael.paoli(a)berkeley.edu> > To: BALUG-Test <balug-test(a)lists.balug.org> > Cc: > Bcc: > Date: Wed, 21 Aug 2024 03:50:08 -0700 > Subject: [BALUG-Test] Re: "Oops" ... lists down for a bit (back by the time you see this?) > Well ... at least that's good - looks like the mail part is probably > working fine. > I thought for a bit it wasn't with one quick test I ran ... but I may > not have been > patient enough with that or may have not done that test quite right. > So, looks like just web/postorius interface I need to get working again. > And by the way, the Django administration interface appears to be fine, > so looks like issue is limited to postorius, and between postorius and Apache. > > So at least in theory, subscribe/unsubscribe via email should also be > working fine too. > > On Wed, Aug 21, 2024 at 3:43 AM Michael Paoli via BALUG-Test > <balug-test(a)lists.balug.org> wrote: > > > > > > > > > > ---------- Forwarded message ---------- > > From: Michael Paoli <michael.paoli(a)berkeley.edu> > > To: BALUG-Test <balug-test(a)lists.balug.org> > > Cc: > > Bcc: > > Date: Wed, 21 Aug 2024 03:42:38 -0700 > > Subject: [BALUG-Test] "Oops" ... lists down for a bit (back by the time you see this?) > > "Oops" ... lists down for a bit. > > Drats ... and hopefully all better by the time this mail makes it to list. > > > > So ... all was fine and dandy until ... > > managed to have a host booboo, > > basically locked up solid, and I power cycled it > > (this was physical host upon which the VM was running). > > Shouldn't be any biggie ... after that all up and fine again ... > > except the Mailman 3 lists. > > > > So, ... isolating and working towards fixing that. > > I'm guestimating maybe issue with some kind of lock file or > > the like that didn't get cleaned up upon (re)boot, > > or possibly, since I perhaps didn't do as many reboots as I ought > > to have made sure it would "always" come up clean, perhaps there was > > some misconfiguration or the like that somehow snuck in, that would be > > effectively a latent defect/issue, and that wouldn't show until a reboot or > > attempted restart of the relevant service(s). > > > > At this point still troubleshooting to narrow down the issue. > > > > As far as I can tell so far, looks like web server hits some kind of issue > > and generally gives or passes along a 500 response, that then ends up > > with the relevant web page(s) failing. When I did deeper into the > > backend service(s) ... notably postorius, looks like it gets requests okay > > and responds to them okay ... but something goes wrong somewhere > > between there and web server properly getting and passing that > > along to client browser. > > E.g.: > > https://lists.balug.org/mailman3/postorius/lists/ > > I see in postorius bit returning (from strace(1)) including: > > {\"display_name\": \"BALUG-Admin\", \"fqdn_listname\": > > \"balug-admin(a)lists.balug.org\", > > {\"display_name\": \"BALUG-Announce\", \"fqdn_listname\": > > \"balug-announce(a)lists.balug.org\", > > {\"display_name\": \"BALUG-Talk\", \"fqdn_listname\": > > \"balug-talk(a)lists.balug.org\", > > {\"display_name\": \"BALUG-Test\", \"fqdn_listname\": > > \"balug-test(a)lists.balug.org\", > > But somehow that doesn't make it to the web page the server serves ... so I'm > > guestimating there's some issue somewhere between postorius and Apache. > > > > > > ---------- Forwarded message ---------- > > From: Michael Paoli via BALUG-Test <balug-test(a)lists.balug.org> > > To: BALUG-Test <balug-test(a)lists.balug.org> > > Cc: > > Bcc: > > Date: Wed, 21 Aug 2024 03:42:38 -0700 > > Subject: [BALUG-Test] "Oops" ... lists down for a bit (back by the time you see this?) > > _______________________________________________ > > BALUG-Test mailing list -- balug-test(a)lists.balug.org > > To unsubscribe send an email to balug-test-leave(a)lists.balug.org > > > ---------- Forwarded message ---------- > From: Michael Paoli via BALUG-Test <balug-test(a)lists.balug.org> > To: BALUG-Test <balug-test(a)lists.balug.org> > Cc: > Bcc: > Date: Wed, 21 Aug 2024 03:50:08 -0700 > Subject: [BALUG-Test] Re: "Oops" ... lists down for a bit (back by the time you see this?) > _______________________________________________ > BALUG-Test mailing list -- balug-test(a)lists.balug.org > To unsubscribe send an email to balug-test-leave(a)lists.balug.org

1 0

Re: "Oops" ... lists down for a bit (back by the time you see this?)
by Michael Paoli 21 Aug '24

21 Aug '24

Well ... at least that's good - looks like the mail part is probably working fine. I thought for a bit it wasn't with one quick test I ran ... but I may not have been patient enough with that or may have not done that test quite right. So, looks like just web/postorius interface I need to get working again. And by the way, the Django administration interface appears to be fine, so looks like issue is limited to postorius, and between postorius and Apache. So at least in theory, subscribe/unsubscribe via email should also be working fine too. On Wed, Aug 21, 2024 at 3:43 AM Michael Paoli via BALUG-Test <balug-test(a)lists.balug.org> wrote: > > > > > ---------- Forwarded message ---------- > From: Michael Paoli <michael.paoli(a)berkeley.edu> > To: BALUG-Test <balug-test(a)lists.balug.org> > Cc: > Bcc: > Date: Wed, 21 Aug 2024 03:42:38 -0700 > Subject: [BALUG-Test] "Oops" ... lists down for a bit (back by the time you see this?) > "Oops" ... lists down for a bit. > Drats ... and hopefully all better by the time this mail makes it to list. > > So ... all was fine and dandy until ... > managed to have a host booboo, > basically locked up solid, and I power cycled it > (this was physical host upon which the VM was running). > Shouldn't be any biggie ... after that all up and fine again ... > except the Mailman 3 lists. > > So, ... isolating and working towards fixing that. > I'm guestimating maybe issue with some kind of lock file or > the like that didn't get cleaned up upon (re)boot, > or possibly, since I perhaps didn't do as many reboots as I ought > to have made sure it would "always" come up clean, perhaps there was > some misconfiguration or the like that somehow snuck in, that would be > effectively a latent defect/issue, and that wouldn't show until a reboot or > attempted restart of the relevant service(s). > > At this point still troubleshooting to narrow down the issue. > > As far as I can tell so far, looks like web server hits some kind of issue > and generally gives or passes along a 500 response, that then ends up > with the relevant web page(s) failing. When I did deeper into the > backend service(s) ... notably postorius, looks like it gets requests okay > and responds to them okay ... but something goes wrong somewhere > between there and web server properly getting and passing that > along to client browser. > E.g.: > https://lists.balug.org/mailman3/postorius/lists/ > I see in postorius bit returning (from strace(1)) including: > {\"display_name\": \"BALUG-Admin\", \"fqdn_listname\": > \"balug-admin(a)lists.balug.org\", > {\"display_name\": \"BALUG-Announce\", \"fqdn_listname\": > \"balug-announce(a)lists.balug.org\", > {\"display_name\": \"BALUG-Talk\", \"fqdn_listname\": > \"balug-talk(a)lists.balug.org\", > {\"display_name\": \"BALUG-Test\", \"fqdn_listname\": > \"balug-test(a)lists.balug.org\", > But somehow that doesn't make it to the web page the server serves ... so I'm > guestimating there's some issue somewhere between postorius and Apache. > > > ---------- Forwarded message ---------- > From: Michael Paoli via BALUG-Test <balug-test(a)lists.balug.org> > To: BALUG-Test <balug-test(a)lists.balug.org> > Cc: > Bcc: > Date: Wed, 21 Aug 2024 03:42:38 -0700 > Subject: [BALUG-Test] "Oops" ... lists down for a bit (back by the time you see this?) > _______________________________________________ > BALUG-Test mailing list -- balug-test(a)lists.balug.org > To unsubscribe send an email to balug-test-leave(a)lists.balug.org

1 0

"Oops" ... lists down for a bit (back by the time you see this?)
by Michael Paoli 21 Aug '24

21 Aug '24

"Oops" ... lists down for a bit. Drats ... and hopefully all better by the time this mail makes it to list. So ... all was fine and dandy until ... managed to have a host booboo, basically locked up solid, and I power cycled it (this was physical host upon which the VM was running). Shouldn't be any biggie ... after that all up and fine again ... except the Mailman 3 lists. So, ... isolating and working towards fixing that. I'm guestimating maybe issue with some kind of lock file or the like that didn't get cleaned up upon (re)boot, or possibly, since I perhaps didn't do as many reboots as I ought to have made sure it would "always" come up clean, perhaps there was some misconfiguration or the like that somehow snuck in, that would be effectively a latent defect/issue, and that wouldn't show until a reboot or attempted restart of the relevant service(s). At this point still troubleshooting to narrow down the issue. As far as I can tell so far, looks like web server hits some kind of issue and generally gives or passes along a 500 response, that then ends up with the relevant web page(s) failing. When I did deeper into the backend service(s) ... notably postorius, looks like it gets requests okay and responds to them okay ... but something goes wrong somewhere between there and web server properly getting and passing that along to client browser. E.g.: https://lists.balug.org/mailman3/postorius/lists/ I see in postorius bit returning (from strace(1)) including: {\"display_name\": \"BALUG-Admin\", \"fqdn_listname\": \"balug-admin(a)lists.balug.org\", {\"display_name\": \"BALUG-Announce\", \"fqdn_listname\": \"balug-announce(a)lists.balug.org\", {\"display_name\": \"BALUG-Talk\", \"fqdn_listname\": \"balug-talk(a)lists.balug.org\", {\"display_name\": \"BALUG-Test\", \"fqdn_listname\": \"balug-test(a)lists.balug.org\", But somehow that doesn't make it to the web page the server serves ... so I'm guestimating there's some issue somewhere between postorius and Apache.

1 0

balug-test3@lists.balug.org --> balug-test@lists.balug.org
by Michael Paoli 20 Aug '24

20 Aug '24

The archives of balug-test3(a)lists.balug.org have been merged into those of balug-test(a)lists.balug.org and the balug-test3(a)lists.balug.org list has been removed.

1 0

test - ignore - db timezone testing
by Michael Paoli 20 Aug '24

20 Aug '24

db timezone testing 2024-08-20T10:15:15+00:00 Tue, 20 Aug 2024 10:15:15 +0000 Tue Aug 20 10:15:15 2024 2024-08-20T03:15:15-07:00 Tue, 20 Aug 2024 03:15:15 -0700 Tue Aug 20 03:15:15 2024

1 1

test - ignore db timezone testing
by Michael Paoli 20 Aug '24

20 Aug '24

db timezone testing 2024-08-20T10:15:15+00:00 Tue, 20 Aug 2024 10:15:15 +0000 Tue Aug 20 10:15:15 2024 2024-08-20T03:15:15-07:00 Tue, 20 Aug 2024 03:15:15 -0700 Tue Aug 20 03:15:15 2024

1 0

test - ignore Check database timezone behavior
by Michael Paoli 20 Aug '24

20 Aug '24

Check database timezone behavior 2024-08-20T09:35:01+00:00 Tue, 20 Aug 2024 09:35:01 +0000 Tue Aug 20 09:35:01 2024 2024-08-20T02:35:01-07:00 Tue, 20 Aug 2024 02:35:01 -0700 Tue Aug 20 02:35:01 2024

2 1

test - ignore Check database timezone behavior
by Michael Paoli 20 Aug '24

20 Aug '24

Check database timezone behavior 2024-08-20T09:35:01+00:00 Tue, 20 Aug 2024 09:35:01 +0000 Tue Aug 20 09:35:01 2024 2024-08-20T02:35:01-07:00 Tue, 20 Aug 2024 02:35:01 -0700 Tue Aug 20 02:35:01 2024

1 0

gravatar.com leakage
by Michael Paoli 19 Aug '24

19 Aug '24

Yeah, I notice at least by default on at least the Mailman 3 hyperkitty archive, it "leaks" information to gravatar.com using per-member URLs for images from gravatar.com ... ugh. Yeah, looks like I'm not the first to notice this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Anyway, one more item to add to migration checklist of things to do, and from the above, looks like it's probably not too difficult to manage to do. Michael Paoli wrote: > Mailman 2 --> Mailman 3 ... largely (but not entirely) done; holler if > one notes any issues. > > Summary on status/progres can be found here: > https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_... > > There were some glitches, notably with import21 ... > and did find a work-around(/fix?) for that, > and also had some issues with archive import+indexing, > but seem to have made it past all that now (though still have > some more validation checks to do, etc.). > > And note that thus far, the merging of archive from the > (temporary) balug-test3(a)lists.balug.org to > balug-test(a)lists.balug.org is still pending. > In the meantime, those archives are available here: > https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.... > And the balug-test3(a)lists.balug.org is also mostly locked down > to prevent changes (no new postings or subscription/membership changes).

1 0

Mailman 2 --> Mailman 3 ... largely (but not entirely) done; holler if one notes any issues.
by Michael Paoli 19 Aug '24

19 Aug '24

Mailman 2 --> Mailman 3 ... largely (but not entirely) done; holler if one notes any issues. Summary on status/progres can be found here: https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_3_… There were some glitches, notably with import21 ... and did find a work-around(/fix?) for that, and also had some issues with archive import+indexing, but seem to have made it past all that now (though still have some more validation checks to do, etc.). And note that thus far, the merging of archive from the (temporary) balug-test3(a)lists.balug.org to balug-test(a)lists.balug.org is still pending. In the meantime, those archives are available here: https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.or… And the balug-test3(a)lists.balug.org is also mostly locked down to prevent changes (no new postings or subscription/membership changes).

1 0

Re: Rats ... some hyperkitty_import issue(s) ...
by admin＠bclug.ca 19 Aug '24

19 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-18 01:34: > So, seems it accepted and indexed them ... but for some reason isn't > yet showing them in hyperkitty - though it lets me download them > from the archive. You've probably tried this already, but: mailman-web update_index -h or mailman-web update_index_one_list -h rb

2 1

Re: And so it begins (well, only one teeny oops so far) Re: Welcome to the "BALUG-Test" mailing list
by admin＠bclug.ca 18 Aug '24

18 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-18 01:30: > Just using the Debian packages. I think they include the venv setup, > but haven't poked into the details to see exactly how they function in > that regard. There should be approaching *zero* Debian packages installed! From my brain-addled notes: ## Use PG, not MySQL! Change next line per venv instructions online: apt install default-libmysqlclient-dev build-essential ## More Debian package(s): sudo apt install libpcre3 libpcre3-dev Various notes follow, the TL;DR is above regarding which repo packages to install. Everything gets installed inside a venv with pip! sudo useradd --create-home \ --home-dir /opt/mailman \ --shell /bin/bash \ mailman sudo chown -v mailman: /opt/mailman sudo chmod -v 755 /opt/mailman sudo -i -u mailman bash -c "python3 -m venv venv; echo 'source /opt/mailman/venv/bin/activate' >> /opt/mailman/.bashrc; exit" sudo -i -u mailman bash -c "pip install wheel mailman PyMySQL" ## Run as sudo: mkdir /etc/mailman3 touch /etc/mailman3/mailman3.service touch /etc/mailman3/mailman-hyperkitty.cfg ## This is about the only Debian / Ubuntu packages to install: ## And, screw messing with MySQL, PostgreSQL all the way: apt update ## Use PG, not MySQL, change next line per venv instructions online: apt install default-libmysqlclient-dev build-essential ## Is this run as mailman? I *think* so, inside the venv: pip install mailman-web mailman-hyperkitty ## As user mailman inside venv: MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web migrate MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web collectstatic MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web compress MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web compressmessages pip install uwsgi ## create & edit /etc/mailman3/uwsgi.ini: ## You can run test run uwsgi using the following command: ## ## (venv)$ uwsgi --ini /etc/mailman3/uwsgi.ini uwsgi --ini /etc/mailman3/uwsgi.ini ## NOTE: if /opt/mailman/web/logs/uwsgi-error.log (?) has this: ## !!! no internal routing support, rebuild with pcre support !!! ## then... ## pip uninstall uwsgi ## More Debian package(s): sudo apt install libpcre3 libpcre3-dev pip install --force-reinstall -U --no-deps --no-cache-dir uwsgi Next and last: Xapian full-text search. ## Xapian full-text search ################################### ## Xapian full-text search ################################### ## Xapian full-text search ################################### ## ## Latest version: 1.4.25 ## Inside (venv) as mailman: export XAPIAN_VERSION="1.4.25" mkdir /tmp/mailman/xapian -vp cd /tmp/mailman/xapian curl https://raw.githubusercontent.com/notanumber/xapian-haystack/master/xapian_w> bash xapian_wheel_builder.sh $XAPIAN_VERSION ls -l *.whl wheelFile=$(ls *.whl) pip install ${wheelFile} xapian-haystack unset wheelFile rm -fr /tmp/mailman/xapian > /dev/null echo "Edit /etc/mailman3/settings_local.py and add HAYSTACK_CONNECTIONS" ## DO NOT OVERLOOK XAPIAN-HAYSTACK IN LINES ABOVE!!! ## DO NOT OVERLOOK XAPIAN-HAYSTACK IN LINES ABOVE!!! ## DO NOT OVERLOOK XAPIAN-HAYSTACK IN LINES ABOVE!!!

1 0

Re: Rats ... some hyperkitty_import issue(s) ...
by admin＠bclug.ca 18 Aug '24

18 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-18 00:04: > Rats ... some hyperkitty_import issue(s) ... imports some emails > perfectly fine, others it just quietly fails to import. Sounds like you're getting really close! I do see something running `mailman-web help hyperkitty_import` about another cleanup tool: > Before running this, the mbox(es) should be checked for messages that > could throw uncaught exceptions with the contrib/check_hk_archive > script and for unescaped 'From ' lines with Mailman 2.1's cleanarch > script. > Oh well, ye olde "divide and conquer" - shouldn't be too hard to > figure out what's tripping it up. I figure you'll have it figured out before this gets sent. Good luck, rb

2 1

Re: And so it begins (well, only one teeny oops so far) Re: Welcome to the "BALUG-Test" mailing list
by admin＠bclug.ca 18 Aug '24

18 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-17 22:41: > For the curious, there's also: > https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_3_… Nice documentation. At a quick glance, did you forego the 'venv' method and go with packages from repo? Word of warning, it's not supported and anyone with issues is sent to Debian (etc.) for support on the MM3-users mailing list. The 'venv' method is *strongly* advised. rb

2 1

Rats ... some hyperkitty_import issue(s) ...
by Michael Paoli 18 Aug '24

18 Aug '24

Rats ... some hyperkitty_import issue(s) ... imports some emails perfectly fine, others it just quietly fails to import. Oh well, ye olde "divide and conquer" - shouldn't be too hard to figure out what's tripping it up.

1 0

And so it begins (well, only one teeny oops so far) Re: Welcome to the "BALUG-Test" mailing list
by Michael Paoli 18 Aug '24

18 Aug '24

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.html https://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.

1 0

test post
by KLH IC 31 Jul '24

31 Jul '24

Thank you for the invite. Is this just an internally focused test of internal mail?

1 0

Re: test - ignore (post, archive, delete, reimport)
by admin＠bclug.ca 26 Jul '24

26 Jul '24

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

2 1

Re: test - ignore (post, archive, delete, reimport)
by admin＠bclug.ca 19 Jul '24

19 Jul '24

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

2 1

test - ignore (post, archive, delete, reimport)
by test-trnzipzntiaotvhgjmee＠balug.org 18 Jul '24

18 Jul '24

1721289353

2 1

Initial BALUG-Test3 posting
by aaronco thirtysix 18 Jul '24

18 Jul '24

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

2 1

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 17 Jul '24

17 Jul '24

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

2 2

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721072500 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721068560 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721068505 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721034204 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721029362 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721028029 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721016870 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive testing
by test-trnzipzntiaotvhgjmee＠balug.org 15 Jul '24

15 Jul '24

body 1721004487 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive import testing
by test-trnzipzntiaotvhgjmee＠balug.org 09 Jul '24

09 Jul '24

body 1720513097 postmaster(a)example.com @example.com last line of body

1 0

test - ignore - archive import testing
by test-trnzipzntiaotvhgjmee＠balug.org 09 Jul '24

09 Jul '24

body archive 1720508844

1 0

test - ignore - archive import testing
by test-trnzipzntiaotvhgjmee＠balug.org 09 Jul '24

09 Jul '24

body archive 1720508695

1 0

test - ignore - @ munge testing
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

So, body @ (a) munging, unmunged in original mail, displays on web GUI: munged: postmaster(a)[127.0.0.1] postmaster(a)example.com unmunged: <postmaster@localhost> @example.com @localhost postmaster@localhost Posted unmunged from GUI, exact same as above. And in the archive itself ugh, slightly worse, but not even the same set!: munged: <postmaster(a)localhost> postmaster(a)example.com postmaster(a)localhost unmunged: @example.com @localhost postmaster(a)[127.0.0.1] Posted unmunged from GUI, exact same as above. And note that @ (a) munging is applied to body, not headers. And I don't think Mailman 3 has an option to turn off munging.

1 0

test - ignore - @ munge testing from mail
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

So, unmunged in original mail, displays on web GUI: munged: postmaster(a)[127.0.0.1] postmaster(a)example.com unmunged: <postmaster@localhost> @example.com @localhost postmaster@localhost And in the arhive itself ugh, slightly worse, but not even the same set!: munged: <postmaster(a)localhost> postmaster(a)example.com postmaster(a)localhost unmunged: @example.com @localhost postmaster(a)[127.0.0.1] In any case, that applies to body, headers in archive aren't @ (a) munged.

2 1

test - ignore - @ munge testing from mail
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

postmaster@localhost <postmaster@localhost> postmaster(a)example.com postmaster(a)[127.0.0.1] @localhost @example.com

1 0

Re: [sf-lug] Mailman 3 testing (@lists.BALUG.org) ...
by Ron 07 Jul '24

07 Jul '24

On 2024-07-07 03:15, Michael Paoli wrote: > Mailman 3 testing (@lists.BALUG.org) ... > > For the interested and/or curious, That's me! > actively testing Mailman 3 at present > (so far looking at least "reasonable enough", and does have some pretty > spiffy features too). If curious and/or want to try it out, > have a peek here: > https://lists.balug.org/mailman3/ It does look nice, for sure. I'm subscribed (via email to ...-request@...), however, when I go to the web page and try to log in, I get: > Server error > > An error occurred while processing your request. I'd expect a different result (I do not yet have an account via the web interface).

2 1

test - ignore ... munging behavior?
by Michael Paoli 07 Jul '24

07 Jul '24

So, if we post from the web interface, how does address munging behave? And both for display via web interface, and in archive? Posting as unmunged to see how it ends up: postmaster(a)[127.0.0.1] postmaster@localhost <postmaster@localhost> @localhost @example.com postmaster(a)example.com What about when we use Quote button to include the earlier?

1 1

test - ignore testing archive headers conflicting: X-Archive: X-Archive: no
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers conflicting: X-Archive: foobar X-Archive: no
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: foobar
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: YeSx
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: xYeS
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: YeS
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: YES
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers conflicting: X-Archive: yes X-Archive: no
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: yes
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: xno
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers X-Archive: nox
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

test - ignore testing archive headers
by test-trnzipzntiaotvhgjmee＠balug.org 07 Jul '24

07 Jul '24

body...

1 0

DMARC mitigation
by Michael Paoli 06 Jul '24

06 Jul '24

Mailman 3 options and results: DMARC mitigation action: Wrap the message in an outer message From: the list. DMARC Mitigate unconditionally: No DMARC rejection notice: DMARC wrapped message text: From: Michael Paoli via BALUG-test3 <balug-test3(a)lists.balug.org> Reply-To: Michael Paoli <[localpart](a)yahoo.com> DMARC mitigation action: Reject the message DMARC Mitigate unconditionally: Yes DMARC rejection notice: Testing DMARC rejection DMARC wrapped message text: DMARC wrapped message text: headers may be munged (no munging when posted from @linuxmafia.com) posting from @yahoo.com bounces: Your message to the BALUG-test3 mailing-list was rejected for the following reasons: Testing DMARC rejection DMARC mitigation action: Reject the message DMARC Mitigate unconditionally: No DMARC rejection notice: Testing DMARC rejection DMARC wrapped message text: DMARC wrapped message text: headers may be munged posting from @yahoo.com bounces: Your message to the BALUG-test3 mailing-list was rejected for the following reasons: Testing DMARC rejection DMARC mitigation action: Wrap the message in an outer message From: the list. DMARC Mitigate unconditionally: No DMARC rejection notice: Rejected due to DMARC. DMARC wrapped message text: Because of DMARC, headers may be munged posting from @yahoo.com: adds a first MIME section that has: Because of DMARC, headers may be munged From: Michael Paoli via BALUG-test3 <balug-test3(a)lists.balug.org> Reply-To: Michael Paoli <[localpart](a)yahoo.com> DMARC mitigation action: Reject the message. DMARC Mitigate unconditionally: Yes DMARC rejection notice: DMARC wrapped message text: posting from @yahoo.com: our message to the BALUG-test3 mailing-list was rejected for the following reasons: You are not allowed to post to this mailing list From: a domain which publishes a DMARC policy of reject or quarantine, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at balug-test3-owner(a)lists.balug.org. Anyway, given the potentially non-ideal situation with DMARC, this seems best compromise: DMARC mitigation action: Wrap the message in an outer message From: the list. DMARC Mitigate unconditionally: No DMARC rejection notice: DMARC wrapped message text: And hyperkitty has at least some display/munging issues: greater than symbol on at least end of email address shows as as apersand gt semicolon at symbol in at least email address show as (a)

1 0

yet more DMARC testing ...
by Michael Paoli 06 Jul '24

06 Jul '24

yes, more, still

1 0

DKIM/DMARC Testing
by Michael Paoli 06 Jul '24

06 Jul '24

DKIM/DMARC Testing

1 0

DMARC/DKIM? (with workaround(s) in place/)
by Michael Paoli 06 Jul '24

06 Jul '24

DMARC/DKIM? (with workaround(s) in place/)

2 1

test - ignore 2024-07-05T22:43:48+00:00
by Michael Paoli 05 Jul '24

05 Jul '24

test - ignore 2024-07-05T22:43:48+00:00

1 0

Re: Mailman3 testing (Michael Paoli)
by Michael Paoli 05 Jul '24

05 Jul '24

Yay, looks like I got the archives working: https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.or… On Fri, Jul 5, 2024 at 2:53 PM Michael Paoli <michael.paoli(a)berkeley.edu> wrote: > > 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(a)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(a)berkeley.edu> > > > To: BALUG-test <balug-test(a)lists.balug.org> > > > Subject: Re: [BALUG-Test] Mailman3 testing > > > Message-ID: > > > <CAPU_E+ds6dcKZm8rUU_gw8R9OEh5FP-7pMCRKtYhthvoJK3JgQ(a)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(a)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(a)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(a)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(a)lists.balug.org > > >> balug-test3-unsubscribe(a)lists.balug.org > > >> balug-test3-request(a)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.

1 0

test - ignore 2024-07-05T22:18:57+00:00
by Michael Paoli 05 Jul '24

05 Jul '24

test - ignore 2024-07-05T22:18:57+00:00

1 0

Re: Mailman3 testing (Michael Paoli)
by Michael Paoli 05 Jul '24

05 Jul '24

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(a)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(a)berkeley.edu> > > To: BALUG-test <balug-test(a)lists.balug.org> > > Subject: Re: [BALUG-Test] Mailman3 testing > > Message-ID: > > <CAPU_E+ds6dcKZm8rUU_gw8R9OEh5FP-7pMCRKtYhthvoJK3JgQ(a)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(a)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(a)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(a)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(a)lists.balug.org > >> balug-test3-unsubscribe(a)lists.balug.org > >> balug-test3-request(a)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.

1 0

test - ignore 2024-07-05T09:03:25+00:00
by Michael Paoli 05 Jul '24

05 Jul '24

test - ignore 2024-07-05T09:03:25+00:00

1 0

test - ignore 2024-07-05T08:56:15+00:00
by Michael Paoli 05 Jul '24

05 Jul '24

test - ignore 2024-07-05T08:56:15+00:00

1 0

test - ignore ... archives, bit closer ...
by Michael Paoli 05 Jul '24

05 Jul '24

# tail -n 2 /var/log/mailman3/mailman.log Jul 05 08:34:57 2024 (1375) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) #

1 0

test - ignore 2024-07-05T08:34:55+00:00
by Michael Paoli 05 Jul '24

05 Jul '24

test - ignore 2024-07-05T08:34:55+00:00

1 0

test - ignore - got archives?
by Michael Paoli 05 Jul '24

05 Jul '24

test - ignore got archives?

1 0

archive ... not working quite yet
by Michael Paoli 05 Jul '24

05 Jul '24

archive ... not working quite yet ... not until after I fix: $ curl -I http://localhost/mailman3/hyperkitty/ HTTP/1.1 302 Found Date: Fri, 05 Jul 2024 06:18:33 GMT Server: Apache/2.4.59 (Debian) Location: http://www.balug.org/mailman3/hyperkitty/ Content-Type: text/html; charset=iso-8859-1 $

1 0

test - ignore
by Michael Paoli 05 Jul '24

05 Jul '24

got archive ... maybe?

1 0

test - ignore
by Michael Paoli 05 Jul '24

05 Jul '24

test - ignore

1 0

Mailman3 testing
by Michael Paoli 05 Jul '24

05 Jul '24

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(a)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(a)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(a)lists.balug.org balug-test3-unsubscribe(a)lists.balug.org balug-test3-request(a)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.

1 1

Re: Mailman3 testing
by Michael Paoli 05 Jul '24

05 Jul '24

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(a)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(a)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(a)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(a)lists.balug.org > balug-test3-unsubscribe(a)lists.balug.org > balug-test3-request(a)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.

1 0

test
by Michael Paoli 20 Jun '24

20 Jun '24

test

1 0

test
by Michael Paoli 20 Jun '24

20 Jun '24

test

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

BALUG-Test