http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5171
------- Additional Comments From [EMAIL PROTECTED] 2007-02-05 15:41 ------- So the reason I pushed this to 3.1.9 originally is that there doesn't seem to be a consensus on whether or not this is a good idea that even solves the problem, if in fact there is a problem with the code. For instance, the same problem will exist if people comment out plugins and then get an update that doesn't properly have ifplugin conditionals around plugin-dependent rules and associated configs. This issue also, currently, doesn't impact 3.1 since the core eval rules are still in EvalTests.pm, and all of the plugin-dependent rules are enclosed in conditionals. So in short, I'm around a -0.8 on this patch -- I'd rather solve the problem correctly via conditionals than put in a kluge which doesn't really change the behavior in the long run. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
