Hey Folks, I have a few questions regarding SpamAssassin's SQL preference support...
First of all, is there any particular reason why "only local scores, whitelist_from(s), required_hits, and auto_report_threshold" are recognized options that may be stored in a database for later retrieval (although, I believe all_spam_to seems to work as well)? I could certainly understand most any philosophy behind this, but I still find myself questioning why these are the only options supported in ~/.spamassassin/user_prefs (unless I am badly mistaken, which is entirely possible). Regardless, it might be handy to allow users to disable or change certain site-wide preferences for their own use through a web-based configuration portal, especially if SpamAssassin is installed on a machine with virtual e-mail hosts--which brings me to my next question/point. The query SpamAssassin uses to extract user data from a database works fine--if you're using MySQL. I noticed in the documentation for MySQL that, "string comparisons are normally case-insensitive..." which can make portability an issue when dealing with other databases such as PostgreSQL or Oracle--neither of which support case-insensitive queries in the same fashion MySQL does. For this reason, I believe MySQL has the unfortunate side-effect of making most nearly everyone who uses it quite lazy. I don't mean to sound as though I'm griping--it's easy enough to change--but since both PostgreSQL and Oracle require that ILIKE be used within a string comparison if case-insensitivity is desired, per-use configurations can easily be defeated if the username/e-mail of the user is not already lower-case'd by the time spamc is called. The latter is only a problem in my case precisely because of the fact that I am using qmail-scanner-queue modified to the extent where it passes the recipient e-mail address directly to spamc. I realize it would be reasonably easier (and more portable) to modify qmail-scanner-queue to lower-case the address. Unfortunately, since MySQL behaves a bit differently from other RDBMS's, I'm not certain who else may have had similar problems who--like me--subscribes to that "other religion" (PostgreSQL, Oracle, etc.). Anyway, apologies for the rather lengthy, "blabbery" message. I was in the process of writing an almost-idiot-proof web-based interface for configuring per-user preferences for SpamAssassin when it dawned on me that half of the options I had added weren't going to work. So, if I am missing something so terribly obvious that I have been downgraded from "moron" to "idiot," then by all means give me a swift kick to the posterior :-) -- Benjamin Shelton "What do you mean it won't turn on? Did you plug it in?" *silence* ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
