Re: [Dovecot] dovecot Digest, Vol 63, Issue 30
It seems that a RPC call fails because rquotas are not supported on 'homesvr'. But dovecots quota-fs requires them for remote storage.
Yes, my homesvr does not support RPC rquotas. Acutally I really don't want Dovecot to handle quota on my home directory, I only want Dovecot to hand quota on /var/mail. That's why I put "noenforcing" in configuration file. If I didn't put "noenforcing", Dovecot can't even display quota information on /var/mail.
My question is isn't "noenforcing" can tell Dovecot to ignore that mount point? It works when querying quota status but not when modifying mail folder on that mount point.
Grandy
mmmh...
so you are using:
plugin { quota = fs:INBOX:mount=/var/mail quota2 = fs:home:noenforcing:mount=/home/h1 }
but "fs:home:noenforcing:mount=/home/h1" will not work and you just added it do make "fs:INBOX:mount=/var/mail" work? Maybe it's worth to have a closer look to this first:
Test 1)
Use:
plugin { quota = fs:INBOX:mount=/var/mail #quota2 = fs:home:noenforcing:mount=/home/h1 }
What output generates:
telnet <your-imp-server> 143
- login <your-login-name> <your-password>
- getguotaroot "INBOX"
- getquotaroot "Trash" . logout
Test 2)
Use:
plugin { quota = fs:INBOX:mount=/var/mail #quota2 = fs:home:noenforcing:mount=/home/h1 }
What output generates:
telnet <your-imp-server> 143
- login <your-login-name> <your-password>
- getguotaroot "INBOX"
- getquotaroot "Trash" . logout
Test 3) Use:
plugin { quota = fs:INBOX:mount=/var/mail quota2 = fs:home:noenforcing:mount=/home/h1 }
What output generates:
telnet <your-imp-server> 143
- login <your-login-name> <your-password>
- getguotaroot "INBOX"
- getquotaroot "Trash" . logout
BTW: I've you don't like to send your password unencrypted use this instead of 'telnet <your-imp-server> 143':
openssl s_client -connect <your-imp-server>:993
Regards, Ralf
Grandy Fu schrieb:
It seems that a RPC call fails because rquotas are not supported on 'homesvr'. But dovecots quota-fs requires them for remote storage.
Yes, my homesvr does not support RPC rquotas. Acutally I really don't want Dovecot to handle quota on my home directory, I only want Dovecot to hand quota on /var/mail. That's why I put "noenforcing" in configuration file. If I didn't put "noenforcing", Dovecot can't even display quota information on /var/mail.
My question is isn't "noenforcing" can tell Dovecot to ignore that mount point? It works when querying quota status but not when modifying mail folder on that mount point.
Grandy
--
Dipl.-Inform. (FH) Ralf Becker Rechenzentrum (r/ft) der FH Trier (Network|Mail|Web|Firewall) University of applied sciences Administrator Schneidershof, D-54293 Trier
Mail: beckerr@fh-trier.de Fon: +49 651 8103 499 WWW: http://www.fh-trier.de/~beckerr Fax: +49 651 8103 214
On Thu, 2008-07-10 at 18:47 +0800, Grandy Fu wrote:
It seems that a RPC call fails because rquotas are not supported on 'homesvr'. But dovecots quota-fs requires them for remote storage.
Yes, my homesvr does not support RPC rquotas. Acutally I really don't want Dovecot to handle quota on my home directory, I only want Dovecot to hand quota on /var/mail. That's why I put "noenforcing" in configuration file. If I didn't put "noenforcing", Dovecot can't even display quota information on /var/mail.
I think you should find out why that happens. Did you see Ralf's mail about those questions?
My question is isn't "noenforcing" can tell Dovecot to ignore that mount point? noenforcing only makes Dovecot not verify quota when adding new mails. And I just did a quick test - it didn't.
It works when querying quota status but not when modifying mail folder on that mount point.
Bu "querying quota status" you probably mean querying the first quota (getquotaroot inbox). However if you try to query the second quota root (e.g. getquotaroot Trash) that'll definitely fail.
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 what I need, adding new mails without verifying quota. If it is not working, it will be a pity.
My requirement is simple. I have multiple mount points for different mail folders, there are mount points need to check "fs" quota, and ignore the rest. I though "noenforcing" is for such purpose, but seem not.
Grandy
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 check or even ignore them.
- for mailboxes hosted by this file system 'getrootquota' should report nothing.
If this is correct, this problem should be covered by a patch I've send to Timo two days ago. You may have a look at this:
http://dovecot.markmail.org/message/7e6bev4l3hen57ii?q=Multiple+quota+roots+...
Ralf
Grandy Fu schrieb:
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 what I need, adding new mails without verifying quota. If it is not working, it will be a pity.
My requirement is simple. I have multiple mount points for different mail folders, there are mount points need to check "fs" quota, and ignore the rest. I though "noenforcing" is for such purpose, but seem not.
Grandy
--
Dipl.-Inform. (FH) Ralf Becker Rechenzentrum (r/ft) der FH Trier (Network|Mail|Web|Firewall) University of applied sciences Administrator Schneidershof, D-54293 Trier
Mail: beckerr@fh-trier.de Fon: +49 651 8103 499 WWW: http://www.fh-trier.de/~beckerr Fax: +49 651 8103 214
participants (4)
-
dovecot@dovecot.org
-
Grandy Fu
-
Ralf Becker
-
Timo Sirainen