Fossil Forum

Apparently Fossil Forum delivered two messages that have identical content in the body but differing timestamps, Message-id, and what's even more strange, different forumpost identifiers.

These two forum posts were delivered to me with the exact same body, at the exact same time, on two different SMTP delivery connections:

https://fossil-scm.org/forum/forumpost/60a9c0e611 https://fossil-scm.org/forum/forumpost/c09c6a3fc7

Both have a Return-Path that is identical:

Return-Path: noreplyc82f4e48b@fossil-scm.org

The body in both emails is that of the first forumpost 60a9c0e611. Here are the differences (as calculated using diff command) and I've removed irrelevant information and replaced it with "[trim]".

-Received: (qmail 4522 invoked from network); 21 May 2026 12:03:16 -0000 +Received: (qmail 6186 invoked from network); 21 May 2026 12:03:16 -0000 [trim] Received: from localhost (core [local]) - by core (OpenSMTPD) with ESMTPA id 54750f00 + by core (OpenSMTPD) with ESMTPA id 6f90f3a6 [trim] Subject: [fossil-forum] Forum enhancement(?): option to search only subject lines -Message-Id: 60a9c0e61193f3921644e66cd7e4cd38@fossil-scm.org +Message-Id: c09c6a3fc75b0c21540e59f441ab6b15@fossil-scm.org In-Reply-To: d27d3e093c00eedebe9ec3f4f9d0f0b0@fossil-scm.org [trim] -Forum post by torstenberg on 2026-05-21 12=3A02=3A31 -https=3A//fossil-scm.org/forum/forumpost/60a9c0e611 +Forum post by torstenberg on 2026-05-21 12=3A02=3A47 +https=3A//fossil-scm.org/forum/forumpost/c09c6a3fc7

OK, this is a useful feature to have. I gave it a try and this my my p= roposal for such a feature, as a fossil diff against the most recent=

Everything else about these 2 unique messages is identical. How did the body of the first forumpost end up in the body of the second forumpost but somehow get it's own unique forumpost identifier and message-id?

Here are logs from the mail server (MST timestamps) that show that 2 unique deliveries came in with the exact same Return-Path (aka MAIL FROM) so we can rule out some kind of corruption during writing of messages to disk:

2026-05-21 06:03:04.511160500 tcpserver: pid 18101 from 194.195.208.62 2026-05-21 06:03:15.713733500 60776 < MAIL FROM:noreplyc82f4e48b@fossil-scm.org 2026-05-21 06:03:15.826592500 tcpserver: pid 21905 from 194.195.208.62 2026-05-21 06:03:15.941239500 60776 < RCPT TO: 2026-05-21 06:03:16.313551500 60776 > 250 ok 1779364996 qp 4522 2026-05-21 06:03:16.430045500 60776 < MAIL FROM:noreplyc82f4e48b@fossil-scm.org 2026-05-21 06:03:16.548777500 60776 < RCPT TO: 2026-05-21 06:03:16.925830500 60776 > 250 ok 1779364996 qp 6186 2026-05-21 06:03:17.046541500 tcpserver: end 18101 status 0 2026-05-21 06:03:36.256022500 tcpserver: end 21905 status 0

I'm baffled how this could even happen.