On Thu, Nov 20, 2014, at 05:25 AM, Andrew Morgan wrote: > On Wed, 19 Nov 2014, Fabio S. Schmidt wrote: > > > Hi, > > > > I have an environment with Cyrus Aggregator and this scenario: > > > > Every user has its INBOX stored on a server and has an archiving > > folder which is kept on another server. > > > > I have noticed that when I move some folder from the INBOX to the > > archiving hierarchy, Cyrus (I'm using 2.4.14) doesn't recognise it > > and create the structure and keep the folder on the server which has > > the INBOX stored. > > > > Is this scenario supported by Cyrus? > > The folder hierarchy in Cyrus doesn't operate like a directory > hierarchy. If you create a sub-folder, it won't automatically be > placed on the same server as the parent folder. You'll have to move > the sub-folder to the archive server as well as rename it to be a sub- > folder of the archive folder.
What Andy said, But also... support for this layout isn't great in general. There's a bunch of stuff like quotas which expects everything for a single user to be on the same machine. Also replication, and probably a bunch of other stuff. I would really prefer not to keep supporting this scenario at all - it's going to play havoc with things like shared modseq and cross folder search/sort. At FastMail we are running patches which allow us to do archiving within each folder, such that the current week's email is on SSDs, and older email is stored on big slow disks. This won't be in 2.5, but I'm hoping to land both archiving support and support for moving emails off into a big object-storage engine for archival, and just fetching them back when requested. This will allow IMAP servers with a small amount of fast local storage to have big archival mailboxes without needing to manually manage moving them between machines or partitions. Bron. -- Bron Gondwana br...@fastmail.fm
