On Thu, Sep 27, 2018 at 06:03:13PM +0300, Henrik Krohns wrote:
> On Thu, Sep 27, 2018 at 07:52:14AM -0700, John Hardin wrote:
> > On Thu, 27 Sep 2018, Henrik Krohns wrote:
> >
> > >
> > >Hello mass checkers,
> > >
> > >Please notice the --after clauses added to automasscheck.cf.
> > >
> > ># Use --after selector for corpus to prevent unnecessary processing.
> > ># Current ruleqa settings: ham 6 years, spam 2 months
> > ># Anything older than that will be ignored by ruleqa regardless.
> > >run_all_masschecks() {
> > > ### sample: single corpus ###
> > > run_masscheck single-corpus \
> > > --after=-174182400 ham:dir:/path/to/Maildir/.Ham/ \
> > > --after=-4838400 spam:dir:/path/to/Maildir/.Spam/
> >
> > What are those values in terms of? delta seconds from now?
>
> Yep. I figured people don't have parsedate. :-)
>
> $ ./mass-check --help
>
> --after=N only test mails received after time_t N (negative values
> are an offset from current time, e.g. -86400 = last day)
> or after date as parsed by Time::ParseDate (e.g. '-6 months')
FYI, the server side values can be found from masses/rule-qa/reports-from-logs
# what's the max age of mail we will accept data from? (in weeks)
# TODO: maybe this should be in ~/.corpus
my $OLDEST_HAM_WEEKS = 72 * 4; # 72 months = 6 years
my $OLDEST_SPAM_WEEKS = 2 * 4; # 2 months
