It seems that it was some sort of file permission problem that prevented the creation of bayes_journal.
Spamd was running as root, which probably isn't the best way to do it anyway. So rather than trying to fix the permission problem, I'm now running spamd chrooted, and the problem has gone away. Thanks. -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Monday, September 27, 2004 10:16 AM To: Tan, William; users@spamassassin.apache.org Subject: Re: Problem with bayes autolearn on 3.0.0 At 09:39 AM 9/27/2004 -0400, Tan, William wrote: >I'm having a problem with autolearn on a newly installed system. It >seems >as though the Bayes database is not recognized. I get messages about >autolearn failing like this: > >Sep 27 02:16:00 host spamd[2113]: result: Y 22 - >COMBINED_FROM,DCC_CHECK,DIGEST_MULTIPLE,MIME_BOUND_DD_DIGITS,RAZOR2_CF_ RANGE_51_100,RAZOR2_CHECK,SARE_HEAD_SPAM,SPF_HELO_PASS,URIBL_AB_SURBL,UR IBL_OB_SURBL,URIBL_SC_SURBL,URIBL_WS_SURBL,X_MESSAGE_INFO >scantime=11.5,size=1533,mid=<[EMAIL PROTECTED]>,autolear n=failed > autolearn=failed does not usualy mean a catastrophic failure. If another process is already writing the bayes database, SA will skip learning rather than logjam your mail queue waiting for the lock. This is a "failure" of a one-shot, non-critical operation. However, if *all* of your messages get failed, and none are ever autolearned at all, you might have a bayes DB the spamd process can't get RW access to.
