Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: CRM114 Mailfilter and spam.el
Date: Sat, 03 Apr 2004 23:19:22 +0200	[thread overview]
Message-ID: <87k70wkbdx.fsf@virgil.koldfront.dk> (raw)
In-Reply-To: <87oeq8kbs9.fsf@virgil.koldfront.dk>

On Sat, 03 Apr 2004 23:10:46 +0200, Adam wrote:

> On Fri, 02 Apr 2004 12:14:44 -0500, Ted wrote:

>>> I've only got the "ham-marked articles in nnml:spam should be
>>> moved as well as processed"-problem left.

>> See spam-ham-copy-or-move-routine for the exact mechanics of this.

Okay, I found out why. In spam-summary-prepare-exit, almost at the
bottom, spam-ham-move-routine is called if and only if the current
group is classified as a spam-group.

This seems to contradict the documentation, where it says:

     So, when you exit a group, the `spam-processors' are applied, if any
  are set, and the processed mail is moved to the
  `ham-process-destination' or the `spam-process-destination' depending
  on the article's classification.  If the `ham-process-destination' or
  the `spam-process-destination', whichever is appropriate, are `nil',
  the article is left in the current group.

   - Spam ELisp Package Sequence of Events

The documentation doesn't mention the codes requirement that the group
be classified as spam for ham to be moved.

I think the code should change, what do you think?


  Best regards,

-- 
 "Mr. Cotton's... parrot. Same question."                     Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2004-04-03 21:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 20:54 Adam Sjøgren
2004-04-02  6:22 ` Kai Grossjohann
2004-04-02 16:04   ` Adam Sjøgren
2004-04-03 13:28     ` Kai Grossjohann
2004-04-03 14:01       ` Adam Sjøgren
2004-04-05 13:21         ` Ted Zlatanov
2004-04-02 16:06   ` Adam Sjøgren
2004-04-02 17:14     ` Ted Zlatanov
2004-04-03 21:10       ` Adam Sjøgren
2004-04-03 21:19         ` Adam Sjøgren [this message]
2004-04-03 21:48           ` Adam Sjøgren
2004-04-03 21:58             ` Adam Sjøgren
2004-04-03 13:29     ` Kai Grossjohann
2004-04-03 13:49       ` Adam Sjøgren
2004-04-06  8:12         ` Kai Grossjohann
2004-04-06 21:40           ` Adam Sjøgren
2004-04-02 16:10   ` Jody Klymak
2004-04-02 17:07   ` Ted Zlatanov
2004-04-02 17:06 ` Ted Zlatanov
2004-04-02 17:26   ` Adam Sjøgren
2004-04-02 17:44     ` Ted Zlatanov
2004-04-03 14:22       ` Adam Sjøgren
2004-04-03 14:24         ` Adam Sjøgren
2004-04-03 23:59 ` Adam Sjøgren
2004-04-04  1:59   ` Jesper Harder
2004-04-04 13:07     ` Adam Sjøgren
2004-04-05 13:24       ` Ted Zlatanov
2004-04-05 15:50         ` Jesper Harder
2004-04-06 21:36       ` Adam Sjøgren
2004-05-20 18:39         ` Ted Zlatanov
2004-05-20 19:19           ` Adam Sjøgren
2004-05-22 23:44             ` Lars Magne Ingebrigtsen
2004-05-23 13:44               ` Adam Sjøgren
2004-05-26 16:23             ` Ted Zlatanov
2004-05-26 20:30               ` Adam Sjøgren

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=87k70wkbdx.fsf@virgil.koldfront.dk \
    --to=asjo@koldfront.dk \
    /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).