From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: [Q]: Gmane groups and spam filtering
Date: Fri, 12 Mar 2004 15:18:29 +0000 (UTC) [thread overview]
Message-ID: <loom.20040312T160537-868@post.gmane.org> (raw)
In-Reply-To: <uoer30xay.fsf@xpediantsolutions.com>
Kevin Greiner <kgreiner <at> xpediantsolutions.com> writes:
> > Now I just want to know if my spam-use-gmane-xref is correct since I
> > don't see any difference when set and when not.
>
> You might find it more informative, and faster, to simply look at the code.
Ok I finally found why it didn't work. Setting it this way:
(spam-autodetect-methods spam-use-gmane-xref spam-use-BBDB)
(spam-autodetect . t)
(spam-process '(spam spame-use-gmane))
;; (gnus-group-spam-exit-processor-report-gmane)) ;; obsoleted
(gnus-agent-consider-all-articles . t)
(gnus-agent-enable-expiration . (quote (DISABLE)))
(spam-contents gnus-group-spam-classification-ham)
(agent-predicate . true) ;; and (not spam) (not old))
But now I see many messages like this one:
/-------------------------------------------------------------
|Fetching headers for nntp+news.gmane.org:gmane.linux.debian.user...done
|Dictionary used: american in group nntp+news.gmane.org:gmane.linux.debian.user
|[2 times]
|Scoring...done
|Making sparse threads...done
|Sorting threads...done
|Generating summary...done
|spam-split: widening the buffer (spam-use-bogofilter requires it)
|spam-split: calling the spam-check-gmane-xref function
|spam-split: calling the spam-check-BBDB function
|Article 138023 has a nil data header [3 times]
|Article 138023 has no message ID!
|spam-generate-fake-headers: article 138023 didn't have a valid header
|spam-split: widening the buffer (spam-use-bogofilter requires it)
|spam-split: calling the spam-check-gmane-xref function
|spam-split: calling the spam-check-BBDB function
|Article 138024 has a nil data header [3 times]
|Article 138024 has no message ID!
|spam-generate-fake-headers: article 138024 didn't have a valid header
|spam-split: widening the buffer (spam-use-bogofilter requires it)
|spam-split: calling the spam-check-gmane-xref function
|spam-split: calling the spam-check-BBDB function
|spam-split: widening the buffer (spam-use-bogofilter requires it)
|spam-split: calling the spam-check-gmane-xref function
|spam-split: calling the spam-check-BBDB function
|Article 138026 has a nil data header [3 times]
|Article 138026 has no message ID!
\-------------------------------------------------------------
First I would like to know wether I can deactivate spam-use-bogofilter method
temporary. I thought (wrongly) that setting `spam-autodetect-methods` in a group
parameters would overload it but it seems it is not.
Secondly I don't know why gnus (or spam.el) is complaining about headers. I
didn't try to see a message header but I surely will since it increase spam.el
load and processing time.
> However, since you asked, it appears that gnus-agent-spam-p (the
> function that implements the span predicate) is a rather misleading
> placeholder. It does a gnus-gethash on gnus-agent-spam-hashtb so it
> seems to do something yet I can't find any code, anywhere, that
> populates gnus-agent-spam-hashtb.
So did I.
> On the other hand, if your spam processing results in an article
> score, you could set the agent predicate to select articles higher
> than that score.
Hmm, problem is spam scores are ones that come from bogofilter check and I can
predicate which message is a good (i.e. interesting or not spam) based only on
its score ;)
Regards,
zeDek
next prev parent reply other threads:[~2004-03-12 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 21:22 Xavier Maillard
2004-03-11 23:38 ` Kevin Greiner
2004-03-12 15:18 ` Xavier Maillard [this message]
2004-03-29 21:21 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20040312T160537-868@post.gmane.org \
--to=zedek@gnu-rox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).