Gmail does the same; I wonder if it's a Mailman feature/bug that triggers the splitting.<br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 6, 2017 at 7:59 PM Charles Srstka via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg">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.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Charles</div><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"></blockquote></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Feb 6, 2017, at 6:45 PM, Daniel Duan via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br class="m_453625111507059298Apple-interchange-newline gmail_msg"></blockquote></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg">Mail.app grouped it in the correct thread (further proves that email clients are awesome 😀). Unfortunately mailman did not do so.<div class="gmail_msg"><br class="gmail_msg"></div></div></div></blockquote></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><span id="m_453625111507059298cid:66030411-98BD-4C32-9789-C3F6DA579724@sfhq.lyft-corp.net" class="gmail_msg"><Screen Shot 2017-02-06 at 4.44.42 PM.png></span><br class="gmail_msg"></div></div></div></blockquote></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Feb 6, 2017, at 4:40 PM, James Berry <<a href="mailto:jberry@rogueorbit.com" class="gmail_msg" target="_blank">jberry@rogueorbit.com</a>> wrote:</div></blockquote></div></div></div></div></blockquote></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><br class="m_453625111507059298Apple-interchange-newline gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Feb 6, 2017, at 4:28 PM, Daniel Duan via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br class="m_453625111507059298Apple-interchange-newline gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg">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?</div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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.</div><br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Feb 6, 2017, at 4:12 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="gmail_msg" target="_blank">xiaodi.wu@gmail.com</a>> wrote:</div><br class="m_453625111507059298Apple-interchange-newline gmail_msg"><div class="gmail_msg">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.<br class="gmail_msg"><br class="gmail_msg"></div></blockquote></div></div></div></div></blockquote><br class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div></div></div></blockquote></div></div></div></div></blockquote></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">_______________________________________________<br class="gmail_msg">swift-evolution mailing list<br class="gmail_msg"><a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg"></div></blockquote></div></div>_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>