Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Herbert Valerio Riedel <hvr@gnu.org>
Cc: ding@gnus.org
Subject: Re: What condition triggers to ham-process-destination ?
Date: Sat, 10 Mar 2012 08:13:18 -0500	[thread overview]
Message-ID: <87pqckzjip.fsf@lifelogs.com> (raw)
In-Reply-To: <87aa3rfna0.fsf@gnu.org> (Herbert Valerio Riedel's message of "Thu, 08 Mar 2012 10:35:35 +0100")

On Thu, 08 Mar 2012 10:35:35 +0100 Herbert Valerio Riedel <hvr@gnu.org> wrote: 

HVR> But when unmarking false positives in Junk, I couldn't trigger the
HVR> `ham-process-destination` action, i.e. the message is not marked with
HVR> '$' anymore (, but stays in the Junk folder. On spam-group-exit the
HVR> $-marked messages are marked expirable (as expected), but the non-$
HVR> marked messages are left untouched.

HVR> What do I have to do, to have the non-$-marked messages moved to
HVR> ham-process-destination? Which elisp function should I try to debug to
HVR> find out what's happening?

The messages in the Junk folder have to be marked as ham.  This is
controlled by the ham-marks group parameter, and you can check with
(gnus-parameter-ham-marks "groupname").  You can set them as group/topic
parameters; e.g. use `G p' on your top-level topic and set:

 (ham-marks (gnus-ticked-mark))

(if this is the only parameter, meaning you only see a nil, you need to
wrap it in extra parentheses)

Now, every time you tick a spam article, it will be moved out of the
spam group for ham training when you exit.

Ted



  reply	other threads:[~2012-03-10 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  9:35 Herbert Valerio Riedel
2012-03-10 13:13 ` Ted Zlatanov [this message]
2012-03-11 13:38   ` Herbert Valerio Riedel

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=87pqckzjip.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=hvr@gnu.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).