Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam.el reporting and moving ham out of spam groups.
Date: 7 Jun 2004 13:12:27 -0400	[thread overview]
Message-ID: <4nn03fpa10.fsf@lifelogs.com> (raw)
In-Reply-To: <87hdu0gwij.fsf@koldfront.dk> (Adam =?iso-8859-1?Q?Sj=F8gren'?= =?iso-8859-1?Q?s?= message of "Fri, 28 May 2004 21:52:04 +0200")

On Fri, 28 May 2004, asjo@koldfront.dk wrote:

On Wed, 26 May 2004 22:29:15 +0200, Adam wrote: 
> On 26 May 2004 12:16:07 -0400, Ted wrote:
>>> But shouldn't spam-process-ham-in-nonham-groups do this? If it
>>> doesn't, there's a bug in my code.
> 
>> I just tested with latest cvs; yes it does work.
> 
> Uh, it gets processed, but not respooled.

> Maybe I need to set "spam-move-ham-in-nonham-groups" to t?

There is no such parameter now.  The logic for moving ham out of spam
groups is:

    ;; now move all ham articles out of spam groups
    (when (spam-group-spam-contents-p gnus-newsgroup-name)
      (let ((num
	     (spam-ham-move-routine
	      (gnus-parameter-ham-process-destination gnus-newsgroup-name))))
	(when (> num 0)
	  (gnus-message 6 "%d ham messages were moved from spam group" num)))))

so it only works in spam groups.  The belief is that ham is already
in the right place outside of spam groups - why should you respool
it?  It only makes sense to process ham outside of spam groups.

Anyhow, I guess this logic can be changed, but I don't think it makes
sense.  I'm not sure anyone but you would find it useful, and adding
an extra option similar to spam-move-spam-nonspam-groups-only would
complicate the code and documentation without gain for the other
users.

If you feel strongly about this, and/or anyone else wants to comment,
feel free.  I just don't want to make spam.el too esoteric.

Thanks
Ted



  reply	other threads:[~2004-06-07 17:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 13:17 Daniel Pittman
2004-05-25 14:14 ` Kai Grossjohann
2004-05-26  4:41   ` Daniel Pittman
2004-05-26 16:17     ` Ted Zlatanov
2004-05-25 15:37 ` Adam Sjøgren
2004-05-26  4:46   ` Daniel Pittman
2004-05-26  8:38     ` Adam Sjøgren
2004-05-26 16:16   ` Ted Zlatanov
2004-05-26 20:29     ` Adam Sjøgren
2004-05-28 19:52       ` Adam Sjøgren
2004-06-07 17:12         ` Ted Zlatanov [this message]
2004-06-07 18:15           ` Adam Sjøgren
2004-06-08 14:24             ` Ted Zlatanov
2004-05-26 16:14 ` Ted Zlatanov
2004-05-26 20:23   ` Miles Bader
2004-05-27  6:15   ` Daniel Pittman
2004-05-27 14:35     ` 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=4nn03fpa10.fsf@lifelogs.com \
    --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).