Hi
We are using share mailboxes quite a bit.
These are quite extensively and contain e.g. separate folders for
projects, companies etc. We are talking thousands of shared boxes with
each hundreds to ten thousands of mails, some of them contain a lot more
emails.
Additionally we use shared Archive folders, that are automatically
filled for archiving purposes, but also contain all mails of certain age.
We are using this out of the box and did not find performance issues
here, only the difficulty in having to configure Cyrus manuall on the
command line.
Cheers
T
Ricardo Signes via Info schrieb am 24.09.25 um 22:23:
Hi,
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!
--
rjbs
------------------------------------------
Cyrus: Info
Permalink:
https://cyrus.topicbox.com/groups/info/Tc1ebd8db5775ccfa-M5c3ce36379ab6dc3d3489f64
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
