Gnus development mailing list
 help / color / mirror / Atom feed
From: Kohkichi Hosoda <khosoda@venus.dti.ne.jp>
Cc: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: Spam does not move
Date: Sat, 19 Jun 2004 01:00:46 +0900	[thread overview]
Message-ID: <m3hdt8ua8f.fsf@venus.dti.ne.jp> (raw)
In-Reply-To: <4nacz63yy6.fsf@lifelogs.com> (Ted Zlatanov's message of "14 Jun 2004 12:07:45 -0400")

>>>>> On 14 Jun 2004 12:07:45 -0400, "Ted Zlatanov" <tzz@lifelogs.com> said:

Ted> The new version of spam.el which I just posted to the ding list
Ted> has new logic for moving spam out.  Can you test with that
Ted> version and let me know what happens?

Unfortunately, the new version does not change the situation.   Spam
mail marked with "O" in ham group still does not go into spam group
when I exited the summary buffer of the ham group. 
The messages say;
Exiting summary buffer and applying spam rules

When I use M-c to remove mark, exit and re-enter the summary buffer,
and mark the spam with M-d, it does go into the spam group.  
The messages say;
Exiting summary buffer and applying spam rules
Registering 1  articles as spam using backend spam-use-stat
1 spam messages were processed by backend spam-use-stat.
Registering 1  articles as spam using backend spam-use-move
Moving to nnml:spam: (7159)...
Loading gnus-dup...done
Wrote /Users/kohkichi/Mail/spam/22187
1 spam messages were processed by backend spam-use-move.

BTW, your patch hunk for gnus.el.  That may be the cause of the
trouble this time.  Could you use -uNr option for diff?

Thank you very much for remembering my problem.  

--
Kohkichi Hosoda
E-mail address: khosoda@venus.dti.ne.jp
http://www.venus.dti.ne.jp/~khosoda/Enlightenment.html



  reply	other threads:[~2004-06-18 16:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 12:47 Kohkichi Hosoda
2004-05-17 15:17 ` Reiner Steib
2004-05-18 14:55   ` Kohkichi Hosoda
2004-05-18 15:40     ` Kai Grossjohann
2004-05-19 15:31       ` Kohkichi Hosoda
2004-05-19 18:07         ` Ted Zlatanov
2004-05-21 13:16           ` Kohkichi Hosoda
2004-05-22 14:11             ` Kohkichi Hosoda
2004-05-24 19:10             ` Ted Zlatanov
2004-05-28 17:00               ` Kohkichi Hosoda
2004-06-14 16:07                 ` Ted Zlatanov
2004-06-18 16:00                   ` Kohkichi Hosoda [this message]
2004-06-24 16:30                     ` Ted Zlatanov
2004-06-26 14:05                       ` Kohkichi Hosoda
2004-06-26 16:19                       ` Kohkichi Hosoda
2004-06-29 18:16                         ` Ted Zlatanov
2004-07-01 13:21                           ` Kohkichi Hosoda
2004-07-01 16:11                             ` Ted Zlatanov
2004-07-02 13:11                               ` Kohkichi Hosoda
2004-07-16 17:00                                 ` Ted Zlatanov
2004-07-25 14:29                                   ` Kohkichi Hosoda
2004-07-27 16:46                                     ` Ted Zlatanov
2004-08-14 14:15                                       ` Kohkichi Hosoda
  -- strict thread matches above, loose matches on Subject: below --
2004-05-16 13:20 Kohkichi Hosoda

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=m3hdt8ua8f.fsf@venus.dti.ne.jp \
    --to=khosoda@venus.dti.ne.jp \
    --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).