Ken Murchison schrieb:
I got a bit deeper in the code and I think there are some things worth to mention:No. The domain level of the hierarchy is not treated as a mailbox. I'd have to think about whether this is even possible.
As I saw in the code adding a quota for a domain would really mean to re-write a hole lot of code. The naming representation of mailboxes like user/account@domain looks a bit "unlucky" to me but seeing the code I know why things are the way they are ;-) Logging in as an admin things would be better if representation would really be something like /domain/user/account. I think it would be possible to create a domain with every IMAP-client without the need of having to run "mkimap -d domain" buy simply creating the domain-"folder" with the client in the root of the hierarchy. But that really means a lot of code-changes! As I saw the actual virtual domain support simply "copies" the underlying storage-hierarchy so that every domain looks like beeing an own cyrus installation. However this is not the desired way and the whole virtual domain support looks a bit squeezed into the existing code. The best solution to get a real tree hierarchy for virtual domain support would make it impossible to use the "old" spooling code so by now I think it is impossible to do the per domain quota with a quick and easy enhancement of the existing code. I can live with not beeing able to specify a domain-quota but what really drives me crazy is that I have to mkimap -d domain for every new domain. So changing the whole spooling mechanism would really bring advantages but it also means to re-write the complete code which nobody really wants to....Every time I've made a big change to the mailbox naming/structure (altnamespace, unixhiersep, virtdomains), I spend several days thrashing on the LIST/LSUB code.
--Christian--
<http://dict.tu-chemnitz.de/dings.cgi?o=3001&service=en-de&query=teeth>
