2026-01-25T12:18:28  <olh> Is there any tracking about the recent data loss while delivering copies to subscibers, like 20090224155527.GA26899@ursa.suse.cz for example?
2026-01-25T13:17:40  <cboltz> olh: mailman receives the bounces and unsubscribes addresses that bounce multiple times
2026-01-25T13:18:23  <cboltz> we also have the usual mail logs if we need to manually check what happened to a mail
2026-01-25T13:26:38  <olh> I got some replies, but not the primary mail. So, what happened to each copy of that exact msg that was supposed to be sent out? Can such question be answered?
2026-01-25T13:27:57  <olh> bbl
2026-01-25T13:36:11  <cboltz> basically yes, but checking for _all_ subscribers is quite some work
2026-01-25T13:36:26  <cboltz> if you tell me a specific receiver, that makes things easier/faster
2026-01-25T14:49:50  <matrix-o-o> <SFaulken> hm, is there a glitch in code.o.o that allows users to see "private issues" that they're not subscribed to?
2026-01-25T14:52:02  <matrix-o-o> <SFaulken> I'm not sure what's going on, but we've got a private issue discussion a moderation issue with a user, and somehow, I've gotten an e-mail from the user in question, through pagure, replying to a comment on the ticket, including quoted text from the private issue
2026-01-25T15:50:43  <matrix-o-o> <knurpht - Gertjan> Confirmed. Got the same email.
2026-01-25T16:28:04  <acidsys> sounds like a case of YAPPing (Yet Another Pagure Problem)
2026-01-25T16:36:39  <cboltz> just as an idea - could it be that this person is watching the mod-team _project_, and that the issue was initially created as public (and later made private)?
2026-01-25T16:37:57  <matrix-o-o> <SFaulken> I don't believe it was, but it's not impossible. I just checked the settings, and it looks like tickets are set to open as private by default.
2026-01-25T16:39:13  <matrix-o-o> <SFaulken> this is the first time I've seen it happen, so I don't really know if it's a wider issue, and there's nothing in the ticket that is _that_ sensitive, (no PII or anything), just seemed odd to me.
2026-01-25T16:46:01  <olh> regarding email delivery, and a potential subscriber self-service: it will be helpful if the list subscriber software and the local MTA cooperate, and track each copy. The transmission id from the local MTA and the transmission id. I think a good start is to let the MTA log to individual files, one per RCPT. Then whatever tooling can grab that log and make it available for the subscriber. That way I would be able
2026-01-25T16:46:01  <olh> to get the answer myself. According to the log of some random mail, there are multiple systems involved, like "mailman3" and "mx2" and likely more.
2026-01-25T16:47:09  <olh> because right now, what is the indicator that there was a data loss along the way?
2026-01-25T16:51:09  <cboltz> mailman tracks a "bounce score" which is visible in the web interface (probably admin-only, but I'm not sure)
2026-01-25T16:52:30  <cboltz> there are indeed multiple servers involved in mailinglist mail - mails come in on mx1 or mx2, get sent to mailman3 and are then delivered to the list members via mx1 and mx2
2026-01-25T16:55:19  <cboltz> self-service log access sounds like a nice idea, but I'm afraid it won't be as easy as it sounds ;-)  (to start with the most boring example - AFAIK mailman groups recipients, so one mail gets sent to 10 recipients)
2026-01-25T17:12:16  <olh> that would be no problem. mailman gets a transmission id. the MTA must write its log to a RCPT file, instead of, or in addition to, dumping everything to syslog. Or whatever MTA actually does for logging.
2026-01-25T17:13:13  <olh> since the number of RCPTs is not infinite, that should be doable without exhausting resources.
2026-01-25T17:20:09  <olh> I can have a look, my pub key is in LDAP.