-----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 needs to know about
it's delivery agent to determine usage. It is not, and it does not. In the
most
simple form, it's just doing a 'du' on the directory.
> Removing the fprintf is ok for MY need, but can complicate the life of
> peoples
> who *does* want the vusaged to work, but forgot to set in place its
> configuration file, or have a syntax error in it.
> So maybe the best thing to do is put in place a configuration option that let
> the sysadmin choose the usage tracking backend, Maildir++ or vusaged
Actually, the original problem you reported was that the client_connect
connect()
errors were cluttering up your logs, and that a missing vusagec.conf caused the
client API to segfault. This had nothing to do with syntax errors in a
configuration
file, which would be reported regardless of whether you remove the fprintfs in
client_connect.
You're writing about concerns about superficial fprintfs in 5.4, a frozen
version, that's
why it makes sense to just comment out the fprintfs. 5.5 is a *much* different
version,
which treats the Maildir++ quota checking as broken, which it is.
- --
/*
Matt Brookings <m...@inter7.com> GnuPG Key FAE0672C
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqhINYACgkQIwet2/rgZyxi5ACfY7VIr6z7rpNAS6Rnxx0UHm/r
//oAoJMwvlXYQLqghQlWeMnbZ51VAkcF
=boVV
-----END PGP SIGNATURE-----
