On 30 May 2019, at 10:57, Mike Ray wrote:
Hello all-
Been using spamassassin for awhile now, basically letting it run on
auto-pilot
and it's been great so far.
However, after the recent __STYLE_GIBBERISH bug
(https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7707), I need to
have a
little more understanding of SA.
The LATEST problem is actually in a different bug that is classified as
a "Security" bug, and so is not publicly visible.
My biggest issue at the moment is that I saw John's message last night
that said
an update would be pushed out with yesterday's update
(https://www.mail-archive.com/users@spamassassin.apache.org/msg104352.html).
However, this morning, the only way I was able to verify that, was by
looking at
his change
(https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/sandbox/jhardin/20_misc_testing.cf?r1=1857655&r2=1857654&pathrev=1857655)
and comparing that to the code currently running on my mail servers.
Is there any easier way to verify that a specific commit is in my
currently
running rule set?
Yes. Compare the first line of
/var/lib/spamassassin/3.004002/updates_spamassassin_org.cf to the
revision number of the commit.
