Hi,
I'm no expert on this, but I've seen similar behaviour on my own system.
From what I can tell, the "in-reply-to" or "references" field is needed
for "real" threading and unfortunately, this is a function of the
client, and therefore impossible to enforce across the whole internet.
On my own system 99% of messages don't thread properly, they basically
sort by subject and date and this is where "possible follow-up(s)" comes
in; it's saying "hey; these look like they are related, but how the hell
do I know?".
I accepted I'd never be able to enjoy "real" threading on my system, so
instead I just set my resource file to exclude the "possible
follow-up(s)" text. This means the replies indent but are directly below
the original message.
What is really bad is where you get mixed up between "sent" and
"received" date. For example Outlook Express tends to use the "received"
date by default, but some list servers use "sent" instead, so at one
stage I had the first reply as the root of the thread with the original
message showing indented as a "possible follow-up", LOL!
Eric Pretorious wrote:
It seems that for some reason - in most but not all of the INTERNAL mailing
lists that we archive with MHonArc - many
of the threads are initially broken. e.g., A typical thread might appear like
this:
File permissions., Shan Chao
<Possible follow-up(s)>
Re: File permissions., Matthew Funk
Re: File permissions., Zoe Barnett - Sun Microsystems
Re: File permissions., Matthew Funk
Re: File permissions., Randall Chuck
Re: File permissions., Randall Chuck
Looking at the header information for these messages:
<!--X-Message-Id:
200008012223(_dot_)PAA00498(_at_)ha3mpk(_dot_)Eng(_dot_)Sun(_dot_)COM -->
<!--X-Message-Id:
200008012227(_dot_)QAA26246(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
<!--X-Reference:
200008012227(_dot_)QAA26246(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
<!--X-Message-Id:
200008021347(_dot_)HAA11397(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
<!--X-Reference:
200008021347(_dot_)HAA11397(_at_)bast(_dot_)Central(_dot_)Sun(_dot_)COM -->
*** No x-message-id information in this message ***
Is this disconnect being caused by our mailing list server?
What, specifically, should I ask our mailing list admin to adjust to prevent
this disconnect?
Is there a setting in MHonArc that I can set to overcome this?
Eric P.
SunPS Web Infrastructure Team
--
Gerry Hickman (London UK)
