Dave,
Did you have any feedback on this if other mirrors need it? Any
centralization of the solution?
Regards,
KAM
On 11/22/2017 9:29 AM, Dave Jones wrote:
> On 11/20/2017 11:33 PM, Matthias Leisi wrote:
>> In addition to server-side blocking, would it make sense for
>> sa-update to rate-limit
Resending this time to the correct dev@ list for sa.
After discussing things with Dave and based on my experience with the SA
releases and Masscheck systems, I'm recommending the following:
#1 - Make all of Masscheck, masscheckers, ruleqa/nitemc, rule promotions,
etc. (EVERYTHING) run using
After discussing things with Dave and based on my experience with the SA
releases and Masscheck systems, I'm recommending the following:
#1 - Make all of Masscheck, masscheckers, ruleqa/nitemc, rule promotions,
etc. (EVERYTHING) run using trunk and not 3.4, etc.
- There is a concern that the
+ promote_active_rules
+ pwd
+ /usr/bin/perl build/mkupdates/listpromotable
/usr/local/spamassassin/automc/svn/trunk
HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/3-days-ago?xml=1
day 3
