I ran into the same problem. I think the problem lies with spamassassin because it queries the database for the settings of the user which is handling the mail at that moment. qmail-scanner runs as the qmailq user so that is the user who is queried. Normally you'd put the spamc line in the users dot-qmail file. At that moment delivery is done by qmail-local who runs as the local user and the database is queried for his/her settings.
For me the only solution was to put the spamc line in the dot-qmail files. An other option would be to put it in the defaultdelivery control file. Arno Steve Fulton wrote: > (Cross-posted to the SA list) > > Hi all, > > I configured SA to use SQL for the whitelist/blacklist etc. It is > called via Qmail-Scanner, which runs as a user called "qmailq". The > SQL lookups are occuring, but SA keeps searching for the user > "qmailq", not the user that is having the e-mail delivered. Here is > a log snippet: > > logmsg: connection from localhost.localdomain [127.0.0.1] at port > 35627 debug: retrieving prefs for qmailq from SQL server > logmsg: checking message > <[EMAIL PROTECTED]> for qmailq:99. > debug: running header regexp tests; score so far=0 > > Has anyone else run into this? Found a solution? > > -- Steve > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Qmail-scanner-general mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
