We're looking to offer bulk storage to our users; essentially, just 
folders with large quotas on cheaper storage and a low priority backup 
schedule.

My initial thought was to create these folders under the user's Inbox, 
on a separate partition and with their own quota root; however, it seems 
pretty easy to break this (eg by renaming the folder, which moves it 
back to the default partition). It's tricky to control this with ACLs as 
subfolders inherit from their parents and we do want people to be able 
to delete those! I'm now thinking that this will have to be done with a 
separate hierarchy.

Presumably a lot of other sites are running a similar setup - I'd 
appreciate any advice on the best way to make this work. We're currently 
running 2.2.12, but mean to upgrade soon; if the ACL extensions in RFC 
4314 are useful then I can delay the bulk storage until the upgrade is done.

regards,
Adam Stephens.

-- 
--------------------------------
Adam Stephens
Network Specialist - Email & DNS
[EMAIL PROTECTED]

----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Reply via email to