Here is a recent example. The reply was sent before the actual post:

Subject: [fossil-forum] Check and merge forum-skin-links branch
Message-Id: <a0dc1fe28cbce6566a004acdd8971278@fossil-scm.org>
In-Reply-To: <b8bd7166707db46827727f03d12c329d@fossil-scm.org>
From: <fossil-forum@fossil-scm.org>
Date: Thu, 9 Aug 2018 23:40:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Forum post by wyoung on 2018-08-09 23:40:10

Subject: [fossil-forum] Check and merge forum-skin-links branch
Message-Id: <b8bd7166707db46827727f03d12c329d@fossil-scm.org>
In-Reply-To: <0d9416b53d5f8ecaaf5928cc5c750e23@fossil-scm.org>
From: <fossil-forum@fossil-scm.org>
Date: Thu, 9 Aug 2018 23:41:22 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Forum post by vor0nwe on 2018-08-09 22:32:18

I assume they're being sent in the order that one of the moderators clicks the Approve button on the posts.

This should have little practical import, since the headers in the message should be enough for your MUA to sort out the threading after getting the "missing" intermediate post.

I suppose we can train the moderators to approve posts in thread order when they have the choice. I don't think anything should change at the code level here.

Should be fixed now. I think. We'll monitor to see if the problem persists.