Quote:I've taken the improved version for 1.0.5 as template. My opinion is those I've expressed in my post above. I think that an extra button overloads the interface, because in my opinion quotas are no settings that are used very often. Just ask yourself: Is it more likely that you change quotas or passwords? (Don't argue that you change passwords via web mailer)
In most cases the answer is: Passwords are changed more often. To argue from an intuitive view there should be an extra button for changing the password not for changing quota.
We should keep the interface simple and group all settings together. Besides that another point for keeping them together is the re-usability of code. Your stand alone solution uses most of the code which is used by the other settings. To have an efficient code design this would mean in the best case extracting all common code and make it usable for all settings. The end would be unnecessary complexity. After all the quota setting is just a small piece of code and just one tiny bit of all settings.
It seems that your users are better than mines
, we opted to do the button in a new column for better usability (the people keeped writing a new password every time the changed the quota).
The other reason of this approach is that there is another (not yet tested enough) patch that adds the space/% of mailbox ocupation in the mail accounts window.
It does require some changes on how dovecot stores that information tought.