[vchkpw] Patch to disable vusaged

2009-09-03 Thread Simone Lazzaris
pmail. I will also be nice if (adding a return 0; at line 74, and a couple of curly braces around that) vdelivermail wouldn't segfault if the config file is missing or unparsable. Now, at version 5.4.28, if vusagec.conf is missing, the code try to proceed and segfault. Thanks for the attention -

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

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 i

Re: [vchkpw] Patch to disable vusaged

2009-09-04 Thread Simone Lazzaris
In data giovedì 03 settembre 2009 hai scritto: > 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

Re: [vchkpw] Patch to disable vusaged

2009-09-04 Thread Simone Lazzaris
In data venerdì 04 settembre 2009 hai scritto: > Simone Lazzaris wrote: > > Well, if I only put mail on the storage via vusaged, and only fetch mail > > via Maildir++, that means that the usage values will always be seriously > > wrong, right? > > Ah, you think that

[vchkpw] [SPAM] Bug in maildirquota.c

2014-01-31 Thread Simone Lazzaris
{ which fixes the problem. Any chance to incorporate the fix in the next version ? Thanks -- Simone Lazzaris QCom S.p.A. !DSPAM:52eb8a1334261024417156!

[vchkpw] [SPAM] Bug in maildirquota.c

2014-01-31 Thread Simone Lazzaris
{ which fixes the problem. Any chance to incorporate the fix in the next version ? Thanks -- Simone Lazzaris QCom S.p.A. !DSPAM:52eb8b0234261033718879!