SA Bugzilla – Bug 6800
X-Spam-Checker-Version should also show what sa-update we are at
Last modified: 2013-02-28 18:13:03 UTC
The X-Spam-Checker-Version header should also show what sa-update we are at. Indeed the value of the latter is often more signifigant that that of the software itself.
A good idea IMO. Any chance you can submit a patch?
Thanks but "grandma lost the ability to sew long ago",
Created attachment 5074 [details] Collect rules versions and make them available through _RULESVERSION_ macro See the attached patch. It collects ruleset versions from their '# UPDATE version' lines, and makes them available through a macro _RULESVERSION_, which can be used in an add_header directive, e.g. (single line, mind the wraps) : add_header all Checker-Version SpamAssassin _VERSION_ (_SUBVERSION_) (_RULESVERSION_) on _HOSTNAME_ trunk: Bug 6800: X-Spam-Checker-Version should also show what sa-update we are at' Sending lib/Mail/SpamAssassin/Conf/Parser.pm Sending lib/Mail/SpamAssassin/Conf.pm Sending lib/Mail/SpamAssassin/PerMsgStatus.pm Committed revision 1346448.
Brilliant!
I just realized the grep is now redundant (a leftover from a version where I tried to correlate versions with filenames or restrict to a main channel). Removing it: trunk: Bug 6800 (removed a redundant grep) Sending lib/Mail/SpamAssassin/PerMsgStatus.pm Committed revision 1346458.
Does somebody feel like changing the 10_default_prefs.cf too to extend the 'add_header all Checker-Version', or do we leave it as an option to site managers? I'd prefer to keep it as it is, i.e. with the new code offering a macro RULESVERSION, but with unchanged default X-Spam-Checker-Version header field.
I'd call it a 'nice to have' so no need to change the default.
(In reply to comment #7) > I'd call it a 'nice to have' so no need to change the default. Concur +1
So this is done, closing.