On Wed, May 14, 2025 at 01:38:12PM +0000, Warren, Tom @ Gainesville via NANOG wrote:
However, I tried to sign up, and I am waiting to get the email to set up my account and it never arrived, yes I checked my spam filtering.
If you were subscribed to the old list, and if you were sorting/filing incoming messages based on the List-Id header (per RFC 2919) then it's possible that the return message from Mailman asking for subscription confirmation went to wherever you were/are sending "outages" list traffic. This happens because Mailman -- in my view, erroneously -- applies the List-Id header to administrative traffic such as subscription confirmation requests, subscription confirmations, etc. I believe I raised this bug to the Mailman folks about 15 years ago, but it's still present. (Why "erroneous"? Because such messages are not actually list traffic and shouldn't be marked as such. Not only does doing so risk their mishandling, but it conflates messages which should always be private with messages which are available to everyone on the mailing list.)
I also don't see any method of support on the signup or the sign-in pages. So I had to turn here for help.
I haven't tested it yet, but I would presume that the standard -owner address (per list) is supported, e.g. outages-owner@outages.org. (If it's not supported, then it darn well should be, for exactly this reason.) Incidentally, one of my users subscribed to "outages" earlier this morning and that process appeared to work correctly. However, a followup subscription to outages-discussion did *not* work correctly: no request-for-confirmation was issued, the address was just subscribed. This needs to be fixed ASAP for what I trust are obvious reasons. ---rsk