Summary: | Support for threading with Microsofts Outlook/Exchange "Thread-Topic" and "Thread-Index" headers | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Nick Brown <nickbroon> |
Component: | message list | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REOPENED --- | ||
Severity: | wishlist | CC: | luigi.toscano, pancho.s |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Nick Brown
2003-03-28 18:06:34 UTC
You say "they are increasingly common in mails" -- is this because other e-mail clients are falling for the "embrace, extend, exterminate" trap, or is the relative percentage of microsoft-based clients increasing? I can't help but think that "supporting" this non-rfc header is playing right into microsoft's hand -- they may be prepared to "drop" this overnight thus making everyone else's "client" look like it's broken [consider the possibility that they have some other header already defined -- outlook and exchange may already have the code in place to use the "new, as yet undocumented header" and simply have it "triggered" by receiving a message with that header. Result: at the drop of a hat, Microsoft can force everyone that "complies" with their way of thinking into a re-write...] If it is the second case, (that the relative number of outlook/exchange clients & servers is increasing,) well, dunno what to say to that... I think its very much the second case. Outlook/exchange is the only client that I know uses these headers. I don't think anyone has of yet reverse engineered the "Thread-Index" header and thus been able to use them. Certainly no linux client I can find uses them (i've raised wishlist bug reports with several to add support, as I'm doing with kmail). I've after asking around, to other windows client seem to use them either. (But then "most" windows users use outlook/exchange) It is rather annoying that outlook/exchange does not use the rfc optional headers for threading as just about every other client in exsistance does, but given its pervasivness, supporting these prioprity headers seem like the only option. (given the unlikelyness of microsoft falling into line and using the rfc optional headers.) Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding. Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. Still applies to kmail2, component: message list. Thanks for the update. |