Could definitely use help on trying to recovery the numbering scheme used by messages on the Gemini Mailing List. It should be easy, but I can't crack it. More details here:

gemi.dev/gemlog/2023-10-15-numbering-madness.gmi

🧇 Acidus

2023-10-15 · 7 months ago

3 Comments ↓

👤 jdcard · 2023-10-15 at 20:58:

Could you use the original e-mail threading scheme based on the Message-Id, In-Reply-To, and References headers? See

— https://datatracker.ietf.org/doc/html/rfc5322#page-25

🧇 Acidus [OP] · 2023-10-16 at 00:37:

Sorry for not being more clear. Threading is not the problem. I'm using Message-Id, In-Reply-To, and References headers to build the threads. I'm also using JWZ's threading algorithm from Netscape, which handles threading when those headers are missing/wrong, as is the case for a lot of threads in the mailing list

The problem is linking the "message number" (aka. the 6 digit number used as the HTML filename) that Orbital Fox assigned to each message in the mailing list for the HTML interface with the message content that is in the mbox files.

☕️ mozz · 2023-10-16 at 02:58:

Check the source code :)

— https://github.com/Koumbit/mailman2/blob/437d44b2258726fe150308d5fe5686f34c70d069/Mailman/Archiver/pipermail.py#L582

Looks like the index is a "sequence" number, and the missing numbers are emails that were discarded by the mail server (detected as spam or otherwise thrown away).

Seems like you could probably:

1. Pull all of the sequence numbers from the wayback archive yearly pages (sorted by date).

2. Sort the emails in your mailbox by UTC date.

3. Line up the numbers with the emails.