Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Spam does not move
Date: 1 Jul 2004 12:11:29 -0400	[thread overview]
Message-ID: <4nsmcbemha.fsf@lifelogs.com> (raw)
In-Reply-To: <m3vfh7981v.fsf@venus.dti.ne.jp> (Kohkichi Hosoda's message of "Thu, 01 Jul 2004 22:21:59 +0900")

On Thu, 01 Jul 2004, khosoda@venus.dti.ne.jp wrote:

> Ted> - do M-: (gnus-summary-article-mark 5644)
> 
> do M-: (gnus-summary-article-mark 6029) -> 36
> 
> Ted> - do M-: (spam-group-spam-mark-p GROUP MARK) where GROUP is the
> Ted> group name, usually in gnus-newsgroup-name, and MARK is what
> Ted> gnus-summary-article-mark returned.

OK, so we know this article is considered spam (36 is the $ character
which is the spam mark).

> do M-: (spam-group-spam-mark-p kohkichi 36) ->
> 
> Debugger entered--Lisp error: (void-variable kohkichi)
>   (spam-group-spam-mark-p kohkichi 36)
>   eval((spam-group-spam-mark-p kohkichi 36))
>   eval-expression((spam-group-spam-mark-p kohkichi 36) nil)
> * call-interactively(eval-expression)

Where you put kohkichi, you need either

gnus-newsgroup-name

OR

"nntp:group.name" (or whatever the actual group name is)

This is essential, but you don't need to do the preceding
gnus-summary-article-mark step, just enter the group and run this
step.

> Ted> I have the feeling you've somehow removed the spam-mark from the
> Ted> list of spam-marks for your ham group.  I don't know what else
> Ted> the problem could be.
> 
> Group parameters of my HAM group are the followings:
> 
> ((spam-contents gnus-group-spam-classification-ham)
>  (spam-process
>   ((spam spam-use-stat)
>    (ham spam-use-stat)))
>  (spam-process-destination "nnml:spam")
>  (spam-marks
>   (gnus-spam-mark)))

Can you please remove the spam-marks parameter altogether?  The rest
looks OK (if you really have a spam group called "nnml:spam").

Thanks
Ted



  reply	other threads:[~2004-07-01 16:11 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
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 [this message]
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=4nsmcbemha.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).