That's not mutually exclusive, and is actually somewhat inclusive. I mean, if people are using the spamassassin script on a low-volume basis, then there's a low volume of SQL/LDAP lookups, so the complaint is nulled.
True, but it's also intended for users who aren't sophisticated enough to run a daemon, in which case they aren't sophisticated enough to run SQL.
However, you don't appear to be using the spamassassin command line anyway.
I'm using a third-party script for the in-line proxy, and it daemonizes spamassassin on its own.
at which point the addition to the spamassassin command-line becomes irrelevant, because you aren't using spamassassin. (it's impossible to daemonize the spamassassin command line tool.)
You need it added to your third-party script, as, based on your description, it's invoking the SA perl API's directly.
