Re: spamassassin sql lookup
On 7/18/06, Nigel Frankcom <[EMAIL PROTECTED]> wrote: Previous message aside, either the user name is wrong or the db for that user is empty I guess you are thinking about this line from my maillog: Jul 18 19:28:20 BlackPete spamd[24325]: bayes: not available for scanning, only 1 spam(s) in bayes DB < 20 I think the reason for this is that i'm using in my userprefs: bayes_min_ham_num 20 bayes_min_spam_num20 Do you have sql whitelist and user prefs enabled? Yes, I have sql whitelist and user prefs enabled. - Martin
spamassassin sql lookup
Hi I am using spamassassin-3.1.3 with bayes_pg.sql. Everything is working fine but in maillog it looks like spamassassin is making the bayes lookup 3 times for each email?? Also the postgres log shows 3 times lookup for each email. Is something wrong here or ... ?? Best regards, Martin tail -f /var/log/maillog | grep bayes Jul 18 19:28:20 BlackPete spamd[24325]: bayes: using username: a0002 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: database connection established Jul 18 19:28:20 BlackPete spamd[24325]: bayes: found bayes db version 3 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: Using userid: 13 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: not available for scanning, only 1 spam(s) in bayes DB < 20 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: database connection established Jul 18 19:28:20 BlackPete spamd[24325]: bayes: found bayes db version 3 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: Using userid: 13 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: not available for scanning, only 1 spam(s) in bayes DB < 20 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: database connection established Jul 18 19:28:20 BlackPete spamd[24325]: bayes: found bayes db version 3 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: Using userid: 13 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: not available for scanning, only 1 spam(s) in bayes DB < 20 Jul 18 19:28:20 BlackPete spamd[24325]: bayes: not scoring message, returning undef Jul 18 19:28:20 BlackPete spamd[24325]: bayes: DB expiry: tokens in DB: 152, Expiry max size: 15, Oldest atime: 1058995800, Newest atime: 1153243555, Last expire: 0, Current time: 1153243700 Best regards, Martin
Re: spamassassin and sql
On 7/6/06, Stuart Johnston <[EMAIL PROTECTED]> wrote: Martin Schiøtz wrote: > Hi > > I'm trying to setup spamassassin with postgres for with bayes_sql, > awl_sql, dcc, razor using sql user_pref etc. > > I have configured the database with: > http://spamassassin.apache.org/full/3.1.x/dist/sql/awl_pg.sql > wget http://spamassassin.apache.org/full/3.1.x/dist/sql/bayes_pg.sql > wget http://spamassassin.apache.org/full/3.1.x/dist/sql/userpref_pg.sql > > I'm using: > spamassassin-3.1.3 > postgresql-8.1.4 > > I can see that spamd is using the right sql user_pref but I get a lot > of postgres encoding errors when scanning mails. > From mailllog: > Jul 6 04:07:48 BlackPete spamd[4192]: bayes: tok_get: SQL error: > ERROR: invalid byte sequence for encoding "UTF8": 0xc829 > Jul 6 04:07:48 BlackPete spamd[4192]: bayes: _put_token: SQL error: > ERROR: invalid byte sequence for encoding "UTF8": 0xc829 > > I guess this has something to do with string-escaping in postgres. How > do I solv this problem? Do you have a line like this in your local.cf? bayes_store_module Mail::SpamAssassin::BayesStore::PgSQL I got this: bayes_store_module Mail::SpamAssassin::BayesStore::SQL but using PgSQL solved problem :-) - Martin :-)
spamassassin and sql
Hi I'm trying to setup spamassassin with postgres for with bayes_sql, awl_sql, dcc, razor using sql user_pref etc. I have configured the database with: http://spamassassin.apache.org/full/3.1.x/dist/sql/awl_pg.sql wget http://spamassassin.apache.org/full/3.1.x/dist/sql/bayes_pg.sql wget http://spamassassin.apache.org/full/3.1.x/dist/sql/userpref_pg.sql I'm using: spamassassin-3.1.3 postgresql-8.1.4 I can see that spamd is using the right sql user_pref but I get a lot of postgres encoding errors when scanning mails. From mailllog: Jul 6 04:07:48 BlackPete spamd[4192]: bayes: tok_get: SQL error: ERROR: invalid byte sequence for encoding "UTF8": 0xc829 Jul 6 04:07:48 BlackPete spamd[4192]: bayes: _put_token: SQL error: ERROR: invalid byte sequence for encoding "UTF8": 0xc829 I guess this has something to do with string-escaping in postgres. How do I solv this problem? Best regards, Martin
