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 traditional Maildir++ quota.
In any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 vusaged is a delivery agent, or that it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simone Lazzaris wrote:
No. I'm aware that vusaged is only a usage tracker daemon; my concern is that
I don't see the point of running a daemon which cannot possibly have
information on the usage short of performing du on a directory. Directory
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 vusaged is a delivery agent, or that it
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
-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,
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
-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
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
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
-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
-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
12 matches
Mail list logo