Oh, Mail messes up the grouping of them quite a lot in my experience. Whenever we get one of those epic, super controversial threads with tons of posts in them, it’s almost guaranteed to split into two or three parallel threads, on my machine anyway.
Charles > On Feb 6, 2017, at 6:45 PM, Daniel Duan via swift-evolution > <[email protected]> wrote: > > Mail.app grouped it in the correct thread (further proves that email clients > are awesome 😀). Unfortunately mailman did not do so. > > <Screen Shot 2017-02-06 at 4.44.42 PM.png> >> On Feb 6, 2017, at 4:40 PM, James Berry <[email protected] >> <mailto:[email protected]>> wrote: >> >>> On Feb 6, 2017, at 4:28 PM, Daniel Duan via swift-evolution >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> I’ve been wondering about this for a while. What heuristic does mailman use >>> to group emails? It this really impossible even if the title, email body, >>> recipient all fits as if it’s from a existing subscriber? >> >> This email is related to the thread only by the subject. How does it work in >> your email client? I just wrote a new message, no “reply to”, etc. >> >>> >>>> On Feb 6, 2017, at 4:12 PM, Xiaodi Wu <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> No, as you define it, they're not mutually exclusive. But maintaining the >>>> option to reply to a thread at an indeterminate point in the future when >>>> you finally get around to reading _is_ essentially mutually exclusive to >>>> not storing a copy of every email sent to the mailing list on your email >>>> account somewhere. >>>> >> >> >> > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
