Thanks! I rolled my own RPM with that patch, and I can confirm that it
works.
--On 11. Februar 2019 um 09:12:14 -0500 Bron Gondwana
<br...@fastmailteam.com> wrote:
Yep, it's fixed in git now, so the next release will automatically create
G keys for messages, even if they don't have a threadid!
Bron.
On Mon, Feb 11, 2019, at 21:30, Sebastian Hagedorn wrote:
So running ctl_conversationsdb -z followed by -b would assign thread ids
to those messages? Because it works when I do that. Clearly this is an
edge case, but IMO it should be handled somehow other than silently
failing ;-)
--On 11. Februar 2019 um 05:16:47 -0500 Bron Gondwana
<br...@fastmailteam.com> wrote:
> That sounds like the source messages have no thread id, and hence they
> aren't being stored.
>
> This is an interesting question actually, should we still store G keys
> for messages without thread identifier (CID)?
>
> Bron.
>
> On Mon, Feb 11, 2019, at 21:11, Sebastian Hagedorn wrote:
>> Hi Bron,
>>
>> --On 11. Februar 2019 um 04:23:16 -0500 Bron Gondwana
>> <br...@fastmailteam.com> wrote:
>>
>> > The data in conversations.db is added and removed in real time as
>> > messages are appended and updated in the cyrus.index.
>>
>> do you know why that does not seem to happen when using the "old" sync
>> protocol for replication?
>>
>> <https://github.com/cyrusimap/cyrus-imapd/issues/2376>
--
--
.:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
