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

Ted Zlatanov <tzz@lifelogs.com> writes:

> 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.

Thanks, now everything works!

I was a bit mislead by the info section "8.20.1 Spam Package
Introduction" telling me to just "unmark" (as I did by using 'M-u'):

| Similarly, you can unmark an article if it has been erroneously marked
| as spam. See Setting Marks.

It might help avoid confusion, if that sentence would be more explicit
to say that not only should the spam-mark be removed, but also a mark
has to be set which is contained in the `ham-marks` set.


Btw, what is the recommended way to set up an "unsure" emailfolder,
i.e. a folder which gets emails which bogofilter (in tristate mode) was
/unsure/ about whether it's spam or ham?

cheers,
  hvr
-- 



      reply	other threads:[~2012-03-11 13:38 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
2012-03-11 13:38   ` Herbert Valerio Riedel [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=87zkbntfyn.fsf@gnu.org \
    --to=hvr@gnu.org \
    --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).