From: Murray T. <mtr...@ce...> - 2006-01-30 08:28:20
|
On Mon, 2006-01-23 at 18:49, Jamie Cameron wrote: > On Mon, 2006-01-23 at 18:19, Murray Trainer wrote: > > On Thu, 2006-01-19 at 17:24, Murray Trainer wrote: > > > On Thu, 2006-01-19 at 16:11, Jamie Cameron wrote: > > > > On Thu, 2006-01-19 at 18:25, Murray Trainer wrote: > > > > > Hi Jamie, > > > > > > > > > > Just setting up the latest version of the module. We haven't used IMAP > > > > > quotas yet. I want a default Cyrus quota of 1GB for new users - what > > > > > format(s) do I enter that in the IMAP quota field - Bytes ,MB, GB? > > > > > Maybe which ever one(s) it is could be put in brackets - eg. Default > > > > > quota for new Cyrus users (MB). > > > > > > > > I am not 100% sure actually, as that value is just passed directly to > > > > the IMAP server via an IMAP command. However, I would guess that the > > > > size is in the bytes. > > > > > > > > As you might guess from looking at the module, I don't run a Cyrus IMAP > > > > server myself, so those parts of it that deal with IMAP are not too well > > > > tested :) > > > > > > I just noticed that the Cyrus IMAP Server module manages Cyrus mailbox > > > quotas - it uses Kb. I will let you know if I figure out what your > > > modules uses. > > > > > > Murray > > > > Hi Jamie, > > > > Just confirmed your module creates IMAP quotas in Kb. > > Thanks .. > > > It would be a useful for our company to have a quota field appear in the > > LDAP Users module containing the user's current quota so we can give > > them a larger one than the default if required. > > That would be nice .. but I don't know which IMAP command to use to > query the current quota. In fact, I don't think there is one .. > > - Jamie Hi Jamie, Despite their being an ability to manage IMAP quotas in the Cyrus IMAP Server module, we would still like to have a hard-coded IMAP quota field in the LDAP User's and groups module. Otherwise it will be a two step process for us to create users with IMAP quotas other than the default. On a related issue, we are using a few custom LDAP fields in the LDAP Users module but these fields would be much more useful if it was possible for the post user-creation script to directly access the values entered into these fields. It would be useful to be able to specify a variable for a custom LDAP field that is exported to the post user-creation script like all the USERADMIN_* ones. Eg. a custom LDAP field could be described as below in the module config as variable description $USERADMIN_CUSTOM_VAR1 and the module could parse out the $USERADMIN string if it finds one and to set the variable to the content of the field. If the field had multiple values then it would be up to our post-user creation script to parse out each value. This would make the module much more flexible for us and less likely to need more fields added to the module in the future. You may still want to add hard-coded fields in the future for attributes that all LDAP accounts are likely to need. Hope you think these suggested improvements have some merit. Regards Murray |