[ postfixadmin-Feature Requests-3103847 ] make mailbox quota non-editable
Brought to you by:
christian_boltz,
gingerdog
Menu
▾
▴
[ postfixadmin-Feature Requests-3103847 ] make mailbox quota non-editable
|
From: SourceForge.net <no...@so...> - 2011-10-25 22:43:11
|
Feature Requests item #3103847, was opened at 2010-11-05 21:59 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=3103847&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Darek M (fafaforza) Assigned to: Nobody/Anonymous (nobody) >Summary: make mailbox quota non-editable Initial Comment: For an ISP type environment, it would be great if there was a way of setting a default quota for a domain, and any time a domain admin added a user, that quota would be applied to that specific user, but without the domain quota being able to set the per user quota when adding a new account. The last part could be easily configurable. The current domain quota appears to set the limit for all users combined, and if a user is added where the domain quota is exceeded, the new user addition is blocked. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2011-10-26 00:43 Message: The current code (2.3.x and SVN trunk) has two quota settings: - a quota per mailbox - a total quota for the domain (sum of all mailboxes) - (and a limit on the number of mailboxes per domain) If one of these is exceeded, user creation will be blocked. The only missing thing is hiding the input field for the quota when creating or editing a mailbox - but this shouldn't cause problems for ISP setups because it's only possible to enter a _lower_ quota than allowed. If you really want, replacing the input field for the quota with a hidden field is the easiest solution for now. I won't add a config option to hide the quota input field (we already have enough config options ;-) - but in future versions (not implemented yet) you'll be able to do this with a hook function that modifies $struct of MailboxHandler. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2011-04-10 19:33 Message: > The current domain quota appears to set the limit for all users combined, and if a user is added where the domain quota is exceeded, the new user addition is blocked. No, the current quota is per mailbox. New user addition is only blocked if you reach the number of allowed mailboxes for this domain. (However a patch to define a total quota for all mailboxes in a domain is available in the patches tracker, but not yet integrated.) > Required altering the 'domain' table to add a 'defquota' field of the same type as maxquota. maxquota contains exactly what you need, therefore the additional field shouldn't be necessary. > Please let me know if I should post a diff (using 2.3.2) I can't promise that we integrate your changes in the official code. But even if not, there might be people who need exactly the behaviour you have now and can use your patch. So: yes, please post the diff ;-) ---------------------------------------------------------------------- Comment By: Darek M (fafaforza) Date: 2010-11-12 21:24 Message: So I went ahead and hacked the code a bit to make it to my liking. Worked out very well. Per user quota for a domain is set at domain creation. Domain admins can see what the quota for new accounts will be but can't edit it. Required altering the 'domain' table to add a 'defquota' field of the same type as maxquota. Didn't want to mess with the existing domain quota stuff. Please let me know if I should post a diff (using 2.3.2) ---------------------------------------------------------------------- Comment By: Darek M (fafaforza) Date: 2010-11-05 22:02 Message: Spelling correction: "but without the domain quota being able to set the per user quota " should be "but without the domain admin being able to set the per user quota " Basically setting a limit in accounts and per account quota without a customer being able to change those limits. Only a super admin would. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=3103847&group_id=191583 |
