Re: [vchkpw] Possible Quota Bug

2008-05-05 Thread Kirill Klimov
On Friday 09 November 2007, Michael Johnson wrote: > I've recently noticed strange behavior with user quotas after an upgrade > to vpopmail 5.4.25 from 5.4.18. The upgrade also moved from the cdb > backend to the MySQL backend (due to locking issues I was experiencing). > > When delivering a mess

Re: [vchkpw] Possible Quota Bug

2007-11-16 Thread Rick Widmer
[EMAIL PROTECTED] wrote: i faced this problem only with version: 5.4.25, reverting back to version: 5.4.24 works fine. I think I may have this fixed. Could someone who has seen this try the CVS version of vpopmail? If not it may be a week or two before I have time to test it. Rick !

Re: [vchkpw] Possible Quota Bug

2007-11-10 Thread dhaval
> On Friday 09 November 2007, Michael Johnson wrote: >> I've recently noticed strange behavior with user quotas after an upgrade >> to vpopmail 5.4.25 from 5.4.18. The upgrade also moved from the cdb >> backend to the MySQL backend (due to locking issues I was experiencing). >> >> When delivering

Re: [vchkpw] Possible Quota Bug

2007-11-09 Thread Steve Cole
Michael Johnson wrote: What version and backend are you using? The better it can be narrowed, the easier it will be to determine what change broke it. For me, 5.4.25 with MySQL 5.0x I started to see this with *.25 but I did jump a number of versions when I took the plunge on .25. !DSPAM

Re: [vchkpw] Possible Quota Bug

2007-11-09 Thread Michael Johnson
Steve Cole wrote: > On Friday 09 November 2007, Michael Johnson wrote: >> I've recently noticed strange behavior with user quotas after an upgrade >> to vpopmail 5.4.25 from 5.4.18. The upgrade also moved from the cdb >> backend to the MySQL backend (due to locking issues I was experiencing). >> >>

Re: [vchkpw] Possible Quota Bug

2007-11-09 Thread Steve Cole
On Friday 09 November 2007, Michael Johnson wrote: > I've recently noticed strange behavior with user quotas after an upgrade > to vpopmail 5.4.25 from 5.4.18. The upgrade also moved from the cdb > backend to the MySQL backend (due to locking issues I was experiencing). > > When delivering a messag