Hi Kevin,
reading the quotas from LDAP is a good idea. The problem
is updating the used disc space somewhere. If you want to
store this information also on LDAP, it will need an update
for every incoming message. This is very problematic,
because usually, LDAP servers are not optimized for doing
updates. 1 or 2 updates pre seconds should not be a problem,
but many updates per second will stress your LDAP server.
This will not scale very well, it will be more complex if
you use replication.
Does it make sense to you to store the quota on LDAP and the
used disc space on a local file ? For me this doesn't seem
to be a good solution, because you have the data on 2 places.
Daniel Matuschek
Swisscom IP-Plus
-----Original Message-----
From: Kevin J. Menard, Jr. [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 27. Juli 2001 03:37
To: [EMAIL PROTECTED]
Subject: LDAP quotas
Hey guys,
I'm thinking about patching cyrus imapd to allow the reading of
quotas from ldap. Does this appeal to anyone? Does this even
make sense? Is this worth the trouble?
Any ideas/flames/suggestions would be greatly appreciated.
Or more interestingly, I'd like to be able to associate a mailbox
with a uid/gid and impose system quotas on it. Same as above.
Feedback is nice :)
--
Kevin
PS -- Is it just me, or do emails take like 3 hours to appear on this
list? Anyone know why? Kinda puts a damper on getting things done
quickly :)
