Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Shields <shields@msrl.com>
Cc: ding@gnus.org
Subject: Re: Problem Moving Ham from Spam
Date: Mon, 03 Nov 2003 16:58:10 +0000	[thread overview]
Message-ID: <87u15l75jx.fsf@mulligatwani.msrl.com> (raw)
In-Reply-To: <76brrtwle3.fsf@newjersey.ppllc.com> (Jake Colman's message of "Mon, 03 Nov 2003 09:56:52 -0500")

In message <76brrtwle3.fsf@newjersey.ppllc.com>,
Jake Colman <colman@ppllc.com> wrote:
> 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?

No.  The default ham marks are:

   :variable-default '((".*" ((gnus-del-mark
			       gnus-read-mark
			       gnus-killed-mark
			       gnus-kill-file-mark
			       gnus-low-score-mark))))

I don't think tick should be a default ham mark, because the tick mark
is not reset when leaving the group.  Many people use ticked articles
as a way of temporarily saving them, and it would be incorrect to copy
them to ham groups every time the group is exited.

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

Manually?  That implies that Emacs could not do it for you.  No, add
tick to the ham-marks if you want, or use 'd' instead of '!' to rescue
ham from spam groups.
-- 
Shields.




  parent reply	other threads:[~2003-11-03 16:58 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
2003-11-03 16:58 ` Michael Shields [this message]
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=87u15l75jx.fsf@mulligatwani.msrl.com \
    --to=shields@msrl.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).