https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6283
--- Comment #3 from Daryl C. W. O'Shea <[email protected]> 2010-01-11 22:33:58 UTC --- Other than "don't do that", I can't think of any. I don't think it's been a commonly reported issue. The behaviour is described in the documentation: perldoc spamassassin ===== CONFIGURATION FILES The SpamAssassin rule base, text templates, and rule description text are loaded from configuration files. Default configuration data is loaded from the first existing directory in: /var/lib/spamassassin/3.002000 /usr/local/share/spamassassin /usr/local/share/spamassassin /usr/local/share/spamassassin /usr/share/spamassassin ===== /var/lib/spamassassin/3.002000 exists so that's where we load config. I'd say you could debug about it, but then if they're running with debug enabled they can see where the rules are being loaded from anyway. It may just come down to if you want your config loaded don't delete it. Of course, I may be open to something like "if the .../3.002000/ directory is empty don't use it". That only disallows the case where somebody wanted to load all of their config from a user prefs file (I'm not sure that would even be possible or work anymore). I admit that I'm not a fan of mucking with this code before a release though. I'd hate to introduce something that isn't portable. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
