Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: SPAM in spam group is processed into that exact same group
Date: Wed, 27 Oct 2010 12:37:51 -0500	[thread overview]
Message-ID: <871v7bmt8w.fsf@lifelogs.com> (raw)
In-Reply-To: <87fwvsis21.fsf@thinkpad.tsdh.de>

On Tue, 26 Oct 2010 23:04:54 +0200 Tassilo Horn <tassilo@member.fsf.org> wrote: 

TH> Ted Zlatanov <tzz@lifelogs.com> writes:

>> Try the attached patch, it just prefilters the groups list.

TH> No, it doesn't seem to work correctly.  Now the message was copied
TH> successfully to INBOX.training.ham but the copy to my INBOX (which
TH> should have been a move anyway) failed.

Can you trace `spam-copy-or-move-routine' as it walks through the
articles and groups?  Also set `gnus-verbose' to 10 so you'll see the
debug messages in `spam-copy-or-move-routine'.  Your settings may be a
little unusual so I can't replicate the problem here.

TH> BTW: I cannot figure out exactly how to mark a false positive in a spam
TH> group as ham.  I always remove the spam mark (or all marks) using M-u,
TH> but that alone doesn't make the article moved away on exit.  I somehow
TH> need to reopen that group, read the message and exit summary again.  How
TH> is it meant to be?

You have to mark it with at least one ham-mark.  Those are defined as
group/topic parameters in gnus.el with the default:

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

I should really add gnus-ticked-mark to that default list, btw.  Do you agree?

Ted




  reply	other threads:[~2010-10-27 17:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 18:38 Tassilo Horn
2010-10-24  9:55 ` Tassilo Horn
2010-10-25 18:53   ` Ted Zlatanov
2010-10-25 20:05     ` Tassilo Horn
2010-10-25 20:23       ` Ted Zlatanov
2010-10-26  7:04         ` Tassilo Horn
2010-10-26 16:26           ` Ted Zlatanov
2010-10-26 17:38             ` Tassilo Horn
2010-10-26 18:47               ` Ted Zlatanov
2010-10-26 21:04                 ` Tassilo Horn
2010-10-27 17:37                   ` Ted Zlatanov [this message]
2010-11-03 16:39                     ` Tassilo Horn
2010-11-04  8:16                       ` Tassilo Horn
2010-11-04 20:18                         ` Lars Magne Ingebrigtsen
2010-11-05  8:59                           ` Tassilo Horn
2010-11-30 16:58                       ` Tassilo Horn
2010-11-30 18:36                         ` Tassilo Horn
2010-12-05 12:33                         ` Lars Magne Ingebrigtsen
2010-12-05 18:13                           ` Tassilo Horn
2010-12-05 18:37                             ` Lars Magne Ingebrigtsen
2010-12-14 22:32                               ` 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=871v7bmt8w.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).