dovecot - Jul 2008 - 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 at fh-trier.de                    Fon: +49 651 8103 499
  WWW:    http://www.fh-trier.de/~beckerr        Fax: +49 651 8103 214
______________________________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6087 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080710/253e29fd/attachment-0002.bin>

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080712/10baece1/attachment-0002.bin>

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