Hi Ken,
--On Friday, January 10, 2003 8:46 AM -0500 Ken Murchison <[EMAIL PROTECTED]>
wrote:
|> Question for the list: should it?
|
| FWIW, Cyrus does. This is because the header is decoded for the SEARCH
| and then passed on to SORT/THREAD. Interestingly, Netscape Messenger
| makes separate threads, even though the algorithms are supposed to be
| similar/same.
|
| I'd vote that the draft is fine, and that UW needs to be fixed (less
| work for me ;)
FYI My client-side implementation of the THREAD algorithm also does it as
per the current draft 'by default' since the subject is already MIME
decoded and 2822 unfolded by the time it gets processed. I believe that is
the right thing to do.
However, I will again voice my annoyance with the fact that the
THREAD=REFERENCES extension does any kind of grouping based on subject.
This is an attempt to fix the behaviour of broken (old) clients that do not
generate proper In-Reply-To and References headers at the expense of
legitimate clients that generate those headers in conformance to 2822.
--
Cyrus Daboo
- Thread extension weirdness Timo Sirainen
- Re: Thread extension weirdness Mark Crispin
- Re: Thread extension weirdness Timo Sirainen
- Re: Thread extension weirdness Mark Crispin
- Re: Thread extension weirdness Ken Murchison
- Re: Thread extension weirdness Sebastian Hagedorn
- Re: Thread extension weirdness Cyrus Daboo
- Re: Thread extension weirdness Arnt Gulbrandsen
- Re: Thread extension weirdness Lawrence Greenfield
- Re: Thread extension weirdne... Mark Crispin
- Re: Thread extension wei... Lawrence Greenfield
- Re: Thread extension wei... Mark Crispin
- Re: Thread extension wei... Cyrus Daboo
- Re: Thread extension wei... Mark Crispin
- Re: Thread extension wei... Lawrence Greenfield
- Re: Thread extension wei... Mark Crispin
- Re: Thread extension weirdne... Arnt Gulbrandsen
