Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@void.at>
Subject: Re: How do you make spam automatically move to spam group on exit?
Date: Sat, 8 Mar 2003 17:10:39 +0000 (UTC)	[thread overview]
Message-ID: <871y1h3idu.fsf@eris.void.at> (raw)
In-Reply-To: <m3bs0l3n83.fsf@heechee.beld.net>

Today, Ted Zlatanov <tzz@lifelogs.com> wrote:
>> BTW, why do unread messages not count? 
> 
> I know it seems counter-intuitive, but unread messages are neither ham
> nor spam.  They are just mail.  Spam groups are the only place where
> unread messages get processed automatically (given the spam mark).

Mm-hm, I see.

> I like that solution.  Maybe there should be a group parameter for the
> spam-spam-marks and spam-ham-marks.

That's what my hack (titled a solution) is trying to emulate. (-;

> Unfortunately, spam groups *always* mark unread articles as
> spam. That's the way they work.  You should use the
> ham-process-destination parameter to move out ham, once you've marked
> it as ham, and you should not use the unread mark to be a ham mark.
> Use the gnus-read-mark (which already is a ham mark by default, and
> will also positively affect the adaptive score).  That way you just
> read the message if it's ham, quit the group, and the message will be
> moved automatically to the ham-process-destination.
> 
> spam-ham-move-routine will be invoked after all the other
> spam/ham processors to move the ham out of a spam group to the
> spam-process-destination.

Could spam-ham-move-routine mark the messages as unread after moving
them? I do really would like to read the message in the "right" group,
and not in my spambox or my "false positive" box.

Thanks for the explanation,
-- 
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
irc.freenode.net's #emacs - online emacs advice from IRC addicts




  reply	other threads:[~2003-03-08 17:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 20:34 Emerick Rogul
2003-03-07 20:56 ` Ted Zlatanov
2003-03-07 21:35   ` Emerick Rogul
2003-03-08  6:07     ` Ted Zlatanov
2003-03-08 13:21       ` Andreas Fuchs
2003-03-08 15:13         ` Ted Zlatanov
2003-03-08 17:10           ` Andreas Fuchs [this message]
2003-03-08 17:16             ` Ted Zlatanov
2003-03-09 11:33               ` Andreas Fuchs
2003-03-09  6:26       ` Emerick Rogul
2003-03-09 10:59         ` Jorge Godoy
2003-03-09 17:24           ` Emerick Rogul
2003-03-10 15:53             ` Ted Zlatanov
2003-03-10 16:31               ` Emerick Rogul
2003-03-10 17:15                 ` Ted Zlatanov
2003-03-10 18:23                   ` Ted Zlatanov
2003-03-10 15:41         ` Ted Zlatanov
2003-03-10 16:20           ` Emerick Rogul

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=871y1h3idu.fsf@eris.void.at \
    --to=asf@void.at \
    /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).