Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: SPAM in spam group is processed into that exact same group
Date: Tue, 26 Oct 2010 09:04:13 +0200	[thread overview]
Message-ID: <878w1lxwnm.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87fwvu2f9m.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 25 Oct 2010 15:23:17 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

Hi Ted,

> TH> Till now, I didn't try your patch, but I think that it is not the
> TH> proper fix, because right now, all the correctly classified SPAM
> TH> messages in my "real" spam group "nnimap+Fastmail:INBOX.Junk Mail"
> TH> are moved to the spam training group
> TH> "nnimap+Fastmail:INBOX.training.spam".  Of course, in the training
> TH> groups I only want to have the false positives and false
> TH> negatives.
>
> I forgot (it's been a while): copy/move is separate from the
> processors.  s/spam exit processor/spam mover/ above.
>
> So we want to look at `spam-copy-or-move-routine' and not at the
> processor routines.

Oh, sorry for confusing that.  So processors are something like
bogofilter and friends, right?  Ok, those have clearly to be run for any
new mail.

> TH> IMO, the proper way would be to invoke only the opposite processor
> TH> of the groups' classification, that is, invoke the ham processor
> TH> in groups classified as spam, and only the spam processor in ham
> TH> (and unclassified) groups.  Or do you know any usecase for
> TH> invoking the spam processor in spam groups or the ham processor in
> TH> ham groups?
>
> I think what you describe is already the case, but in any case is not
> relevant to your problem, which is with the copy/move routine.
>
> I think the logic should be:
>
> 1) when (and (eq classification 'spam)
>              (spam-group-spam-contents-p gnus-newsgroup-name)
>              (spam-group-spam-contents-p target))
>    -> message "Sorry, can't move spam from spam group A to spam group B"

Sounds right.  classification is the classification of the message,
right?

> 2) when (and (eq classification 'ham)
>              (spam-group-ham-contents-p gnus-newsgroup-name)
>              (spam-group-ham-contents-p target))
>    -> message "Sorry, can't move ham from ham group A to ham group B"

Yes.

> 3) any other case, operate normally and actually do the moves

Yes.

Bye,
Tassilo



  reply	other threads:[~2010-10-26  7:04 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 [this message]
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
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=878w1lxwnm.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.org \
    --cc=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).