http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3838
------- Additional Comments From [EMAIL PROTECTED] 2006-02-14 10:29 ------- For me: Allow_user_rules, yup. Spamd, yup. I can not state absolutely that I've never heard of this happening *without* allow_user_rules; in fact I'm pretty sure I have a vague recollection of someone reporting a one-off that sounded suspiciously like this happening without allow_user_rules. However, that was one mysterious occurance vs *lots* of occurances with people that allow user rules. I've also observed that the problem seemes to run in a batch. No problem for a while, then several messages in a row would not be checked, then things worked again for a while. Even catching an unchecked message in procmail and sending it back through spamd, it would be uncaught (due to this failure) the second time. However, run it through spamassassin directly and there is a very good chance that the spam will be correctly caught. I was never able to tie it down to a rule since it was too sporadic. Never connected it to max children or max conns, but that is a good likely explanation. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
