Hi
Thanks for the debugging hints!
client_timeout sat to 30M and the UID THREAD REFS US-ASCII ALL actually
completes.
But first after ~10 mins on a CPU: Intel(R) Celeron(R) CPU N2930 @ 1.83GHz
(1833.38-MHz K8-class CPU)
and after 69.484 secs on a CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
in your imap client, send the UID THREAD REFS US-ASCII ALL" command and
step through to see what happens
Note that these are not exhaustive steps, more of a "get started, and then
react accordingly, depending on what you see"
I would also try variations of that THREAD command -- i
Hi.
I recently upgraded Cyrus to 3.2.2 from 3.0.13.
Now threading "UID THREAD REFS US-ASCII ALL" on one specific folder with
>50K mails,
makes imapd process use 100 CPU% without any progress. truss[1] or dtrace
shows no output. The process seems totally stuck.
I installed in a
Thanks for your help
Gabriele
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
Da:
Ken Murchison
A:
gbul...@sonicle.com info-cyrus@lists.andrew.cmu.edu
Data:
19 luglio 2016 18.00.28 CEST
Oggetto:
w.gabrielebulfon.com/>
*Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon
*Da:* Ken Murchison
*A:* gbul...@sonicle.com info-cyrus@lists.andrew.cmu.edu
*Data:* 19 luglio 2016 15.02.36 CEST
*Oggetto:* Re: thread=refs
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
Da:
Ken Murchison
A:
gbul...@sonicle.com info-cyrus@lists.andrew.cmu.edu
Data:
19 luglio 2016 15.02.36 CEST
Oggetto:
Re: thread=refs
I don't think much has
bulfon.com <http://www.gabrielebulfon.com/>
*Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon
*Da:* Ken Murchison
*A:* gbul...@sonicle.com info-cyrus@lists.andrew.cmu.edu
*Data:* 14 luglio 2016 17.14.18 CEST
*Oggetto:* Re: th
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
Da:
Ken Murchison
A:
gbul...@sonicle.com info-cyrus@lists.andrew.cmu.edu
Data:
14 luglio 2016 17.14.18 CEST
Oggetto:
Re: thread=refs
I went ahead and committed an implementati
I went ahead and committed an implementation of THREAD-REFS:
https://github.com/cyrusimap/cyrus-imapd/commit/16747e608f32f9dd9348988d3f83cb8f1b037ff6
Per the draft, grouping by subject is skipped and threads (toplevel
messages) are sorted by INTERNALDATE, while the messages within the
threads
Gabriele,
The attached patch is what I was thinking in terms of implementation.
It skips the grouping by subject for REFS, but I didn't do the
REFS-specific date handling. Contrary to what the THREAD=REFS draft
says, I'm not sure if the special date handling should be done in st
u.edu
Data:
8 luglio 2016 17.17.32 CEST
Oggetto:
Re: thread=refs
On 07/08/2016 11:08 AM, Gabriele Bulfon wrote:
Ok, sure, butstill two issues remain other than the draft:
- we need to getrid of subject grouping in REFS, it only brings
disorder,merging stuff that i
to handle this.
- I would try to guess why dovecot does not change sorting in REFS,
keeping it same as REFERENCES
I would contact that Dovecot authors and find out which version of the
THREAD=REFS draft they based their work on.
BTW, which clients use THREAD=REFS
CEST
Oggetto:
Re: thread=refs
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 eachthread,
replacing THREAD=REFERENCES step
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
: thread=refs
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.cdbaby.com/cd/gabrielebulfon
Da:
Ken Murchison
A:
gbul...@sonicle.com info-cyrus@lists.andrew.cmu.edu
Data:
8 luglio 2016 15.02.38 CEST
Oggetto:
Re: thread=refs
On 07/07/2016 02:03 PM, Gabriele Bulfon via Info-cyrus wrote:
I can finally getback to this after so many months!
I checked the
*Da:* Ken Murchison
*A:* info-cyrus@lists.andrew.cmu.edu
*Data:* 5 ottobre 2015 14.04.02 CEST
*Oggetto:* Re: thread=refs
As far as I can tell, the last specification for thread=refs was
here:https://tools.ietf.org/html/draft-ietf-morg-inthread-01
To implemen
refs
- change the sortcrit to use the SORT_REVERSE modifier
what do you think? may be fine?
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
Da:
Ken Murchison
A:
i
As far as I can tell, the last specification for thread=refs was
here:https://tools.ietf.org/html/draft-ietf-morg-inthread-01
To implement this you want to look at index.c in the Cyrus source and
add another entry to the thread_algs[] array. I'm guessing that you can
reuse a lot o
Great, Ken. Can you give me some advice / pointer to the sources I should look
at?
Gabriele
Da:
Ken Murchison
A:
info-cyrus@lists.andrew.cmu.edu
Data:
2 ottobre 2015 19.08.04 CEST
Oggetto:
Re: thread=refs
On 10/02/2015 10:53 AM, Gabriele Bulfon wrote:
Nice, it's not a big deal for
it omit the subject matching, change sorting
and...maybe just this? How much hard do you think it is?
That sounds about right from what I remember of THREAD=REFERENCES (which
I co-authored and implemented) and THREAD=REFS (which I think was last
drew.cmu.edu
Data:
2 ottobre 2015 12.59.08 CEST
Oggetto:
Re: thread=refs
No, there isn't. The conversations work in 3.0 beta contains a lot of what
would be required to efficiently implement THREAD=REFS, but nobody has done the
work to implement it.
It certainly will never be backported to the
No, there isn't. The conversations work in 3.0 beta contains a lot of
what would be required to efficiently implement THREAD=REFS, but nobody
has done the work to implement it.
It certainly will never be backported to the 2.4 series, which is only
getting security updates and fixes for
Hi,
we have systems running cyrus 2.4.12, where thread algorithms are only
references and orderedsubject.
Is there support for the thread=refs algorithm?
Thanks
Gabriele
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To
24 matches
Mail list logo
