On 11/17/2017 06:32 AM, David Jones wrote:
On 11/16/2017 05:09 PM, Richard Doyle wrote:
Update applied, no issues.
I saw 18 testers in my web logs for yesterday's $REV. Thanks to
everyone that are helping by testing.
On 11/16/2017 05:22 AM, David Jones wrote:
Great news! Last night's run finally produced a full 72_scores.cf. Big
thanks to Merijn van den Kroonenberg for helping track down the
remaining issues! There were about 3 rules difference which could be
expected with 8 months difference.
# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY
# wc -l 72_scores.cf
149 72_scores.cf
Now 149 lines and we were stuck at around 100 before.
https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/
WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE FEEDBACK. I
would like to enable DNS updates again for sa-update on Sunday or Monday
depending on the feedback.
REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz
(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang,
MailScanner, etc.)
I have applied this ruleset to my platforms and will monitor
scoring/blocking over the next couple of days.
On Tue, Nov 14, 2017 at 2:36 PM, John Hardin <jhar...@impsec.org
<mailto:jhar...@impsec.org>> wrote:
On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:
I am running SpamAssassin 3.4.1, and I have been trying to
update the DB
located on /var/lib/spamassassin/3.004001/ using
SA-UPDATE. But,
it has not
gotten an update in almost 2 weeks.
The rules update service has been down due to infrastructure
problems for a few months now. It is very close (like, this
week) to
being fixed.
New version today looks good. Keep testing and checking your scores to
make sure they look normal. Back in June when we tried going live with
sa-update, the scores were obviously low allowing spam through. This
time things look much better and very different. The new 72_scores.cf
is complete in size and number of lines (151).
cd /tmp
REV=1815423
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz
(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang,
MailScanner, etc.)
If I don't hear any objections or negative feedback in the next 36
hours, I will enable DNS updates tomorrow so sa-update will start
automatically updating rulesets on Sunday morning.
My thoughts on starting Sunday morning are based on this:
- sa-update won't update for most instances until later on Sunday
- no one would be able to tell of any problems until 24 or 48 hours
later anyway
- very low risk of problems after testing
I can wait until Monday morning if anyone else thinks we should wait one
more day. It's been broken for 8 months so what's one more day? :)
--
David Jones
