From: Kohkichi Hosoda <khosoda@venus.dti.ne.jp>
Subject: Re: Spam does not move
Date: Tue, 18 May 2004 23:55:25 +0900 [thread overview]
Message-ID: <m3brklbx9b.fsf@venus.dti.ne.jp> (raw)
In-Reply-To: <v9oeonrsl1.fsf@marauder.physik.uni-ulm.de>
>>>>> On Mon, 17 May 2004 17:17:30 +0200, Reiner Steib <4.uce.03.r.s@nurfuerspam.de> said:
Reiner> Try the recommended setup from the manual instead:
Reiner> ,----[ (info "(gnus)Filtering Spam Using The Spam ELisp
Reiner> Package") ] | First of all, you *must* run the function
Reiner> `spam-initialize' to | autoload `spam.el' and to install the
Reiner> `spam.el' hooks. There is one | exception: if you use the
Reiner> `spam-use-stat' (*note spam-stat spam | filtering::) setting,
Reiner> you should turn it on before `spam-initialize':
Reiner> |
Reiner> | (setq spam-use-stat t) ;; if needed
| (spam-initialize)
Thank you for your advice. However, this setting in my .gnus.el gave
me error and gnus did not even start.
Debugger entered--Lisp error: (void-function spam-initialize)
(spam-initialize)
eval-buffer(#<buffer *load*> nil "~/.gnus" nil t)
;;; Reading at buffer position 15404
load-with-code-conversion("/Users/kohkichi/.gnus.el" "~/.gnus" nil t)
load("~/.gnus" nil t)
gnus-read-init-file()
gnus-1(nil nil nil)
gnus(nil)
* call-interactively(gnus)
execute-extended-command(nil)
* call-interactively(execute-extended-command)
I also tried the following setup.
(setq spam-use-stat t)
(require 'spam)
(spam-initialize)
With this setting, gnus starts but my problem is not solved, i.e.,
spam mails in ham group still do not move into spam group.
Is there any other method I should try?
Thank you for your help in advance.
--
Kohkichi Hosoda
E-mail address: khosoda@venus.dti.ne.jp
http://www.venus.dti.ne.jp/~khosoda/Enlightenment.html
next prev parent reply other threads:[~2004-05-18 14:55 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 [this message]
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
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=m3brklbx9b.fsf@venus.dti.ne.jp \
--to=khosoda@venus.dti.ne.jp \
/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).