Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Volkan YAZICI <volkan.yazici@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Filtering Spam Messages With Bogofilter
Date: Wed, 16 Sep 2009 06:14:32 -0700 (PDT)	[thread overview]
Message-ID: <6753d3c8-33f9-40ff-9cb0-6ace8fa1265a@d23g2000vbm.googlegroups.com> (raw)
In-Reply-To: <87vdjkz7q0.fsf@lifelogs.com>

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.

I "G c"ed into "misc" group and selected below parameters.

  [X] Spam Summary Exit Processor: [Value Menu] Spam Summary Exit
Processor Choices:
      Set:
      [ ] gnus-group-spam-exit-processor-ifile
          OBSOLETE: The ifile summary exit spam processor.
      ...
      [ ] gnus-group-ham-exit-processor-copy
          OBSOLETE: The ham copy exit ham processor. [More]
      [ ] Spam: Gmane Report
      [X] Spam: Bogofilter
      [ ] Spam: Blacklist
      ...
      [ ] Ham: Spam Oracle
  Which spam or ham processors will be applied when the summary is
exited.

After pressing to "[Done]" I returned back to *Group* buffer and
marked an article in the "misc" group  via "S x" and closed the group
buffer. Below are the related lines appeared in the *Messages* buffer.

  Exiting summary buffer and applying spam rules
  Registering 1  articles with classification spam, check spam-use-
bogofilter
  Marking spam as expired without moving
it
  Expiring articles...done
  Quit

But when I entered into "misc" group again, I still see the spam
marked message with an "E" status (as was before). Shouldn't it be
disappeared and messaged would have moved into "spam" group?

BTW, I have below configurations in my ~/.gnus.el file and "misc" is
collected under "mail" topic.

  (defun custom-nnmail-expiry-wait (group)
    (cond ((member (gnus-group-topic group) '("mail" "personal")) 90)
          (t 30)))

  (setq
   gnus-agent-expire-all nil
   gnus-agent-expire-days 7
   gnus-agent-expire-unagentized-dirs t
   nnmail-expiry-wait 7
   message-expires 7
   nnmail-expiry-wait-function 'custom-nnmail-expiry-wait
   gnus-auto-expirable-newsgroups ".*")


Regards.

  reply	other threads:[~2009-09-16 13:14 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 [this message]
2009-10-08 19:51         ` Ted Zlatanov
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=6753d3c8-33f9-40ff-9cb0-6ace8fa1265a@d23g2000vbm.googlegroups.com \
    --to=volkan.yazici@gmail.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).