Dovecot quota / webspace question

Hello,
the migration from courier to dovecot works very well -good job. but how is the handling of the mailquota now? i use rc4 and want to offer a mailpaket with 2gb mailbox, but how are the limits and the automatism behind that?

Quote from kilburn

I think we should aim at dropping courier support. Now that there's a clean way to migrate all the mailboxes without any kind of information loss, there is simply no reason to stick with courier anymore. Dovecot is a superior piece of software, that can do everything courier can, plus some extra things. Further, it performs better in general (a lot better in some cases).

I opposed to a dovecot transition in the past (on the other project). The reason was simple: in there, we supported older debian versions (lenny) and other oses/distros that did not include dovecot >=1.1. Until dovecot 1.1 there was no clean way to migrate existing mailboxes, so dropping courier support would have meant unclean migrations (with already downloaded mails being downloaded again by the clients). However, this is not an issue anymore because all of the imscp's supported distros/versions *do* have dovecot > 1.1.

AFAIK, the only reason courier is still supported in imscp is because nuxwin wanted to keep courier, arguing that "he was fine with it and didn't want to change". Since this is obviously not a sound reason, and nuxwin is not around anymore, my opinion now is that we should move forward, drop courier, and try to achieve the best panel behaviour we can.

In this case, there should be at least a per-domain maximum mailbox quota limit, just like there is one for the disk space. The only thing I am speaking about here is a new limit in the hosting plans, stating the maximum cumulative quota that can be assigned to mailboxes of each domain. This is, a limit of "1Gb" should allow for either a 1Gb mailbox or 10 100Mb mailboxes, but not a 10Gb mailbox.

Additionally, the panel should let admins choose if the mail space is intended to be counted towards the disk quota or not. If it is not, then mail space is only limited by the mail quota above, and is enforced in real time by dovecot. Otherwise, the nighly script will detect disk oversize in the nighly run and disable FTP access (just as it does right now).

Display More

Hello ;

When the cat is away, the mice dance ... Well, courier is also a great piece of software and more easy to maintain than dovecot and maybe more faster than dovecot too. Quotas can be implemented with both courier and dovecot.

For now we still install procmail for nothing. Installing such MDA without using it has not sense. Maildrop can replace procmail and be used for quotas.

To resume, and to make all users happy (it's our primary goal there), I'll implement quotas for both courier and dovecot.

Thanks

Yes you are right. I choose dovecot mainly while i can use sieve on serverside and the user could it use with an roundcube plugin, i have read. but if i talk to the dev i will notice that after migrating from courier the packages still there. is that purpose, or an mistake or what is behind that. if imscp doesnt need it after switching to courier could i deinstall it?
thx

Quote from Sunghost

Yes you are right. I choose dovecot mainly while i can use sieve on serverside and the user could it use with an roundcube plugin, i have read. but if i talk to the dev i will notice that after migrating from courier the packages still there. is that purpose, or an mistake or what is behind that. if imscp doesnt need it after switching to courier could i deinstall it?
thx

Hello ;

I would recommend you to update to last Git Master. Un-needed packages are removed automatically.

BTW: I would recommend you to wait tomorrow to update to last Git Master since I'll commit several important fixes that night.

Thank for using i-MSCP

Hi,
iam not so firm with git and other versioning systems but i understand that this is an beta or alpha. while iam using rc4 on my productiv server, ok i know there is an warning of that, but it works very well, but i wouldnt install an nightly build or how they are named. So my question and i think of all others here is how the quota system works on i-mscp. whitout testing i understand that:
- set the limit of space for an account which is for space, db and mail at all.
- the user can add i.e. more mailaccounts, but the overall quota set by reseller is the limit
- if one of these are over the quota, to have read something at 2 checks via cron which check this quota, whil send at 85% a warning1 and by 95% warning2 <- whould be nice to setup in i-mscp
- after that the space is locked?
- naturly if all added to one sum it must be under the limit of quota which is set by reseller, or?

But what is the maximum of Quota at all or in detail? (disk = disk, mail? mysql?), in dovecot.conf are a max of 1GB right?

ok as you see there are a lot of questions..

Hello,
no answers yet and still questions about Quota in i-MSCP. What is the last fact of that? I read and searched in the forum but found any news, am i right? My knowledge about so far, while using dovecot:
- Mail- and Filequota matches at all the hostingplan e.g. at all 10GB mail and web could added max to 10gb
- Mail is always working also when quota is exceeded, fileuploads not
- the quota in gui can only set in userarea, not in reseller nor in paneladmin
- the max size of quota set in gui is 2GB

All these facts right now? Thx for summarize

No answer until now thats bad. How can i change the quota of dovecot over 2GB? I found a old thread here, but what is actual and why the limit of 2GB?

Hello MuhKuh,
many thx for pointing me to that ;). Opened for 12 month - not bad. i conclude that only a few guys use the option of limitation ,). ok i will test it. what do you think about the other facts? they are still actual?