From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: Filtering Spam Messages With Bogofilter
Date: Thu, 08 Oct 2009 14:51:13 -0500 [thread overview]
Message-ID: <87iqepwtou.fsf@lifelogs.com> (raw)
In-Reply-To: <6753d3c8-33f9-40ff-9cb0-6ace8fa1265a@d23g2000vbm.googlegroups.com>
On Wed, 16 Sep 2009 06:14:32 -0700 (PDT) Volkan YAZICI <volkan.yazici@gmail.com> wrote:
VY> On Sep 15, 3:57 pm, Ted Zlatanov <t...@lifelogs.com> wrote:
>> Bogofilter is not set as your group's spam exit processor (according to
>> spam-group-processor-p). Can you try using `G c' on a group and
>> explicitly set it in the group/topic parameters, then mark spam and
>> exit? If that works, we can check what's inconsistent in your Lisp
>> configuration (it looks fine as I said, but I may have missed
>> something). There are old-style and new-style backend specification
>> formats, which makes it even more annoying for you I'm sure.
VY> I "G c"ed into "misc" group and selected below parameters.
VY> [X] Spam Summary Exit Processor: [Value Menu] Spam Summary Exit
VY> Processor Choices:
VY> Set:
VY> [ ] gnus-group-spam-exit-processor-ifile
VY> OBSOLETE: The ifile summary exit spam processor.
VY> ...
VY> [ ] gnus-group-ham-exit-processor-copy
VY> OBSOLETE: The ham copy exit ham processor. [More]
VY> [ ] Spam: Gmane Report
VY> [X] Spam: Bogofilter
VY> [ ] Spam: Blacklist
VY> ...
VY> [ ] Ham: Spam Oracle
VY> Which spam or ham processors will be applied when the summary is
VY> exited.
VY> After pressing to "[Done]" I returned back to *Group* buffer and
VY> marked an article in the "misc" group via "S x" and closed the group
VY> buffer. Below are the related lines appeared in the *Messages* buffer.
VY> Exiting summary buffer and applying spam rules
VY> Registering 1 articles with classification spam, check spam-use-
VY> bogofilter
VY> Marking spam as expired without moving
VY> it
VY> Expiring articles...done
VY> Quit
This is good, it means the Bogofilter backend was called for that message.
VY> But when I entered into "misc" group again, I still see the spam
VY> marked message with an "E" status (as was before). Shouldn't it be
VY> disappeared and messaged would have moved into "spam" group?
You need to set up the spam move target explicitly through `G c' again.
Give it a group name. The default (nil) means don't move, just mark
expired.
VY> BTW, I have below configurations in my ~/.gnus.el file and "misc" is
VY> collected under "mail" topic.
VY> (defun custom-nnmail-expiry-wait (group)
VY> (cond ((member (gnus-group-topic group) '("mail" "personal")) 90)
VY> (t 30)))
VY> (setq
VY> gnus-agent-expire-all nil
VY> gnus-agent-expire-days 7
VY> gnus-agent-expire-unagentized-dirs t
VY> nnmail-expiry-wait 7
VY> message-expires 7
VY> nnmail-expiry-wait-function 'custom-nnmail-expiry-wait
VY> gnus-auto-expirable-newsgroups ".*")
That's all fine, it just relates to expiry and not to spam.el.
Ted
next prev parent reply other threads:[~2009-10-08 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 7:00 Volkan YAZICI
2009-09-14 19:22 ` Ted Zlatanov
2009-09-15 8:14 ` Volkan YAZICI
2009-09-15 12:57 ` Ted Zlatanov
2009-09-16 13:14 ` Volkan YAZICI
2009-10-08 19:51 ` Ted Zlatanov [this message]
2009-11-08 20:23 ` Volkan YAZICI
2009-11-12 19:09 ` Ted Zlatanov
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=87iqepwtou.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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).