Peter Peltonen wrote:
Hi,

On Sun, Nov 22, 2009 at 1:14 AM, Eric Shubert <[email protected]> wrote:
Bad news: quotas are broken on QMT. I'm not sure to what extent. Easy fix is
to change their account to unlimited. :(

Good news: quotas work better in a more recent vpopmail release (5.4.28 I
think) than what is in QMT. This is not a simple upgrade though, as I think
there is a small database change somewhere between QMT's version (5.4.17)
and 5.4.28.

Better news: quotas have reportedly been really fixed in vpopmail 5.5. I
will be working on packaging vpopmail-5.5 for QMT when it's available (with
LDAP), which I expect will be in the first quarter of '10.

Thanks for clarifying this. I now disabled the quota warning messages:

# mv /home/vpopmail/domains/.quotawarn.msg
/home/vpopmail/domains/.quotawarn.msg-notinuse

Is it really that badly broken, that I really should disable quotas
for every user or is disabling the warning message enough?

Best,
Peter


I honestly don't know the extent to which quotas are broken. I suppose they might work under some circumstances, but I'm not aware of what those circumstances are.

I also don't know what the best fix would be for all situations. For me, simply not using it is sufficient. If I really needed it, I think I'd check the vpopmail list archives to see what's known about the problem first. Then either attempt to upgrade to 5.4.28, or simply ride out the status quo and wait for 5.5 to become available.

--
-Eric 'shubes'


---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
     If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
    Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to