Thanks Eric. Wasn't sure if I was doing something wrong that was causing this problem, or if it was a bug. What type of issues are there with quotas? I'm sure I'll run into them eventually, but if I knew what to watch out for, it would definitely be helpful.

Totally understandable about the development of vpopmail...we're all fairly busy people these days, so it can certainly be difficult at times to dedicate enough time to any one thing ;-)

I'm actually kinda honored that you're asking if I'd like to help work on the vpopmail-toaster package. I must admit I'm still very much a beginner at all of this stuff with qmailtoaster, but I'm a quick learner and look forward to getting my experience in. With that being said...I'd love to help! Just let me know what you need done, and I'll do my best to figure out how to get it accomplished.

Thanks,

Casey

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>

On 10/2/11 12:01 AM, Eric Shubert wrote:
Thanks for taking the time to put together some documentation, Casey. We'll all look forward to seeing it.

In the present vpopmail-toaster-5.4.17-1.3.7, a couple pieces of the data in the vpopmail database are not always quite right. You've identified one of them, and quotas is another.

In the case of quotas, it is reportedly fixed in vpopmail-5.4.33, which has not yet been packaged for QMT (a vpopmail-toaster-5.4.33-1.3.8 package). We're hopeful that vqadmin will also once again work correctly with that version, which is rumored.

I'm not certain whether or not the particular error to which you refer has been identified or fixed in versions since 5.4.17. It would be inappropriate for the authors (the kind folks at inter7 who work on vpopmail, namely Matt Brookings) to try to fix anything like this in older versions, as his development time with vpopmail is limited. We'll need to upgrade to 5.4.33 and see if the problem persists in that version before reporting a bug, and getting it fixed.

I've already written a script that updates the database appropriately for upgrading from 5.4.17 to 5.4.27, but don't know if there are any database changes since that would require special processing for upgrading. That's pretty much where the process has stalled.

So how would you like to help getting vpopmail-toaster-5.4.33-1.3.8 put together?

Reply via email to