I am running spamassassin 2.55 out of spamass-milter 0.2.0, and I recently had a problem in which spamd went crazy because it couldn't write to a user's Bayes journal. Is there a way to have spamd give up if it can't write to the journal? Below are detail of exactly what happened.
As I said, spamassassin is run out of spamass-milter, which uses spamc to pass e-mails to spamd for tagging. I have a user who filled her quota. Normally sendmail would have refused to accept e-mails for this user, but with spamass-milter, spamassassin runs before sendmail has had an opportunity to reject the mail. So when the user received an e-mail that was auto-learned as spam or ham by spamassassin, spamd went into loops trying to write to that user's bayes_journal. It failed, and filled /var with millions of log file entries of the form: spamd[9644]: partial write to Bayes journal /home/foouser/.spamassassin/bayes_journal ( of 205), recovering. Spamd didn't fail, but the same process tried over and over to write to bayes_journal. Is there a way to make spamd just give up if it can't write to the bayes_journal? -- Any help will be greatly appreciated, Jeff Lessem. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
