Andrew Morgan wrote: AM> In the case of new mailbox creation, something must decide AM> which backend/partition to use. AM> I'm trying to think of a way the frontend could determine AM> which backends/partitions exist, but I don't think it can AM> currently. AM> Let's assume it could though... How would it pick which AM> backend/partition to create the mailbox on? At random? That is indeed the question that needs to be answered, and I think you're right that it's too complex and too deployment-specific a problem to be solved inside of Cyrus. The patch I posted earlier in this thread: http://lists.andrew.cmu.edu/pipermail/info-cyrus/2009-June/031173.html is a rough-and-ready means for the frontend to farm the decision out to something that _is_ competent to decide. In my world, that's pretty much always a perl script which interrogates OpenLDAP, but other people's scenarios may differ ;-) Cheers Duncan -- Duncan Gibb - Technical Director Sirius Corporation plc - control through freedom http://www.siriusit.co.uk/ || t: +44 870 608 0063 Debian Cyrus Team - https://alioth.debian.org/projects/pkg-cyrus-imapd/ ---- 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
