http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5044
------- Additional Comments From [EMAIL PROTECTED] 2006-08-30 16:23 ------- <harried end-user perspective> "I think if we're going to load any plugins we should load whatever is configured in the local site dir pre files" hear! hear! when i build SA (currenly, svn trunk on OSX), i "mv" all the silly/extraneous .pre files (which i would recommend be renamed *.pre.README_YOU_SILLY_PONCE ...) and put into *my* init.pre what plugins i want to load. from my perspective, neither 72_active.cf nor 70_sandbox.cf, or anything else (yes, i've griped abt this elsewhere ...) should presume otherwise, or undertake to override my instructions. also, sa-update, imho, should recognize/honor *my* pluging config, whether it be in just init.pre, or spread across multiple *.pre. since it currently (apparently?) does not, sa-update (atm, of daryl's provided SARE channels), fails lint with a bunch of error messages. iiuc, as a result of not reading/loading the plugins from my config. bottom line(s) -- imho, the end user should be made aware of the plugin requirements in various readme's, wiki pages, documentation, etc., AND be responsible for properly config'ing/enabling plugins. all the automagic loadplugin/tryplugin should ALWAYS be conditional on the LACK of any user-specified override, not the other way around. </harried end-user perspective> my $0.02 ... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
