Gary Smith wrote:
I'm not worried about it exploding as we don't allow user_prefs. The machines are processed via relays. I believe the bayes_sql_override_username will solve the last piece of the puzzle. I think I will test this out this weekend on the laptop, then our test environment.
'Exploding' as in 'sucking up far more disk than expected causing I/O saturation and grotty spam detection rates' (because by default, each calling user as provided by spamc will get its own Bayes records in SQL). In switching from an environment with a sitewide BDB file-based Bayes to sitewide SQL I ended up learning about that one the hard way. :/
There's no direct relation between user_prefs and a sitewide Bayes DB. -kgd
