Yeah, so:

postorious is the admin/management application/web pages. It's under /admin/

hyperkitty is the archiver, it's under /archives/

mailmail3 is the entire thing.

Note that the links you give above are to our staging instance. Not sure it matters, just FYI, thats not the live production instance.

Would you be willing to file this upstream? ( https://gitlab.com/mailman/mailman ) A way to get back to archives/front page from subscriptions seems like a good idea to me. The admin/lists/ is for administrating lists not reading archives, not sure what to do there.

I was wondering about the 'stg.' part of those URLs. I'm not sure how I got using those in the first place. Browser history kept me going back conveniently enough, but I think it was a Google search that (mis)guided me from the start. I wonder how much that was affecting all my "fun" with #5712.

File upstream at https://gitlab.com/mailman/mailman/issues/308

Thanks Kevin!

Yeah, the stg stuff could have confused things for sure. ;(

Thanks for filing this!

So how does staging work? Do I need to nuke my subs there and redo on production or ....

Looks like they share the same DB behind the scenes so all I really need to do is just use the web UI from non-staging.

I really need to stop sticking my thumb in so many different pies at once. :-/

They do not share the same db. But from time to time we sync the prod one to stg...

Ok, thanks for the clarification. That proves that I must have done my recent subscription editing in production because the values there are the new ones. I suspect now that when I was having problems (#5712) that it was then I was working in staging accidentally and perhaps that's why those edits had no apparent effect on the mail I was actually being sent.

Regardless, I intend to have a beer or two to cap the week off -- it's been crazy. If I can ever drag my but to a fudcon I most certainly owe you a beer good sir! :-)