Yeah, well, somewhere between about 2026-03-02 and 2026-03-16,
(not sure exactly how it started or got introduced) had an issue with
the list(s) and/or MTA that was impacting at least list(s).
Poked around a bit and got that straightened out and working again.
And yes, the earliest on the Test list around the end of that time
range that made
it through and to the archive, well, first of those would be first that made it
through after successful correction.
For the curious:
# date; pwd -P; rlog main.cf 2>&1 | sed -ne '/^revision 1\.5/,/03-02/p'
Wed Mar 18 05:46:17 UTC 2026
/etc/postfix
revision 1.5 locked by: root;
date: 2026/03/16 15:13:05; author: root; state: Exp; lines: +1 -0
+lmtp_host_lookup = native to avoid Host or domain name not found.
Name service error
for name=localhost type=AAAA: Host not found
----------------------------
revision 1.4
date: 2026/03/16 14:34:09; author: root; state: Exp; lines: +1 -1
-balug13 (apparently carried over unintentionally from a testing VM)
----------------------------
revision 1.3
date: 2026/02/28 21:58:44; author: root; state: Exp; lines: +30 -17
further adjustments for mailman, etc. - was working 2026-03-02(?)
#
rcsdiff -U 0 -r1.3 -r1.4 main.cf 2>>/dev/null
--- main.cf 2026/02/28 21:58:44 1.3
+++ main.cf 2026/03/16 14:34:09 1.4
@@ -95 +95 @@
-mydestination = $myhostname, localhost.$mydomain, localhost,
$myorigin, lists.balug.org, balug13
+mydestination = $myhostname, localhost.$mydomain, localhost,
$myorigin, lists.balug.org
# rcsdiff -U 0 -r1.4 -r1.5 main.cf 2>>/dev/null
--- main.cf 2026/03/16 14:34:09 1.4
+++ main.cf 2026/03/16 15:13:05 1.5
@@ -89,0 +90 @@
+lmtp_host_lookup = native
#
Also added to /etc/hosts:
# grep '^::1[ ]\{1,\}localhost$' /etc/hosts
::1 localhost
#
On Tue, Mar 17, 2026 at 8:40 PM aaronco thirtysix via BALUG-Test
<balug-test(a)lists.balug.org> wrote:
>
>
>
>
> ---------- Forwarded message ----------
> From: aaronco36(a)sdf.org
> To: balug-test(a)lists.balug.org
> Cc:
> Bcc:
> Date: Wed, 18 Mar 2026 03:40:02 -0000
> Subject: [BALUG-Test] Re: BALUG-Test Digest, Vol 20, Issue 2
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of BALUG-Test digest..."
> >
> > submissions: balug-test(a)lists.balug.org
> > unsubscribe: balug-test-unsubscribe(a)lists.balug.org
> > subscribe: balug-test-subscribe(a)lists.balug.org
> > help: https://lists.balug.org/help/
> > reach person(s) managing list: balug-test-owner(a)lists.balug.org
> >
> > Today's Topics:
> >
> > 1. test ignore 2026-03-16T15:13:21Z (Michael Paoli)
> >
>
> Test successfully ignored :-)
>
>
>
>
> ---------- Forwarded message ----------
> From: aaronco thirtysix via BALUG-Test <balug-test(a)lists.balug.org>
> To: balug-test(a)lists.balug.org
> Cc:
> Bcc:
> Date: Wed, 18 Mar 2026 03:40:02 -0000
> Subject: [BALUG-Test] Re: BALUG-Test Digest, Vol 20, Issue 2
> _______________________________________________
> list: BALUG-Test(a)lists.balug.org help: https://lists.balug.org/help/
> unsubscribe email: balug-test-unsubscribe(a)lists.balug.org
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of BALUG-Test digest..."
>
> submissions: balug-test(a)lists.balug.org
> unsubscribe: balug-test-unsubscribe(a)lists.balug.org
> subscribe: balug-test-subscribe(a)lists.balug.org
> help: https://lists.balug.org/help/
> reach person(s) managing list: balug-test-owner(a)lists.balug.org
>
> Today's Topics:
>
> 1. test ignore 2026-03-16T15:13:21Z (Michael Paoli)
>
Test successfully ignored :-)
But wait, there's more you also get ...
$ hostname; date --iso-8601=seconds; (for IP in 10.1.10.109
96.86.170.229 2001:470:1f04:19e::2 2001:470:1f05:19e::2
2001:470:1f05:19e::3 2001:470:1f05:19e::4 2001:470:1f05:19e::5
2001:470:1f05:19e::6 2001:470:1f05:19e::7 2001:470:1f05:19e::8
2001:470:1f05:19e::9 2001:470:1f05:19e::a
2603:3024:1b29:0:5054:ff:fe13:5199 2603:3024:1b29:2::2
2603:3024:1b29:2::3 2603:3024:1b29:2::4 2603:3024:1b29:2::5
2603:3024:1b29:2::6 2603:3024:1b29:2::7 2603:3024:1b29:2::8
2603:3024:1b29:2::9 2603:3024:1b29:2::a; do echo "$IP" $(dig
@ns1.google.com. -b "$IP" +short o-o.myaddr.l.google.com. TXT | tr -d
'"'); done)
balug-sf-lug-v2.balug.org
2026-03-01T22:28:53+00:00
10.1.10.109 96.86.170.230
96.86.170.229 96.86.170.229
2001:470:1f04:19e::2 2001:470:1f04:19e::2
2001:470:1f05:19e::2 2001:470:1f05:19e::2
2001:470:1f05:19e::3 2001:470:1f05:19e::3
2001:470:1f05:19e::4 2001:470:1f05:19e::4
2001:470:1f05:19e::5 2001:470:1f05:19e::5
2001:470:1f05:19e::6 2001:470:1f05:19e::6
2001:470:1f05:19e::7 2001:470:1f05:19e::7
2001:470:1f05:19e::8 2001:470:1f05:19e::8
2001:470:1f05:19e::9 2001:470:1f05:19e::9
2001:470:1f05:19e::a 2001:470:1f05:19e::a
2603:3024:1b29:0:5054:ff:fe13:5199 2603:3024:1b29:0:5054:ff:fe13:5199
2603:3024:1b29:2::2 2603:3024:1b29:2::2
2603:3024:1b29:2::3 2603:3024:1b29:2::3
2603:3024:1b29:2::4 2603:3024:1b29:2::4
2603:3024:1b29:2::5 2603:3024:1b29:2::5
2603:3024:1b29:2::6 2603:3024:1b29:2::6
2603:3024:1b29:2::7 2603:3024:1b29:2::7
2603:3024:1b29:2::8 2603:3024:1b29:2::8
2603:3024:1b29:2::9 2603:3024:1b29:2::9
2603:3024:1b29:2::a 2603:3024:1b29:2::a
$
See also / references:
https://lists.balug.org/mailman3/hyperkitty/list/balug-admin@lists.balug.or…
On Sat, Feb 28, 2026 at 6:29 PM Michael Paoli
<michael.paoli(a)berkeley.edu> wrote:
>
> So, on the BALUG VM (hosting balug.org, sf-lug.org & berkelug.com.
> (except list on those latter two), many additional domains, DNS
> primaries for all those, additional secondaries, etc.
>
> So, IP addresses:
> $ (for IP in 10.1.10.109 96.86.170.229 2001:470:1f04:19e::2
> 2001:470:1f05:19e::2 2001:470:1f05:19e::3 2001:470:1f05:19e::4
> 2001:470:1f05:19e::5 2001:470:1f05:19e::6 2001:470:1f05:19e::7
> 2001:470:1f05:19e::8 2001:470:1f05:19e::9 2001:470:1f05:19e::a
> 2603:3024:1b29:0:5054:ff:fe13:5199; do echo "$IP" $(dig
> @ns1.google.com. -b "$IP" +short o-o.myaddr.l.google.com. TXT | tr -d
> '"'); done)
> 10.1.10.109 96.86.170.230
> 96.86.170.229 96.86.170.229
> 2001:470:1f04:19e::2 2001:470:1f04:19e::2
> 2001:470:1f05:19e::2 2001:470:1f05:19e::2
> 2001:470:1f05:19e::3 2001:470:1f05:19e::3
> 2001:470:1f05:19e::4 2001:470:1f05:19e::4
> 2001:470:1f05:19e::5 2001:470:1f05:19e::5
> 2001:470:1f05:19e::6 2001:470:1f05:19e::6
> 2001:470:1f05:19e::7 2001:470:1f05:19e::7
> 2001:470:1f05:19e::8 2001:470:1f05:19e::8
> 2001:470:1f05:19e::9 2001:470:1f05:19e::9
> 2001:470:1f05:19e::a 2001:470:1f05:19e::a
> 2603:3024:1b29:0:5054:ff:fe13:5199 2603:3024:1b29:0:5054:ff:fe13:5199
> $ dig -4 @ns1.google.com. +short o-o.myaddr.l.google.com. TXT | tr -d '"'
> 96.86.170.229
> $ dig -6 @ns1.google.com. +short o-o.myaddr.l.google.com. TXT | tr -d '"'
> 2603:3024:1b29:0:5054:ff:fe13:5199
> $
> Recently started adding more. Some of the motivations:
> Had some recent minor glitches between Hurricane Electric (HE.net,
> tunnelbroker.net) IPv6 IPs and AT&T (att.com) IPv6 IPs.
> I've also got Comcast Business IPv6 IPs potentially available to me (my
> current ISP), but for the most part hadn't been using those. Longer
> term will likely move to AT&T, but in the meantime. So, started adding
> those, not yet all that significantly pressed into service, but mostly
> set. Just add relevant statics, DNS entries, etc., and good to go.
> And checking side-by-side, the HE.net/tunnelbroker.net IPs perform very
> surprisingly well - even with their tunneling, latency and number of
> hops, almost indistinguishable. And the up-front prep work will make later
> transitioning to AT&T IPs that much simpler.
>
> Also, changed the Mail Transport Agent (MTA) from exim4 to Postfix.
> There were multiple motivations on that, including:
> exim4 just wasn't cutting it anymore. Most notably, though exim4 has
> configuration for source IP(s) for SMTP send, it just doesn't work. I'd
> mostly kludged around that, by it / the routing generally using by
> default, source of the last (IPv4 or IPv6) IP address added, but that
> was no longer sufficient and had bitten me multiple times before.
> Though it's documented - it just plain doesn't work - and all the
> research basically pointed to same, and I certainly wasn't the only one
> to switch from exim4 to Postix to get a proper working solution.
> Additionally, exim4 has still no capabilities for per-domain aliasing.
> Very annoying, as that means if there's rsvp(a)balug.org, then the alias
> for that also applies to rsvp(a)lists.balug.org, and any other mail
> domains too - not at all what's desired. So, with Postfix, can well
> separate those out. Furthermore, part of the anti-spam configuration
> I'd been using with exim4 was highly outdated and not being maintained,
> and a bit fragile and crusty, so, also good to get away from that, and
> dropping exim4 was also a cleaner simpler way to do that. And, yet
> another advantage, mailman3 well supports two MTAs, Postfix and exim,
> but it better supports and default configurations support Postix, so,
> even simpler to deal with mailman3 on Postfix than exim4. So, all
> those reasons, quite overdue to switch to Postfix, and have now done
> so. And well tested on the BALUG-Test list too. Most all changes were
> also first tested on a test VM (balug13) too, before being implemented
> on the production VM (balug).
>
> In the bit of example testing further above, can see for each of many
> source IPs, that for all of them we can see that they not only route
> properly, but the server in fact sees the expected source IP address,
> (same IP, excepting the one v4 behind NAT/SNAT) and likewise also with
> default source for v4 and v6 - though on the latter I may or may not
> want to change what that default is. But with MTA and DNS using their
> proper source IP addresses for their services, in those case, doesn't
> much matter what the defaults are when the sources are set properly
> when used for the services, most notably source IP on MTA when it sends
> or attempts to send email.
>
> So, fair bit of cleanup and improvements on that infrastructure, and
> helps well clear the way for more.