Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Using spam.el to report spam to gmane
Date: Mon, 08 Dec 2008 12:47:11 -0600	[thread overview]
Message-ID: <86k5aaijww.fsf@lifelogs.com> (raw)
In-Reply-To: <87wseepo1n.fsf@anzu.internal.golden-gryphon.com>

On Fri, 05 Dec 2008 10:47:00 -0600 Manoj Srivastava <srivasta@golden-gryphon.com> wrote: 

MS> 	I added this to my gnusrc:
MS> (setq gnus-spam-autodetect-methods
MS>       '(
MS>         (".*" . (spam-use-blacklist
MS>                  spam-use-BBDB
MS>                  ;;spam-use-bogofilter
MS>                  spam-use-gmane-xref))
MS>         ))              ;default
MS> (setq gnus-spam-autodetect '(("^nntp.*" . t)
MS>                              ("^gmane\\." .t)
MS>                              ("^nnml:\\(debian-.*\\)$" . t)))

MS> (setq gnus-spam-process-newsgroups
MS>       '(("^nntp+news.gmane.org" ((spam spam-use-gmane)))
MS>         ("^gmane\\."            ((gnus-group-spam-exit-processor-report-gmane)))
MS>         (".*" nil)                      ;test
MS>         ))

MS> ;; Since the above did not seem to do anything, try this
MS> (add-to-list
MS>  'gnus-parameters
MS>  '("^gmane\\."
MS>    (spam-autodetect-methods spam-use-gmane-xref spam-use-gmane spam-use-BBDB)
MS>    (spam-autodetect . t)
MS>    (spam-process (gnus-group-spam-exit-processor-report-gmane))
MS>    ))

MS>         As you can see, thre is some duplication here, as I tried to get
MS>  this to work.  It seems to properly recognize spam; ao the
MS>  spam-atuodetect part is right.  But while sniffing my network traffic
MS>  while leaving a group where I had marked articles as spam, no report
MS>  was sent to gmane.

MS>         What am I doing wrong? Is the spam reporting deferred in some
MS>  way? Do I need to take additional action?

First of all, turn up gnus-verbose to 10 and watch *Messages*.  You'll
see at least some indication that things are happening, if they are.
Easier than sniffing network traffic, I hope.  spam.el only does work
when you exit the group so you were looking in the right time frame.

Every Gnus parameter that spam.el uses has a test function.  Those are
created by macros in the parameter definition; here's what you need:

(gnus-parameter-spam-process group)

This should return a list looking like this

(((ham spam-use-whitelist)))

That's the easy way to test your settings, too.  When you have things
working, please let us know.  I have not used the global gnus-parameters
variable much, preferring to set topic/group parameters.

For GMane reporting in particular, it's setup like so in spam.el:

(spam-install-nocheck-backend 'spam-use-gmane
			      'spam-report-gmane-unregister-routine
			      'spam-report-gmane-register-routine
			      'spam-report-gmane-register-routine
			      'spam-report-gmane-unregister-routine)

So you want the cell (spam spam-use-gmane) in your parameter list
above.

Ted




      reply	other threads:[~2008-12-08 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 16:47 Manoj Srivastava
2008-12-08 18:47 ` Ted Zlatanov [this message]

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=86k5aaijww.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).