We're getting ready to set up a new mail server running dovecot 0.99.11 (CentOS 4) with maildir and filesystem quotas. I saw on the Dovecot web site that "hard filesystem quota can also be problematic." How problematic? What problems might we anticipate?
Thanks.
Josh Kelley
Josh Kelley wrote:
We're getting ready to set up a new mail server running dovecot 0.99.11 (CentOS 4) with maildir and filesystem quotas. I saw on the Dovecot web site that "hard filesystem quota can also be problematic." How problematic? What problems might we anticipate?
If you're about to set up, don't use such an old version. There were a LOT of fixes between 0.99.11 and 0.99.14 (the latest 0.99 release), many of which are quite important.
I have quotas enabled on my system (running 0.99.14... 1.0 is missing _one_ feature for me to migrate) and the only problem I see is that users don't get new mail delivered when they exceed their quota.
However, other people have noticed that users can not log in, and this is because Dovecot can't modify/extend its control files due to quota limits. As was just this week pointed out on the mailing list, you can add a CONTROL path to the mail env to specify where Dovecot is to create these files, thus avoiding the issue.
From what I recall, aside from the actual mail folder, you can additionally specify: INBOX= where to find the inbox (not sure if this is in 0.99) INDEX= where to create the indexes CONTROL= where to create other Dovecot control files
Check out http://wiki.dovecot.org/moin.cgi/MailLocation for some more details, or search this mailing list.
-- Curtis Maloney
Curtis Maloney wrote:
If you're about to set up, don't use such an old version. There were a LOT of fixes between 0.99.11 and 0.99.14 (the latest 0.99 release), many of which are quite important.
I usually prefer to just stick with what the distro provides, for simplicity, but if 0.99.14 is that much better than 0.99.11, I'll go ahead and upgrade.
However, other people have noticed that users can not log in, and this is because Dovecot can't modify/extend its control files due to quota limits. As was just this week pointed out on the mailing list, you can add a CONTROL path to the mail env to specify where Dovecot is to create these files, thus avoiding the issue.
I'll look into that. Thanks for the information.
Josh Kelley
V Pá, 10. 06. 2005 v 02:10, Curtis Maloney píše:
Are those features of specifying INDEX and CONTROL going to be permanent in dovecot or is it some temporary *hack* ???
However, other people have noticed that users can not log in, and this is because Dovecot can't modify/extend its control files due to quota limits. As was just this week pointed out on the mailing list, you can add a CONTROL path to the mail env to specify where Dovecot is to create these files, thus avoiding the issue.
From what I recall, aside from the actual mail folder, you can additionally specify: INBOX= where to find the inbox (not sure if this is in 0.99) INDEX= where to create the indexes CONTROL= where to create other Dovecot control files
Check out http://wiki.dovecot.org/moin.cgi/MailLocation for some more details, or search this mailing list.
-- Curtis Maloney
David Kmoch Technical University of Liberec Department of Applied Informatics Halkova 6, 461 17 Liberec
tel: +420 485 353 633 fax: +420 485 353 112
On Fri, 2005-06-10 at 16:00 +0200, David Kmoch wrote:
Are those features of specifying INDEX and CONTROL going to be permanent in dovecot or is it some temporary *hack* ???
Specifying them in default_mail_env will be removed and they're going to be made separate settings, but they will stay. They are pretty much the only possible 100% working solution to fix filesystem-level quota problems.
On Tue, Jun 14, 2005 at 12:24:36PM +0300, Timo Sirainen wrote:
On Fri, 2005-06-10 at 16:00 +0200, David Kmoch wrote:
Are those features of specifying INDEX and CONTROL going to be permanent in dovecot or is it some temporary *hack* ???
Specifying them in default_mail_env will be removed and they're going to be made separate settings, but they will stay. They are pretty much the only possible 100% working solution to fix filesystem-level quota problems.
Or 99% :-) Note that there are some systems where moving messages from 'new' to 'cur' can trigger a quota issue because of failure to increase the directory size. I suppose this doesn't necessarily cause a failure though, if you simply leave the messages in 'new' in this case, if messages can still be accessed/deleted out of the 'new' directory.
mm
On Tue, 2005-06-14 at 09:57 -0400, Mark E. Mallett wrote:
On Tue, Jun 14, 2005 at 12:24:36PM +0300, Timo Sirainen wrote:
On Fri, 2005-06-10 at 16:00 +0200, David Kmoch wrote:
Are those features of specifying INDEX and CONTROL going to be permanent in dovecot or is it some temporary *hack* ???
Specifying them in default_mail_env will be removed and they're going to be made separate settings, but they will stay. They are pretty much the only possible 100% working solution to fix filesystem-level quota problems.
Or 99% :-) Note that there are some systems where moving messages from 'new' to 'cur' can trigger a quota issue because of failure to increase the directory size. I suppose this doesn't necessarily cause a failure though, if you simply leave the messages in 'new' in this case, if messages can still be accessed/deleted out of the 'new' directory.
That is pretty much the same problem as with read-only maildirs. Dovecot handles that already :)
participants (5)
-
Curtis Maloney
-
David Kmoch
-
Josh Kelley
-
Mark E. Mallett
-
Timo Sirainen