From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Processing ham with spam.el
Date: 1 Nov 2004 14:05:16 -0500 [thread overview]
Message-ID: <4nfz3tbdar.fsf@lifelogs.com> (raw)
In-Reply-To: <87lldne9pl.fsf@marant.org> =?iso-8859-1?Q?=28J=E9r=F4me?= Marant's message of "Sun, 31 Oct 2004 06:29:58 +0100")
On Sun, 31 Oct 2004, jmarant@nerim.net wrote:
> I read the proper Gnus manual sections about spam and I managed
> to make gnus teach bogofilter about spam messages.
>
> I added the following:
>
> (add-to-list 'gnus-parameters
> '(".*"
> (ham-marks (gnus-ticked-mark))
> (spam-process ((spam spam-use-bogofilter)
> (ham spam-use-bogofilter)))
> (spam-process-destination "spam")))
>
> However, I can't make it work for ham. Marking messages with '!'
> (ticked mark) and leaving the group does not trigger bogofilter.
> I must have missed something. Any idea?
It looks correct. Can you try to force these parameters with `G p' to
be sure they are active in the group of interest?
If you can step through the spam-summary-prepare-exit function, that
would be most helpful. Specifically,
spam-resolve-registrations-routine will be invoked and I need to know
what articles are listed for ham bogofilter processing.
Ted
next prev parent reply other threads:[~2004-11-01 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 5:29 Jérôme Marant
2004-11-01 19:05 ` Ted Zlatanov [this message]
2004-11-01 20:23 ` Jérôme Marant
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=4nfz3tbdar.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).