From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: ham destination bugs (was: spam.el: Bugs, compatibility with v5-10)
Date: 13 Feb 2006 14:15:55 -0500 [thread overview]
Message-ID: <4nzmkv9ij8.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <v98xsk60h0.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 09 Feb 2006 16:00:43 +0100")
On 9 Feb 2006, reinersteib+gmane@imap.cc wrote:
On Wed, Feb 08 2006, Ted Zlatanov wrote:
> [ I didn't report it yet because I wanted to test if the problem only
> occurs with nnimap or also for nnml groups. But now that you ask... ]
> `ham-process-destination' doesn't work correctly for me. When I find
> a ham message in "Spam/Unsure", I mark it with `d'. On group exit,
> the message is moved to `rs-imap-train-ham-group' but not to
> `rs-imap-inbox-group'. IIRC, it worked correctly when using Gnus 5.11
> (from Emacs CVS). `spam-process-destination' works also with multiple
> destinations[1] for the same group.
> (defvar rs-imap-method "nnimap+kiz:"
> "Prefered IMAP method.")
> (defvar rs-imap-inbox-group (concat rs-imap-method "INBOX")
> "IMAP inbox.")
> (defvar rs-imap-spam-group (concat rs-imap-method "Spam/spamblock")
> "Group for incoming spam.")
> (defvar rs-imap-train-ham-group (concat rs-imap-method "bayes/ham")
> "Group for training ham.")
> (defvar rs-imap-train-spam-group (concat rs-imap-method "bayes/spam")
> "Group for training spam.")
>
> (setq
> gnus-parameters
> `(;; [other stuff]
> (":Spam/Unsure"
> (ham-process-destination ,rs-imap-train-ham-group
> ,rs-imap-inbox-group)
> (spam-move-spam-nonspam-groups-only nil)
> (spam-process-destination ,rs-imap-train-spam-group
> "nnml+personal:misc.Spam.2006")
> (spam-contents gnus-group-spam-classification-spam)
> (auto-expire . nil))
> ;; [other stuff]
> ("^gmane\\."
> (spam-contents gnus-group-spam-classification-ham);; tool bar
> (spam-process
> ,(if (boundp 'spam-summary-exit-behavior)
> ;;(> (gnus-continuum-version) 5.11)
> '((spam spam-use-gmane))
> '(gnus-group-spam-exit-processor-report-gmane))))
> ;; [other stuff]
> ))
Can you go inside the group and check what spam-move-ham-routine is
doing? Specifically, what is the value of
(gnus-parameter-ham-process-destination gnus-newsgroup-name)
and whether spam-move-ham-routine is getting invoked at all?
> In the "^gmane\\." entry, I need a conditional for v5-10 and trunk,
> because the backward compatibility code doesn't work correctly,
> see [2].
Well, spam-list-of-processors doesn't contain
gnus-group-spam-exit-processor-report-gmane so perhaps that's why it
doesn't work. Can you try adding
(gnus-group-spam-exit-processor-report-gmane spam spam-use-gmane)
to that list and see if that fixes your problem?
> Additionally to those two items, my message from September [3].
> Unless these problems are resolved, I'd rather not put it into v5-10.
> [3] <news:v9vf0ugya0.fsf@marauder.physik.uni-ulm.de>
> http://thread.gmane.org/v9vf0ugya0.fsf%40marauder.physik.uni-ulm.de
That message has several issues; I definitely will fix the manual by
taking Chong's version and adding the changes for the new-style
backend variables. Was there anything else I missed?
Thanks
Ted
p.s. you're so well-organized, it makes me jealous. Is there an Emacs
rs-brain-organize-mode? :)
> [1]
> ,----[ *Messages* ]
> | Exiting summary buffer and applying spam rules
> | Registering 1 specific articles as spam using backend spam-use-move
> | Copying to nnimap+kiz:bayes/spam: (657)...
> | nnimap: Setting marks in bayes/spam...done
> | nnimap: Updating info for nnimap+kiz:bayes/spam...done
> | Copying to nnml+personal:misc.Spam.2006: (657)...
> | Wrote /home/dept/ste/Mail/personal/misc.Spam.2006/715
> | 1 spam messages were registered by backend spam-use-move.
> | nnimap: Setting marks in Spam/Unsure...done
> | Retrieving newsgroup: nnimap+kiz:bayes/spam...
> `----
>
> [2] <news:v9br2n61qd.fsf@marauder.physik.uni-ulm.de>
> http://thread.gmane.org/v9br2n61qd.fsf%40marauder.physik.uni-ulm.de
next prev parent reply other threads:[~2006-02-13 19:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 20:59 Gnus manual update Chong Yidong
2006-02-06 19:18 ` Ted Zlatanov
2006-02-06 20:19 ` Chong Yidong
2006-02-06 20:31 ` spam manual update for Gnus (was: Gnus manual update) Ted Zlatanov
2006-02-06 22:49 ` spam manual update for Gnus Reiner Steib
2006-02-08 20:20 ` Ted Zlatanov
2006-02-08 20:56 ` Chong Yidong
2006-02-09 15:00 ` spam.el: Bugs, compatibility with v5-10 (was: spam manual update for Gnus) Reiner Steib
2006-02-13 19:04 ` spam.el: Bugs, compatibility with v5-10 Ted Zlatanov
2006-02-13 22:36 ` Emacs 20.7 compatibility in v5-10 (was: spam.el: Bugs, compatibility with v5-10) Reiner Steib
2006-03-20 19:51 ` Emacs 20.7 compatibility in v5-10 Ted Zlatanov
2006-03-20 20:38 ` Reiner Steib
2006-02-13 19:15 ` Ted Zlatanov [this message]
2006-02-14 15:04 ` ham destination bugs Reiner Steib
2006-02-20 14:29 ` Reiner Steib
2006-05-27 10:17 ` Reiner Steib
2006-05-30 13:55 ` Ted Zlatanov
2006-06-08 20:54 ` spam.el spam-summary-prepare-exit rewrite (was: ham destination bugs) Ted Zlatanov
2006-04-19 14:23 ` spam manual update for Gnus Reiner Steib
2006-04-20 18:18 ` Ted Zlatanov
2006-04-20 18:38 ` Chong Yidong
2006-04-20 20:08 ` Reiner Steib
2006-04-20 23:20 ` Miles Bader
2006-04-20 18:45 ` Ted Zlatanov
2006-02-06 20:25 ` message mode screwy (was: Gnus manual update) Ted Zlatanov
2006-02-08 16:52 ` message mode screwy Reiner Steib
2006-02-09 15:37 ` Ted Zlatanov
2006-02-13 18:58 ` Ted Zlatanov
2006-02-13 22:15 ` Adam Sjøgren
2006-02-13 22:39 ` Reiner Steib
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=4nzmkv9ij8.fsf_-_@lifelogs.com \
--to=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).