Jake Vickers wrote:


I would rather use my old Bayes database, so I went ahead and changed the path in local.cf to point to the old database. If no one else has tried this (successfully or unsuccessfully), then I will port my results.

I also changed the auto-whitelist path back to the old path, and am getting this in my spamd logs:
2005-10-21 10:29:58.021444500 [5288] info: prefork: child states: II
2005-10-21 10:30:54.208533500 [5294] info: spamd: connection from localhost.localdomain [127.0.0.1] at port 32898 2005-10-21 10:30:54.211496500 [5294] info: spamd: processing message (unknown) for clamav:89 2005-10-21 10:30:54.383483500 [5294] error: auto-whitelist: cannot open auto_whitelist_path /etc/mail/spamassassin/.spamassassin/auto-whitelist: Inappropriate ioctl for device 2005-10-21 10:30:54.383590500 [5294] warn: auto-whitelist: open of auto-whitelist file failed: auto-whitelist: cannot open auto_whitelist_path /etc/mail/spamassassin/.spamassassin/auto-whitelist: Inappropriate ioctl for device 2005-10-21 10:30:54.383669500 [5294] error: Can't call method "finish" on an undefined value at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/Plugin/AWL.pm line 397. 2005-10-21 10:30:54.525250500 [5294] info: spamd: clean message (-2.3/6.5) for clamav:89 in 0.3 seconds, 2136 bytes. 2005-10-21 10:30:54.525489500 [5294] info: spamd: result: . -2 - BAYES_00 scantime=0.3,size=2136,user=clamav,uid=89,required_score=6.5,rhost=localhost.localdomain,raddr=127.0.0.1,rport=32898,mid=(unknown),bayes=2.22044604925031e-16,autolearn=ham
2005-10-21 10:30:54.602003500 [5288] info: prefork: child states: II

It looks like it can now not open the auto-whitelist DB. Alright, so I renamed it and let it start a new file. I still get the same error... I went ahead and did 'chown vpopmail:vchkpw' auto-whitelist and it seems to be working okay now. Anyone else have any thoughts on this?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to