On Thu, 2012-04-05 at 13:10 -0700, Mark Sapiro wrote: > Pierre-Yves Chibon wrote: > > > >Ok, I missed a something here. > >So when it parses the email, it checks for 'References' or > >'In-Reply-To'. > >- If it finds them, it looks for the preceding email > > - if it finds the preceding email, then the current email gets the > >ThreadID from the preceding email > > - if it does not find the preceding email, then the current email is > >assumed to be a new thread and thus its ThreadID is its Message-ID > >- if it does not find 'References' or 'In-Reply-To', then the current > >email is assumed to be a new thread and thus its ThreadID is its > >Message-ID > > > This is still incomplete. One of the MUAs I use generates In-Reply-To: > headers but not References: headers. Thus in cases where someone has > replied to me but not included the list (and may or may not have > subsequently sent the reply to the list with a different Message-ID), > and I reply and include the list, the Message-ID in my In-Reply-To: is > not in the archive. > > Another situation is someone replies to me and the list, but the list > reply is greylisted and not retried for a while. Meanwhile, I reply to > my copy and the Message-ID in my In-Reply-To: is not yet in the > archive. > > Threading is not easy.
I haven't completely read the link that Stephen sent earlier, hopefully the answer to these two points is in there :) Pierre _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
