On Friday, 6 January 2012 at 19:11:27 UTC, Brad Roberts wrote:
On 1/6/2012 3:32 AM, Vladimir Panteleev wrote:
On Friday, 6 January 2012 at 03:17:55 UTC, Walter Bright wrote:
Something about the way you are posting is breaking the
threading of these message threads.
This is because the mailing list gateway assigns new Message
IDs to posts forwarded from the mailing list to the
newsgroup. Mailing list users don't see these IDs, so a post
from a mailing list user replying to a post by another
mailing list user will never appear as a "reply" to newsgroup
users.
I have an idea of how to counter this in DFeed (subscribing
DFeed to mailing lists, in addition to polling the newsgroup
server, and saving both Message IDs for each post), but it'll
still be broken for everything else tied to the newsgroup
server.
It's not nearly that generally broken. As evidence.. this
reply.. or any of my replies over the last mumble (5?) years.
Or any of the replies from the hundreds of other people that
use the lists rather than the newsgroups.
The problem is not visible to mailing list users. Mailing list
users receive messages with the original Message ID.
I admit I haven't looked hard for a counter-example, but there's
an obvious pattern emerging to newsgroup users when two
mailing-list users engage in a dialogue: their posts appear flat,
all replies to the same parent (a post from a newsgroup user).
The last time anyone researched it, there was a known bug in
mailman (the gateway software in use) that triggered with
messages that are crossposted to multiple newsgroups. I'd
welcome anyone to dig deeper into the mailman code and send
bug report and/or fixes. I'll happily install any updates that
come down the pike.
I found this:
http://wiki.list.org/pages/viewpage.action?pageId=4030712
So, it looks like this behavior is by design.
Note that the page states the following:
If your mail program or newsreader implements message threading
correctly (see http://www.jwz.org/doc/threading.html), then it
should be able to deal with these differences.
I don't know if they simply refer to software being able to
handle posts without known parents, but fully-correct threading
is certainly impossible - the original message IDs are never
mentioned anywhere (Mailman could have at least had the courtesy
to put the original ID into some X-Mailman-Original-ID header). A
workaround in DFeed as described above would probably be the
safest solution...
