Gnus development mailing list
 help / color / mirror / Atom feed
From: Jody Klymak <jklymak@coas.oregonstate.edu>
Subject: Re: Problem Moving Ham from Spam
Date: Mon, 03 Nov 2003 08:13:20 -0800	[thread overview]
Message-ID: <uvfq1e8gv.fsf@coas.oregonstate.edu> (raw)
In-Reply-To: <76brrtwle3.fsf@newjersey.ppllc.com>

Jake Colman <colman@ppllc.com> writes:

> I also set the global variable
> spam-mark-ham-unread-before-move-from-spam-group to true.
>
> I entered the group and tickeed ("!") those messages that were really ham.  I
> did a 'c' on the group and watched it all chug away expecting to have my ham
> moved to the INBOX/Misc folder marked unread.  Instead, the ticked messages
> remained as ticked messages in my spam folder and did not get moved.

This all works fine for me, except I have
spam-mark-ham-unread-before-move-from-spam-group set to nil.

> Two questions:
>
> 1) What did I do wrong?  Do I need to specify the ham-marks group
> parameter for this to work?  I didn't think so since the tick mark
> shold be comnsidered a ham mark by default, no?

Maybe it should, but I doubt that it is.  I asked Ted to have it added
to the customize list.  I don't think it is enabled by "default".  Are
any marks enabled by default?  What happens if you actually try to set
it?

> 2) How do I fix this now?  I want the ticked messages to be trained
> as ham and moved.  Do I just move them manually to my ham group and
> let them get trained by the ham group's exit processor?

No, you shouldn't need to move them manually.  They will get moved...

Cheers,  Jody

-- 
Jody Klymak      http://mixing.coas.oregonstate.edu/people/jklymak/
mailto:jklymak@coas.oregonstate.edu   




  reply	other threads:[~2003-11-03 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 14:56 Jake Colman
2003-11-03 16:13 ` Jody Klymak [this message]
2003-11-03 16:58 ` Michael Shields
2003-11-03 19:01   ` 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=uvfq1e8gv.fsf@coas.oregonstate.edu \
    --to=jklymak@coas.oregonstate.edu \
    /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).