tor, 30.06.2005 kl. 11.46 skrev Jasper Slits:
I am not sure if it's a bug but I know more people experienced this
situation as well.
Current setup:
maildrop 1.8.1 using courier-authlib with MySQL as its backend.
Postfix is used as SMTP-server and I am using pipe (virtual_transport)
to talk to maildrop. I am not using quota warnings yet.
The following situation doesn't work as expected:
1. Virtual user jo...@domain.com has a quota of 5000000S (5MB)
2. The user reached his quota. (maildirsize is created).
3. I increase his quota in the database to 10000000S (10MB).
4. I send him an e-mail of 1MB.
[Expected behavior]
Maildrop sees that his new quota differs from the one in maildirsize and
updates the maildirsize before trying to deliver the e-mail.
[Actual behaviour]
Mails remains in the queue because the user is over his 5MB quota.
I need to manually remove the 'maildirsize' file from the user's homedir
and force a queue run (postqueue -f) for immediate delivery.
I'm using maildrop 1.8.1, true enough with LDAP and not MySQL, but that
shouldn't make any difference ;)
All you have to do is wait a few minutes (5-10) after increasing the
quota and sending the next message. This has always been the case since
I started using maildrop (a couple of years ago?). If it hadn't been so,
*many* others would have complained long ago. I've been using using
maildrop in production on a site with 1150+ users for the last year, a
few of whom exceed their quotas, and adding to their quota - or the user
pruning and purging his Maildir - has always worked for me.
I was looking around in maildirquota.c to implement the expected
behavior. What would be the right function to patch?
IMHO no patching necessary.
--Tonni
4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Quota increasing issue
