[swift-evolution] [Discussion] mailing list alternative
cocoadev at charlessoft.com
Mon Feb 6 21:58:57 CST 2017
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.
> On Feb 6, 2017, at 6:45 PM, Daniel Duan via swift-evolution <swift-evolution at swift.org> 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 <jberry at rogueorbit.com <mailto:jberry at rogueorbit.com>> wrote:
>>> On Feb 6, 2017, at 4:28 PM, Daniel Duan via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> 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 <xiaodi.wu at gmail.com <mailto:xiaodi.wu at gmail.com>> 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
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution