https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7645
--- Comment #19 from Henrik Krohns ---
Origin of the warning seemed to be from fixup_re which created utf8 encoded
strings, should be silenced now. Judging from sa-compile temp files, nothing
changed, so nothing should break (assuming the
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7962
--- Comment #3 from Henrik Krohns ---
Some quick benchmarks with 100 emails
sa-compile stock
18.47user 0.15system 0:18.62elapsed 99%CPU (0avgtext+0avgdata
129804maxresident)k
18.49user 0.11system 0:18.61elapsed 99%CPU (0avgtext+0avgdata
HTTP get: https://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/3-days-ago?xml=1
Bad performing rules, from the past 3 night's mass-checks.
(Note: 'net' rules will be listed as 'no hits' unless you
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7962
Henrik Krohns changed:
What|Removed |Added
Summary|[review] Deprecate |Deprecate sa-compile in
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7962
Henrik Krohns changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7645
--- Comment #20 from Henrik Krohns ---
Now UTF-8 rules might actually work:
Sending
spamassassin-3.4/lib/Mail/SpamAssassin/Plugin/BodyRuleBaseExtractor.pm
Sendingspamassassin-3.4/sa-compile.raw
Sending