https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8092
Greg Troxel <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Greg Troxel <[email protected]> --- The part I did not understand is that enable_compat is a declaration by the user that their rules are compatible with the new feature, and that the new feature should be partially off by default. I expected that without compat set, one would simply get the new names, only, and that you could turn on compatibility to function with the old names. In the future, this would fade and not need to be carried indefinitely, but I realize that can happen with rule changes. SO it would be good to say more loudly where the sense of the compat comes from, as I expect it will feel backwards to most people, but maybe that's just me. The new page is vastly improved - thanks! The remaining point that is not explained is how whitelist_from is handled. I know from discussions and reading that it is treated as a synonym for welcomelist_from, silently, and that this might change in 4.1. Right now the new page mostly talks about rules (which is the hard part, I realize), and doesn't give guidance about changing directives in local config. -- You are receiving this mail because: You are the assignee for the bug.
