Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: bogofilter config
Date: Fri, 31 Oct 2003 22:08:06 -0500	[thread overview]
Message-ID: <4n65i46b1l.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <76ism5xk20.fsf@newjersey.ppllc.com> (Jake Colman's message of "Fri, 31 Oct 2003 14:51:19 -0500")

On Fri, 31 Oct 2003, colman@ppllc.com wrote:

>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>    TZ> On Fri, 31 Oct 2003, colman@ppllc.com wrote:
>    >> I subscribe to many email lists.  I scan all the subjects but
>    >> only read some of the messages.  How can I use the contents of
>    >> this list for ham training?  It would seem that I either have
>    >> to manually read ('R mark) or delete ('r' mark) any message
>    >> which I want touse for training.  Is this correct?  Is there
>    >> anyway around this?
> 
>    TZ> Hitting `c' (catchup) should mark all unread articles in the
>    TZ> current group as read.  Does that invoke the ham processing
>    TZ> for you?
> 
> Hmmmm.  if you are correct, then why woud I need to specify
> gnus-unread-mark as a ham mark, as you suggested elsewhere?

In case you want to use `q' instead of `c' - the unread articles stay
unread then.  I don't claim one approach is better than the other, but
I would use `c' instead of making the unread mark a ham mark because
it requires less customization on your part.

Ted



  reply	other threads:[~2003-11-01  3:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 13:58 Jake Colman
2003-10-30 15:23 ` Ted Zlatanov
2003-10-30 15:35   ` Jake Colman
2003-10-30 15:40     ` Jake Colman
2003-10-30 15:54       ` Ted Zlatanov
2003-10-30 16:56         ` Jake Colman
2003-10-31 16:30           ` Ted Zlatanov
2003-10-31 17:32             ` Jake Colman
2003-10-31 18:51               ` Ted Zlatanov
2003-10-31 19:51                 ` Jake Colman
2003-11-01  3:08                   ` Ted Zlatanov [this message]
2003-11-03 14:46                     ` Jake Colman
2003-11-07  6:39                     ` smtpmail and starttls John Owens
2003-11-07 16:50                       ` Simon Josefsson
2003-11-07 17:33                         ` John Owens
2003-11-08  1:38                           ` Simon Josefsson
2003-11-14  2:18                             ` John Owens
2003-11-07 20:12                         ` John Owens

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=4n65i46b1l.fsf@lockgroove.bwh.harvard.edu \
    --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).