https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6155

--- Comment #138 from Mark Martinec <[email protected]> 2009-10-27 14:29:03 
UTC ---
(In reply to comment #134)
> Some of the spam in my corpora is from third parties. I do check it for 
> correct
> classification before uploading, but I was wondering: how does masscheck
> determine the correct lastexternal for corpora containing messages from
> multiple different networks? Or does it assume all of the messages in a given
> contributor's corpora have the same network boundary? If the latter, I need to
> remove those third-party messages from my spam corpora...
> 
> Might lastexternal confusion in the masschecks be contributing in some way to
> the odd RCVD_IN_* score generation?

I believe the masschecks leaves internal/external/msa_networks to their
defaults, unless one cares to configure it correctly for his corpus. And
I believe that it is more likely than not that some corpora were scanned
with unsuitable settings of networks. I know that configuring it for my
mass checks runs it gave me a headache (but I did it right in the end).
Which is why I posted the following note on the ML at that time:


  From: Mark Martinec <[email protected]>
  To: [email protected]
  Subject: Re: SpamAssassin 3.3.0 mass-checks now starting
  Date: Fri, 4 Sep 2009 21:46:59 +0200

  Docs don't say where one is supposed to put a local.cf with
  options which are ignored in masses/spamassassin/user_prefs
  (like Bayes SQL options, DCC, Pyzor timeouts etc).

  I tried to place local.cf into masses/spamassassin/, with
  horror results (some directives in local.cf proclaimed as
  invalid, as apparently plugins have not yet been loaded
  at the time of parsing this file, but only later).

  I finally placed it into ../rules/ as mylocal.cf, which
  finally works as expected, but I wonder if the is the proper
  solution. Should be documented I guess...

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to