Hey folks, I'm finishing up a mailserver upgrade this weekend, and I notice that my new SQL-based install isn't picking up on user-based Bayes data. This is on a new, squeaky-clean OpenBSD 4.0-STABLE machine running on AMD64, using SpamAssassin 3.1.7 with perl 5.8.8.
As per spamd -D info: 2006-12-03 22:41:53.760956500 [12889] dbg: config: retrieving prefs for [EMAIL PROTECTED] from SQL server OK, yay, spamd is picking up on the SQL userprefs. 2006-12-03 22:41:53.772480500 [12889] dbg: info: user has changed Not sure what this means? 2006-12-03 22:41:53.774209500 [12889] dbg: bayes: using username: [EMAIL PROTECTED] 2006-12-03 22:41:53.781308500 [12889] dbg: bayes: database connection established 2006-12-03 22:41:53.786485500 [12889] dbg: bayes: found bayes db version 3 2006-12-03 22:41:53.789654500 [12889] dbg: bayes: unable to initialize database for [EMAIL PROTECTED] user, aborting! 2006-12-03 22:41:54.117388500 [12889] dbg: bayes: not scoring message, returning undef 2006-12-03 22:41:54.118260500 [12889] dbg: bayes: opportunistic call attempt failed, DB not readable Uh. What does "unable to initialize database" mean? Spamd has already successfully connected to the PostgreSQL database above, right? So what does "initializing database" mean? My user_scores_sql_custom_query is as follows, if that makes a difference (not sure if that's consulted for Bayes data): user_scores_sql_custom_query SELECT preference, value FROM userpref WHERE username = _MAILBOX_ OR username = _USERNAME_ OR username = '$GLOBAL' ORDER BY user name ASC; To add insult to injury, learning spam and ham work just fine. It's just the Bayes scoring that seems to have issues. So. I'm at a loss at the moment... My SA install is doing well, but not as well as it should, if it's ignoring Bayes. What info can I pass along to help diagnose this problem? Thanks much! Benny -- "If stupidity were a handicap, you'd have the best parking spot." --Bill Paul