On Tue, 2008-07-15 at 18:17 +0800, Grandy Fu wrote:
> dovecot: Jul 15 18:13:21 Error: IMAP(01234567g): fcntl(0, F_GETFL)
> failed: Bad file number
> dovecot: Jul 15 18:13:21 Fatal: IMAP(01234567g): fd_set_nonblock(0)
> failed: Bad file number
Fixed: http://hg.dovecot.org/dovecot-1.1/rev/2bd9f6fe
I can't help you with this messages
> dovecot: Jul 15 18:13:21 Error: IMAP(01234567g): fcntl(0, F_GETFL)
> failed: Bad file number
> dovecot: Jul 15 18:13:21 Fatal: IMAP(01234567g): fd_set_nonblock(0)
> failed: Bad file number
It seems that they are produced by "int fd_set_nonblock(int fd, bool
So my understanding for now is this:
/var/mail
-
* has quotas
* for mailboxes hosted by this file system 'getrootquota' should
report used/total quota sizes.
/home/h1
* has or has not quotas. This is the same, because if 'homesvr'
doesn't support rquota, you
So my understanding for now is this:
/var/mail
-
* has quotas
* for mailboxes hosted by this file system 'getrootquota' should
report used/total quota sizes.
/home/h1
* has or has not quotas. This is the same, because if 'homesvr'
doesn't support rquota, you can't
Timo Sirainen wrote:
I think you should find out why that happens. Did you see Ralf's mail
about those questions?
I just did it, and replied in another mail.
noenforcing only makes Dovecot not verify quota when adding new mails.
And I just did a quick test - it didn't.
Actually, that is
It seems that a RPC call fails because rquotas are not supported on
'homesvr'. But dovecots quota-fs requires them for remote storage.
You may verify this also using perl:
perl -e 'use Quota; print Quota::rpcquery("homesvr", "/home"),"\n";'
To test if perl-Qouta will report any quotas for '/ho
