Aaron Bennett wrote:
On 06/29/2010 11:00 AM, Kris Deugau wrote:
Aaron Bennett wrote:
1) Are you supposed to have a global Bayes DB?
2) How many users do you have?
3) If the answer to 1) is "yes", did you set bayes_sql_override_username?
If the answer to 1) is no, you're probably not running Bayes expiry for
every user, so their individual sub-databases are growing without bound.
Better to re-enable auto-expiry (it's primarily a concern with global
databases, particularly with DB_File).
We are using amavis-maia so every bayes transaction is made under the
amavis user -- is that the same as a global database?
Mmm, usually, with a filter at that layer. Do you know if amavis-maia
passes messages to the SA libraries on a real per-user basis (ie,
similar manner to spamc -u) or just under the one systemwide logical
user? (IIRC another amavis variant can.) System users may not
necessarily map one-to-one with SpamAssassin "users".
The other thing to check to confirm whether you're really running as
globally as you think you are is:
mysql> select distinct id from bayes_token;
or
mysql> select count(*) from bayes_vars;
You should only get one row back from the first, or a count of one from
the second.
If you get "many"... Try setting bayes_sql_override_username
explicitly. You'll probably have to drop the table and recreate it (or
at least delete everything in it) to clear out the excess usage -
there's no convenient way to merge Bayes DBs that I know of.
-kgd
