On 26/01/2011 10:12 PM, Kevin A. McGrail wrote:
On 1/26/2011 5:39 PM, Karsten Bräckelmann wrote:
Just came up on the users list. Escalating. ;) The facts:
1.3.3.updates.spamassassin.org descriptive text "1052462"
2.3.3.updates.spamassassin.org descriptive text "1052462"
Rule update tarball available on mirrors. 4 weeks old revision from
trunk.
0.3.3.updates.spamassassin.org descriptive text "1061118"
Tarball NOT available. 6 days old revision from tags, not trunk.
Not quite sure why 3.3.0 would be different from 3.3.1+2 would be
different, but the reason we haven't had any stable branch rules
published in a while is that we haven't had enough *recent* spam
submitted. Last nights cron job says:
HAM: 188008 (150000 required)
SPAM: 51330 (150000 required)
Insufficient spam corpus to generate scores; aborting.
Ever since my main corpus server hard drive failed in October my corpus
hasn't had spam being added to it so my spam corpus finally aged out a
few weeks ago. I guess I need to get this fixed, but we also need more
spam from others.
Moreover, the dostech mirror currently is unresponsive, serving neither.
Bah, I'm running into issues Infra had back when they were using VMware
Server 1.0.x. The VM pretty much halted around 12:32 PM today. I'll be
moving this VM to a new HP GL380 G7 running ESXi 4.1 in the next week or
so. That should put an end to issues with this VM.
I think we knew this. See
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6533
Interesting. I seem to recall wanting "tflags allowpublish" at one
point in the past... it seems no matter what, and I'm at fault too,
people almost never use "tflags nopublish".
Regarding score-ing, yeah, the score generator should probably use any
score in the sandbox as a maximum. It's just a little hard to access
the score, if I recall.
Same issue?
Nah, I think the fact that we're not pushing updates due to no spam is
the root cause.
Daryl
