From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Spam does not move
Date: 19 May 2004 14:07:09 -0400 [thread overview]
Message-ID: <4nfz9wcmuq.fsf@lifelogs.com> (raw)
In-Reply-To: <m37jv8xwk0.fsf@venus.dti.ne.jp> (Kohkichi Hosoda's message of "Thu, 20 May 2004 00:31:56 +0900")
On Thu, 20 May 2004, khosoda@venus.dti.ne.jp wrote:
>>>>>> On Tue, 18 May 2004 17:40:09 +0200, Kai Grossjohann <kgrossjo@eu.uu.net> said:
>
> Kai> Did you (require 'gnus-load) from ~/.emacs? It must be before
> Kai> any part of Gnus is loaded, therefore ~/.gnus is too late.
>
> Oops, I did not do that. Yes, addition of (require 'gnus-load) in my
> .emacs.el solved the Gnus startup trouble. However, the original
> problem (spam does not move) still exists. What else should I try?
Hi,
I looked at your settings earlier and nothing looked unusual. Can
you run spam-summary-prepare-exit manually when you mark some spam?
Does it do anything? If not, can you trace the function's
execution? It does not do anything very complex, and the specific
point of interest is
(unless (and spam-move-spam-nonspam-groups-only
(spam-group-spam-contents-p gnus-newsgroup-name))
(when (< 0 (length (spam-list-articles
gnus-newsgroup-articles
'spam)))
(gnus-message 6 "Marking spam as expired and moving it to %s"
(gnus-parameter-spam-process-destination
gnus-newsgroup-name))
(spam-mark-spam-as-expired-and-move-routine
(gnus-parameter-spam-process-destination gnus-newsgroup-name))))
which works fine for me, so something odd is happening on your side.
You know, it could be an old version of spam.el, which doesn't even
have the code as it is above... But you would have to upgrade your
whole Gnus to CVS to use the latest spam.el, so that's annoying. Hmm.
What do you want to do, try CVS or try to fix your current spam.el
copy?
Thanks
Ted
next prev parent reply other threads:[~2004-05-19 18:07 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 [this message]
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=4nfz9wcmuq.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).