mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 00:46:03 +03:00
[GH-ISSUE #3254] Add a new quota handler #1817
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1817
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Toniob on GitHub (May 27, 2024).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/3254
Hi,
We already had private discussion with @tonioo about it. Instead of replacing the current method of handling quotas in Modoboa, should it be possible to add a switch for a new one ?
In my opinion, Modoboa shouldn’t try to handle the quotas. And the current method is too restrictive for my clients. Currently, I put a quota on domains I sell, but I don’t put restrictions on the number of identities or the size of each mailbox. As an admin, it’s ok, because I can create identities with a quota of 0. But if I declare a domain admin, they can’t do so, and they have to put a quota on each mailbox. And as Modoboa is reserving this space, the users are blocked and can’t create new accounts, even if the current used space on the filesystem doesn’t match the domain quota.
Is it possible to add a handler where Modoboa does nothing about the quota, except being a frontend to set them ? That way, everything is handled by dovecot.