http://bugzilla.spamassassin.org/show_bug.cgi?id=4317
------- Additional Comments From [EMAIL PROTECTED] 2005-06-08 11:03 ------- Subject: Re: old user_prefs files now fail --lint due to ok_languages being optional On Wed, Jun 08, 2005 at 10:09:30AM -0700, [EMAIL PROTECTED] wrote: > specifically, settings that *were* part of core, but moved to optional but > disabled-by-default plugins in a later release. This will also confuse users and net us a bunch of tickets: - I have [insert config here] set in my local.cf, and --lint doesn't show any errors, but the setting isn't working. Why not? Then we'll have to explain that the plugin isn't loaded, but we accept and ignore the old options. I'd rather have stuff not work, then when they run --lint it tells them that old options aren't available anymore. If we didn't ignore the option, we'd have to alert the user about it (which I think is a bad idea, it should be --lint only imo), which we already do: [32511] info: config: failed to parse line, skipping: ok_languages en Granted, instead of saying it failed to parse it could say "X functionality moved to plugin", but that's not going to help most people anyway. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
