Sorry for the delay. Yes, this does seem like the right thing to do. The conversation root being the user is a convenience for a ton of things to the point that we're basically using "fake users" for storing related things for a business.
But doing the same thing for mailshare would be quite easy I think. There are only a few places where we convert mailbox name to conversations_db path.
Bron.
On Tue, Sep 22, 2020, at 01:00, Thomas Fricker wrote:
Hello,I noticed that Cyrus does not keep track of conversations in mailshare folders.There is a code comment addressing this issue in conversations.c:/* only users have conversations. Later we may introduce the idea of* "conversationroot" in the same way we have quotaroot, but for now* it's hard-coded as the user */Is it still imaginable adding this feature in a future Cyrus version?Can you elaborate on a reasonable approach of implementing this on the current codebase?My goal is to have 1 conversation.db per mailshare subtree (not per single folder).Any ideas?Thanks,--Thomas Fricker
www.bluemind.net / Blog[WEBINAR]
Migrer sa messagerie vers BlueMind depuis Exchange
24/09/20 - 11h
----Cyrus Home Page: http://www.cyrusimap.org/List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/To Unsubscribe:Attachments:
- x-disclaimer1569892563-0.png
- x-disclaimer1569892563-1.png
- x-disclaimer1569892563-2.png
- x-disclaimer1569892563-3.png
- x-disclaimer1569892563-4.png
--
Bron Gondwana, CEO, Fastmail Pty Ltd
brong@xxxxxxxxxxxxxxxx
---- 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
