9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Dynamic maild...
FromSent OnAttachments
Piotr RoszatyckiJun 12, 2001 6:45 am 
Sam VarshavchikJun 12, 2001 2:32 pm 
rolandJun 12, 2001 8:23 pm 
Piotr RoszatyckiJun 13, 2001 4:15 am 
Sam VarshavchikJun 13, 2001 4:54 am 
Piotr RoszatyckiJun 13, 2001 5:37 am 
Sam VarshavchikJun 13, 2001 2:51 pm 
Piotr RoszatyckiJun 19, 2001 6:09 am 
Sam VarshavchikJun 19, 2001 2:53 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: Dynamic maildirquota.Actions...
From:Piotr Roszatycki (Piot@netia.net.pl)
Date:Jun 19, 2001 6:09:21 am
List:net.sourceforge.lists.courier-users

Nope. In fact, if the quota already exists on the maildir, it will be checked.

But it isn't.

Then you need to create it.

Is it possible to force the Courier server to ignore maildirsize file and recalculate the Maildir size all the time? I would like to see it as an optional feature, not the default.

I'd like integrate Courier-IMAP with Exim MTA, and use the internal Exim's delivery agent and Exim's quota implementation. I.e. Exim has a special timeout if quota is exceeded. Just now it is not possible because Exim doesn't handle maildirsize cache file. I think the easier way is to hack the Courier-IMAP to not use the maildirsize file and to get the quota value from LDAP directly (or via MAILDIRQUOTA).

I've created maildir, delivered some mails then changed quota. After that the Courier-IMAP didn't noticed changes. AFAIK Courier always get the quota value from maildirsize file.

Correct.

I don't understand why it can't get it from MAILDIRQUOTA variable? authldap module sets this variable based on LDAP record.

There's a very big difference between initially creating a quota, and changing it. Quotas on accounts should not change very often. Therefore, if you decide to adjust the quota, you'll just have to manually fix maildirsize.

Other way to change quota value than changing LDAP database would be hard to implement.