Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: spam filtering
Date: 29 Sep 2004 10:55:07 -0400	[thread overview]
Message-ID: <4nmzz9azw4.fsf@lifelogs.com> (raw)
In-Reply-To: <uoejp2ote.fsf@gnu.org> (Sam Steingold's message of "Wed, 29 Sep 2004 09:21:33 -0400")

On Wed, 29 Sep 2004, sds@gnu.org wrote:

> also, I have _many_ imap folders, listing them all is not feasible.

You can use topics, they support parameters just like groups do.

>>> (it would also be nice if I could mark non-spam in Trash and have it
>>> moved to INBOX on exit from Trash, but...)
>>
>> Same here:
>>
>>         ("nnimap+...:Trash"
>>          (ham-process-destination . "nnimap:INBOX")
>>          (spam-contents gnus-group-spam-classification-spam))
> 
> so, do I use M-d in "Trash" to "ham" the message?

You give the article a ham-mark, which can be many things (by default
the ham marks are (gnus-del-mark gnus-read-mark gnus-killed-mark
gnus-kill-file-mark gnus-low-score-mark) but I like to also use
gnus-ticked-mark.

You may also want spam-mark-ham-unread-before-move-from-spam-group,
which will undo the ham-mark (set the article to "Unread") before
moving the article to your favorite destination.  It's nil by default.

Ted



  parent reply	other threads:[~2004-09-29 14:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 20:38 Sam Steingold
2004-09-29  7:12 ` Reiner Steib
2004-09-29 13:21   ` Sam Steingold
2004-09-29 14:54     ` Reiner Steib
2004-09-29 15:29       ` Sam Steingold
2004-09-30 14:35         ` Ted Zlatanov
2004-10-03 14:12           ` Sam Steingold
2004-10-07 18:24             ` Ted Zlatanov
2004-09-29 14:55     ` Ted Zlatanov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-06 23:57 SPAM filtering Jorge Godoy
2000-11-07  7:05 ` Kai Großjohann

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=4nmzz9azw4.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    /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).