on. den 24. 09. 2025 klokka 16.23 (-0400) skreiv Ricardo Signes via Info: > Over time, we're trying to reduce the number of possible configurations of > Cyrus. Every optional feature means more possible configurations, which > means more testing and debugging. A likely candidate for "no longer > optional" in the future is the conversations system. In general, I do not > expect this to cause difficulty, but there is one place that it becomes > interesting. > > The conversations database is per-user, and so grows in proportion to the > user's mail size. That's the unit you have to scale at. > > For shared, not-user-owned mailboxes, there is no conversationsdb. If we > want to create one, we will need to think about where it goes, and how we > scale. For example, if you're using shared mailboxes to store all of usenet, > you may well want to split that up into multiple conversation databases. > > We (Fastmail) do not use shared mailboxes like this. I am looking for a show > of hands or description of use case from anybody out there who is using > shared mailboxes like this so we can get a sense of what folks are doing. (I > realize that this is not going to be a scientific survey of all Cyrus IMAP > users.) > > Hit reply or reply to me privately. Thanks! >
I am not entirely sure what conversationsdb is used for, but it seems it used to track threads for mail sent by clients not using References or In-reply-to correctly? why would this need to be per-user? we have not enabled conversationsdb and have not missed the functionality. we do need per-user Seen-databases for shared folders, though, but that is probably not relevant for this development. -- venleg helsing, Kjetil T. ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/Tc1ebd8db5775ccfa-M6c9ab6521a5e95ee2654067b Delivery options: https://cyrus.topicbox.com/groups/info/subscription
