Mainly web clients, installed clients usually implements threading internally
to overcome problems with the original references algorithm that is often
confusing.
The problem with references is that it includes subject grouping, that is an
old netscape model of the 90s: today, we just need refer
On 07/08/2016 11:08 AM, Gabriele Bulfon wrote:
Ok, sure, but still two issues remain other than the draft:
- we need to get rid of subject grouping in REFS, it only brings
disorder, merging stuff that is not related
I believe that the parameterization of the core functions should be able
to
Ok, sure, but still two issues remain other than the draft:
- we need to get rid of subject grouping in REFS, it only brings disorder,
merging stuff that is not related
- I would try to guess why dovecot does not change sorting in REFS, keeping it
same as REFERENCES
--
Is there an actual RFC? All I find is draft-ietf-morg-inthread-01.
Looking at that draft, the only difference between REFS ad REFERENCES is
this:
THREAD=REFS sorts threads by the most recent INTERNALDATE in each
thread, replacing THREAD=REFERENCES step (4). This means that when a
Ok, it works :) but checking against dovecot implementation, it looks like they
have refs order same as references, but without subject grouping. AFAIK the RFC
on refs says ordering of dates within the group should be reversed. Am I wrong?
-
Testing ;) and checking against a dovecot machine with refs and same messages.
Will let you know
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbab
On 07/07/2016 02:03 PM, Gabriele Bulfon via Info-cyrus wrote:
I can finally get back to this after so many months!
I checked the sources, and I actually see it doesn't look very hard.
Looks like:
- renaming all functions like "index_thread_ref" into
"index_thread_references"
- duplicate them
