mailinabox
mailinabox copied to clipboard
mail-in-a-box
Quota
How does one restrict delivery to the Mailinabox with a quota? I'd like to make sure that the limiting factor happened earlier than the actual physical disk space in the instance because systems have an annoying tendency to crash if you allow the disk space to become full.
This would probably be the way to do it: http://wiki2.dovecot.org/Quota
Feel free to submit a pull request.
Hi,
We are setting up Mail-in-a-box at our workplace. I've been doing some tweaking here and there and I managed to set up a user-based quota (with a hardcoded default of 1GB per user, but of course this value can be changed to a sensible generic default).
The only thing left is to enable administrators to modify these settings in the administration panel, as soon as I complete this I will submit a pull request if this is OK with you.
Quota implementation is already working. Thank you @rainulf :sunglasses: Looking forward to the merge of @JoshData !
If anyone wants to try the quotas feature on v0.20, I have merged @rainulf's changes to a fork of the latest master commit da5497c:
SSH into your box and then:
$ git clone https://github.com/geminilabs/mailinabox mailinabox-quotas
$ cd mailinabox-quotas
$ git checkout feature/quotas
$ sudo setup/start.sh
A few things to note:
- This worked/works fine on my existing v0.20 box, but as always make a backup. If you use DigitalOcean, make a snapshot of your droplet before upgrading. Use at your own risk.
- I have not tested reverting from this fork back to the official master branch. However, as far as I can tell there should be no problems in doing so. The only thing not reversed when reverting is the new quota column that this feature adds to the
userssqlite database table. But if you do revert back to the official branch, the column will just be unused. - Quotas is a great feature for the server admin to curb disk space usage, but it's not so user-friendly for the user. If a user's quota is full and they are using an email client to sync their emails, they will get no notification that they have run out of quota space and they will not realize that emails being sent to them are getting returned to sender.
- Instead of implementing quotas, consider hosting on DigitalOcean and using a datacenter that supports Volumes. $0.10 per GB per month. https://www.digitalocean.com/products/storage/
Is this going to be implemented in the near future? Would love to see quotas :)
@mitchellurgero I don't think quotas will be ever be officially implemented. I suggest if using DigitalOcean, host your mail server 💧 on a server that supports Volumes. Working great over here, 50 GB volume for $5/month. You can choose a smaller volume size and grow as needed.
On Dec 2, 2016, 10:08 PM -0500, mitchellurgero [email protected], wrote:
Is this going to be implemented in the near future? Would love to see quotas :)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/mail-in-a-box/mailinabox/issues/58#issuecomment-264612092), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAIPG_9g6bYwmPMldUndXam4P1bzoXqyks5rEN0_gaJpZM4B7GcV).
Also, thanks for the response, but I will be hosting over 100 emails, and would like to limit each account specifically. :)
Can I at least install this modification on the latest 0.21?
The PR has merge conflicts.
Also it changes the layout of the database: https://github.com/mail-in-a-box/mailinabox/pull/665/files#diff-d55d822b8e6ccfbe30985a32aeaca9c6
So even if it might be mergeable for 0.21, it might not be for 0.xx. So if your are not comfortable with applying the patch set every time and possibly dealing with database layout changes, then no. Also if quota's do land, it might be a different implementation and you would have to provide an upgrade path yourself.
I personally don't need it, but quota is a safe and simple feature (postfix/dovecot plays with it very simply) that can be integrated with little friction. In terms of UI, it's only a question of adding a numeric input box, and the database update (which has to happen once).
So the real question, @JoshData what do you think needs to be done to make this PR 👌 to merge?
Solve one of the more pressing issues first (e.g. #514, #777, among others) and then we can talk about adding features!
PR is here #665 - I rebased it, and resolved conflicts. But it's not tested, because I currently don't have time.
I am fairly out to date with the state of this project, but I do still use mailinabox. Implementation of quota is simple, but it is really up to the maintainer which priority to take, or if this feature is even necessary.
for #514 - One option is Pydio. It has an open source version (I dont remeber the license it uses) but would be "simple" enough to swap out as it also supports SQLite.
Solve one of the more pressing issues first (e.g. #514, #777, among others) and then we can talk about adding features!
Is there any news on this feature? Or anyone knows how to do this? Thank you
