[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 84256] Threading a mix of send and received messages
From:       Till Adam <adam () kde ! org>
Date:       2004-06-30 20:46:37
Message-ID: 20040630204637.28560.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=84256      




------- Additional Comments From adam kde org  2004-06-30 22:46 -------
Ok, this is what I suspected. Your replies (the sent ones) are proper replies with \
correct In-Reply-To headers (of course, after all KMail creates them ;), but the \
other half of the conversation has to be subject threaded, apparently, because it is \
missing In-Reply-To or References headers. I would bet that they were generated by \
OL/Exchange or something similarly broken. The problem is that due to the way the \
threading algorithm works the messages that can be threaded perfectly are threaded \
and only aftwards are the parents of those mini-threads considered as parents for \
subject threading. This means that mails that are not toplevel after the regular \
threading pass will never be parents of subject-threaded mails. The result is the \
slightly off threading you see. I will try to come up with a workaround that improves \
this particular case, but I don't want to break the other (more common) cases which \
led me to the current threading algorithm. In short, and now that you have read \
through more info on threading than you ever wanted to get, I'll see what I can do, \
but don't hold your breath. ;)


[prev in list] [next in list] [prev in thread] [next in thread]