Re: [vchkpw] Released updated 5.4.28 tarball on SourceForge

2009-09-03 Thread Harm van Tilborg
Hi Matt, That counter is not really working properly, since I at least downloaded the `previous' 5.4.28 release about 10 times I guess. Btw: I'm looking into my personal vusage `symbolic link problem'. Like I said: the individual user usage's are computed correctly. However, if I request

Re: [vchkpw] Released updated 5.4.28 tarball on SourceForge

2009-09-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harm van Tilborg wrote: That counter is not really working properly, since I at least downloaded the `previous' 5.4.28 release about 10 times I guess. Really? That's no good. Their file release system has been pretty broken since the new

[vchkpw] Patch to disable vusaged

2009-09-03 Thread Simone Lazzaris
Hi everybody; we are using vpopmail in a deployment which involves many programs. We use maildrop for some (but not all) deliveries, dovecot for imap access, some custom perl script to forward some mail. Log story short, we cannot use (at the moment) vusaged to track the mail usage. I've looked

Re: [vchkpw] Patch to disable vusaged

2009-09-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simone Lazzaris wrote: Hi everybody; we are using vpopmail in a deployment which involves many programs. We use maildrop for some (but not all) deliveries, dovecot for imap access, some custom perl script to forward some mail. Log story short,

Re: [vchkpw] Patch to disable vusaged

2009-09-03 Thread Simone Lazzaris
In data giovedì 03 settembre 2009 hai scritto: Simone Lazzaris wrote: Hi everybody; we are using vpopmail in a deployment which involves many programs. We use maildrop for some (but not all) deliveries, dovecot for imap access, some custom perl script to forward some mail. Log story

Re: [vchkpw] Patch to disable vusaged

2009-09-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simone Lazzaris wrote: Our setup is spreaded on many servers (think 20), with the mail stored on an NFS share (NetApp). The vusage daemon is written with this in mind, though it's more efficient to have it run on the device providing storage so

Re: [vchkpw] Patch to disable vusaged

2009-09-03 Thread Simone Lazzaris
In data giovedì 03 settembre 2009 hai scritto: Simone Lazzaris wrote: Our setup is spreaded on many servers (think 20), with the mail stored on an NFS share (NetApp). The vusage daemon is written with this in mind, though it's more efficient to have it run on the device providing storage

Re: [vchkpw] Patch to disable vusaged

2009-09-03 Thread Tonix (Antonio Nati)
Simone Lazzaris ha scritto: In data giovedì 03 settembre 2009 hai scritto: Simone Lazzaris wrote: Our setup is spreaded on many servers (think 20), with the mail stored on an NFS share (NetApp). The vusage daemon is written with this in mind, though it's more efficient to have

Re: [vchkpw] Patch to disable vusaged

2009-09-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simone Lazzaris wrote: Ok, but how can be syncronized the two vision of the quota, if only vpopmail uses vusaged ? I think that there can be only two cases 1) all tools use vusaged or 2) all tools use traditional Maildir++ quota. In any other

[vchkpw] Re: Patch to disable vusaged

2009-09-03 Thread Eric Shubert
Tonix (Antonio Nati) wrote: I did not imagine vusaged was so intrusive! Is should be completely disabled if not needed. Tonino -- Matt, Is there some sort of specification documentation for vusaged that describes how it works? If there is, I think it would be useful to have it published

Re: [vchkpw] Patch to disable vusaged

2009-09-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tonix (Antonio Nati) wrote: Besides vpopmail, there are a lot of other important tools (like dovecot for example) which as far as I know are not using vpopmail, and rely on Maildirs. When the old domain quota code was going to be released, I

Re: [vchkpw] Re: Patch to disable vusaged

2009-09-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Shubert wrote: Is there some sort of specification documentation for vusaged that describes how it works? If there is, I think it would be useful to have it published so that it can be scrutinized by the community. Better to get things worked

Re: [vchkpw] Released updated 5.4.28 tarball on SourceForge

2009-09-03 Thread Harm van Tilborg
Hi Matt, Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harm van Tilborg wrote: That counter is not really working properly, since I at least downloaded the `previous' 5.4.28 release about 10 times I guess. Really? That's no good. Their file release system has been

[vchkpw] Re: Patch to disable vusaged

2009-09-03 Thread Eric Shubert
Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Shubert wrote: Is there some sort of specification documentation for vusaged that describes how it works? If there is, I think it would be useful to have it published so that it can be scrutinized by the community. Better

Re: [vchkpw] Released updated 5.4.28 tarball on SourceForge

2009-09-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harm van Tilborg wrote: No, it's really 'rubbish' :]. I've posted this in the 'some experiences with 5.5' thread before, but here we go: My apologies :) [cv] ~# ls -l /home/vpopmail/domains/example.com total 28 drwx-- 3 vpopmail vchkpw 4096