From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: [Q]: Gmane groups and spam filtering
Date: Mon, 29 Mar 2004 16:21:49 -0500 [thread overview]
Message-ID: <4nk713qrgy.fsf@lifelogs.com> (raw)
In-Reply-To: <loom.20040312T160537-868@post.gmane.org> (Xavier Maillard's message of "Fri, 12 Mar 2004 15:18:29 +0000 (UTC)")
On Fri, 12 Mar 2004, zedek@gnu-rox.org wrote:
> But now I see many messages like this one:
>
> /-------------------------------------------------------------
> |Article 138023 has a nil data header [3 times]
> |Article 138023 has no message ID!
> \-------------------------------------------------------------
This is caused by the spam-generate-fake-headers function, which will
use the overview data to build fake headers when possible.
See if you can find what's causing the nil data header by tracing
through the spam-find-spam function. It calls
(spam-generate-fake-headers article) when possible.
> 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.
It should. What does `G p' show for the group in question?
> 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.
With spam-autodetect, all headers of hitherto unseen messages are
checked when you enter a group, but spam.el tries to do it without
retrieving the whole article. That's the reason for the whole
spam-generate-fake-headers rigamarole.
Ted
prev parent reply other threads:[~2004-03-29 21:21 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
2004-03-29 21:21 ` Ted Zlatanov [this message]
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=4nk713qrgy.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).