Created attachment 2519 [details] Robert's message is a child of Martin's although he replied to Oguz in NNTP folder Hi, the messages of a particular user (Robert Elz) on the gmane.comp.shells.bash.bugs news group (accessed via the news.gmane.io nntp-server) is always displayed as a child of the message of which it is a grand child. I don't see a reason for that as the headers of his messages appear to be correct, i.e., both the "In-Reply-To:" and the "References:" header list the correct parent the latter does so as the first reference. Indeed, after copying the whole thread to a local folder the tree is displayed correctly there. I attach two screenshots and the headers of Robert's message and of the one he was replying to.
Created attachment 2520 [details] In local test folder Robers't message is correctly placed under Oguz'
Created attachment 2521 [details] header of robert's message
Created attachment 2522 [details] header of Oguz' message
Comment on attachment 2521 [details] header of robert's message Sorry the attachment is not complete.
Created attachment 2523 [details] header of robert's message The complete header
Looking at the archive of the original mailing list (before gmane copied it) shows the wrong threading arrangement: https://lists.gnu.org/archive/html/bug-bash/2024-11/threads.html I downloaded the mbox archive from lists.gnu.org and, after importing it into Claws Mail, the threading is correct. What seems to be happening is that in Robert's messsage he has quoted the Message-ID header in the body of his reply, and this 2nd Message-ID seems to be confusing both the gmane newsgroup and the original mailman online archive. But, as you notice, if you copy the whole thread to a separate folder in Claws Mail, Claws Mail is not confused by the 2nd Message-ID header in the body, and actually threads it correctly. The bug seems to be in mailman archiving (and the gmane copy, which replicates the wrong threading).
But why then is the threading also wrong in Claws Mail when I view it in the gmane newsgroup folder as can be seen in my first screenshot? Does that mean that in the nntp communication there is separate information on how the messages are threaded which takes precedence over the headers?
(In reply to Jazz Fan from comment #7) That's hard to tell with the information that you've supplied coupled with the fact that I can't access the gmane server.
(In reply to Paul from comment #8) Is there anything I can do to provide more information? I could send the messages of the thread as they are lying in my ~/.claws-mail/newscache/news.gmane.io/gmane.comp.shells.bash.bugs folder.
(In reply to Jazz Fan from comment #9) Send me the the cache folder directly via email, tarballed. It might shed some light on the situation.
(In reply to Paul from comment #10) Just reopening this as Paul confirmed the problem being in the code to display nntp lists after having received the tarball.