[auto] bad sandbox rules report

2019-09-11 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-09-04 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-08-28 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-08-21 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-08-14 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-08-07 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-07-31 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-07-24 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-07-17 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-07-10 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-07-03 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-06-26 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-06-19 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2019-05-08 Thread Rules Report Cron
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

[auto] bad sandbox rules report

2017-05-24 Thread Rules Report Cron
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 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set

[auto] bad sandbox rules report

2015-04-08 Thread Rules Report Cron
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 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set

[auto] bad sandbox rules report

2015-03-25 Thread Rules Report Cron
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 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set

[auto] bad sandbox rules report

2015-03-11 Thread Rules Report Cron
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 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set

[auto] bad sandbox rules report

2015-03-04 Thread Rules Report Cron
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 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set

Re: [auto] bad sandbox rules report

2013-03-06 Thread Axb
Guys, I'm disabling 0 hit/non perfomers/abandoned rules in hstern's sandbox. make test spit out: STOX_REPLY_TYPE_WITHOUT_QUOTES depends on __HS_SUBJ_RE_FW which is nonexistent STOX_REPLY_TYPE_WITHOUT_QUOTES depends on __HS_QUOTE which is nonexistent FROM_12LTRDOM depends on __HS_SUBJ_RE_FW

Re: [auto] bad sandbox rules report

2013-03-06 Thread Axb
On 03/06/2013 10:19 AM, Axb wrote: Guys, I'm disabling 0 hit/non perfomers/abandoned rules in hstern's sandbox. make test spit out: STOX_REPLY_TYPE_WITHOUT_QUOTES depends on __HS_SUBJ_RE_FW which is nonexistent STOX_REPLY_TYPE_WITHOUT_QUOTES depends on __HS_QUOTE which is nonexistent

Re: [auto] bad sandbox rules report

2013-03-06 Thread Kevin A. McGrail
On 3/6/2013 4:54 AM, Axb wrote: I've copied the dependencies to jm and jhardin sandboxes. Suggest you rename them so they're unique to your rules and/or put them in a commitername_dependencies.cf file I like getting rid of the rules that aren't working. But this copying rules in sandbox

Re: [auto] bad sandbox rules report

2013-03-06 Thread Axb
On 03/06/2013 11:55 AM, Kevin A. McGrail wrote: On 3/6/2013 4:54 AM, Axb wrote: I've copied the dependencies to jm and jhardin sandboxes. Suggest you rename them so they're unique to your rules and/or put them in a commitername_dependencies.cf file I like getting rid of the rules that aren't

Re: [auto] bad sandbox rules report

2013-03-06 Thread John Hardin
On Wed, 6 Mar 2013, Axb wrote: If your rules depend on sandbox rules which are not in your own, PLEASE always copy these rules to your own sandbox. This will avoid suprises in the future. It also can lead to problems if the owner of that rule modifies their original copy, but I see your

Re: [auto] bad sandbox rules report

2013-03-06 Thread John Hardin
On Wed, 6 Mar 2013, Axb wrote: I've copied the dependencies to jm and jhardin sandboxes. Suggest you rename them so they're unique to your rules and/or put them in a commitername_dependencies.cf file Thanks! -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/

Re: [auto] bad sandbox rules report

2012-09-12 Thread Axb
Godo day rulesrc/sandbox/khopesh/ is full of rules which are tflags nopublish We've been masschecking these rules for months and it seems pretty pointless to spend CPU time on them if they're never going to be published. Could these be reviewed and disabled/removed if there's no plan

Re: [auto] bad sandbox rules report

2012-07-04 Thread Axb
Good day Commiters, Could we agree to remove/disable no hits at all rules? This would speed up masschecks quite a bit. (also, never hurts to do a cleanup) Thanks Axb

Re: [auto] bad sandbox rules report

2012-07-04 Thread Benny Pedersen
Den 2012-07-04 10:44, Axb skrev: Could we agree to remove/disable no hits at all rules? no, spammers would start using this taktics after disable is there an minimum time for not hitting ?, or just not hitting last masscheck ? This would speed up masschecks quite a bit. oh fair :)

Re: [auto] bad sandbox rules report

2009-08-27 Thread Justin Mason
ah, noted. --j. On Thu, Aug 27, 2009 at 01:23, Warren Togamiwtog...@redhat.com wrote: On 08/26/2009 04:31 AM, Rules Report Cron wrote: rulesrc/sandbox/jm/20_khop_sc_bug_6114.cf (10 rules, 10 bad):   KHOP_SC_CIDR16:  no hits at all   KHOP_SC_CIDR24:  no hits at all   KHOP_SC_CIDR8:  no

[auto] bad sandbox rules report

2009-07-08 Thread Rules Report Cron
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 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set

[auto] bad sandbox rules report

2009-06-24 Thread Rules Report Cron
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 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set