http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3838
------- Additional Comments From [EMAIL PROTECTED] 2006-02-13 16:19 ------- I have been plagued with this bug ever since upgrading SA to 3.1.0 on my server. Here are my particulars if it helps. I'm running FreeBSD 4.7-RELEASE-p28. This is a shared server and my mailbox is the only one I have detected that has this problem (other clients mention infrequent issues with SA but so far I haven't been able to tie it in with this bug). I run approx 2000 spams per day through the filter. All rules worked great in version 2.?? before. No errors or anything out of the ordinary in the --lint report. Due to the frustrating intermittent nature of problem, I finally set up a new server, fresh installation of SA v 3.1.0, fresh perl v 5.8.4. Ran email for 2 days without any cusomization without incident. Put customized procmailrc file in for a day without incident. Put in user_prefs file and it ran for approx 6 or 8 hours before the problem showed up. Same error in maillog file as others mentioned: spamd: Insecure dependency in eval while running setuid at /usr/local/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 913. Restarted spamd and all was well for a few hours. Again restarted spamd with similar result. Then I sat and swapped out parts of my user_prefs file. Removed whitelist (approx 50 entries) but no change. Removed all custom rules and SA began working again. Put back a few at a time until I was able to consistantly replicate the problem with 2 rules: # body PATENT_BIZ /based patent business/i score PATENT_BIZ -2.0 describe PATENT_BIZ Reduce score for someone with comments about my business # body YOUR_PATENT /your patents/i score YOUR_PATENT -2.0 describe YOUR_PATENT Reduce score for someone with comments about my patents # Without those rules, it has been working for over 24 hours without incident. I put those rules back in this morning, and the SA still works (this is a slippery bug!). My guess is that if I left those rules in, after a few hours it would again start skipping out again. <guess/speculation>It almost seems like a cumulative effect: I put the custom rules in that trigger problems and all is well for a while. After a certain threshhold, it suddenly shuts SA filters off. If I remove the problem rules, SA immediately works. If I quickly put them back, SA shuts off. If I leave the rules out for a period of time, whatever the problem was, clears out. Beyond that info, I don't know what else I can offer. I hope that helps. js ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
