Re: Even Worse
The problem is that it really can't. Email clients can easily categorize by such things as sender, recipient(s), thread (subject line, in reply to, or checking for copies of previous messages), dates, and if they're willing to add even more storage, some keyword database for message contents. That's great, but it's also what I can quite easily do from the client's advanced search controls. I don't need the client to categorize my archives by sender because it's pretty easy for me to do that manually if it comes to that. The categorization that could be needed is more advanced processing of the message content to link related messages together. For example, if I am included on thread A about something, then start thread B about the same thing but with different people, and later am involved in thread C which reports a problem with the thing implemented by thread B, those things are related in my mind but will not be linked in the software. The intelligence to identify that link is usually absent, and if you try to build it in you end up with all the standard language processing problems and likely won't get useful results. If the messages were crucial and required frequent cross-referencing, I would perform that organization manually, thus having the certainty that I've done it correctly and in a way I can quickly navigate. When you consider that, at least in my example, all the effort spent on this autocategorization is for messages the user is keeping around because space is cheap and with the expectation that they will be unneeded, it is often not worth it.