> require_version n.n.n > Indicates that the entire file, from this line on, requires a certain > version of SpamAssassin to run. If a different (older or newer) version > of SpamAssassin tries to read the configuration from this file, it will > output a warning instead, and ignore it.
> Note: The version must be in the internal SpamAssassin version format > which is: x.yyyzzz. x is major version, y is minor version, and z is > maintenance version. So 3.0.0 is 3.000000, and 3.4.80 is 3.004080. I'd like to begin using this in the SARE rules files I maintain. How is this intended to be used? For instance, if I have a file which includes RULEA, suitable for all versions of SA, RULEB, which is an addition-based meta rule, therefore needing 2.50 or higher, and RULEC which greatly overlaps a new 3.0.0 rule and therefore should be used only in 2.xx versions, is it possible to create a file that looks like the following? Is there a better way to do this? Bob Menschel require_version 2.004000 RULEA RULEC require_version 2.004001 RULEA RULEC require_version 2.004002 RULEA RULEC require_version 2.004003 RULEA RULEC require_version 2.005000 RULEA RULEB RULEC require_version 2.005001 RULEA RULEB RULEC require_version 2.005002 RULEA RULEB RULEC require_version 2.005003 RULEA RULEB RULEC require_version 2.006000 RULEA RULEB RULEC require_version 2.006001 RULEA RULEB RULEC require_version 2.006002 RULEA RULEB RULEC require_version 2.006003 RULEA RULEB RULEC require_version 2.006004 RULEA RULEB RULEC require_version 3.000000 RULEA RULEB
