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 sql lookup
Do you have sql whitelist and user prefs enabled? On Tue, 18 Jul 2006 20:18:12 +0200, Martin Schiøtz [EMAIL PROTECTED] wrote: 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 sql lookup
Previous message aside, either the user name is wrong or the db for that user is empty On Tue, 18 Jul 2006 20:18:12 +0200, Martin Schiøtz [EMAIL PROTECTED] wrote: 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