Uday S Reddy writes:
Yes, indeed, multiple instances are definitely a serious issue. I
referred
to them as "duplicate copies" of messages earlier. They did give me
significant trouble because I didn't worry about them initially. But,
later, I discovered that it was important to keep track of which copy among
the duplicate copies is regarded as the canonical copy in the thread tree.
The duplicate copies share the same message-id, but we cannot assume that
they are identical. In the simplest case, one of them might have the
'deleted' attribute set and another one not. The duplicate copies have
different UID's on the IMAP server. Sometimes, they even have different
References headers because the mailing-list admins munge them!
Another thing I might add. A solution for fixing broken threads is actually
to make more messages to be duplicates of each other. Mailing lists,
newsgroups and bug trackers etc. change the message-id's of messages
discarding the original message-id's. The threading code would need to
recognize the duplicates that arise in this way and identify messages even
if their message-id's differ. Keeping trace of the canonical message in
each container will prove to be even more important with this than it has
been!
Cheers,
Uday
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta